Redesign
Audit an existing web UI and produce a modernization plan plus a fresh design system. Use when a site or app already works but looks dated or generic and needs a proper visual audit and a redesign pass, not a rebuild from scratch. Preserves content, routes, and SEO.
Install
$ agentstack add skill-darcos-loft-fluid-redesign ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-darcos-loft-fluid-redesign) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Redesign
Audit-first. For a site that already works but looks templated or dated, this finds what is wrong, decides what to keep, and ships a committed new identity, without throwing away working structure.
When to use
- An existing site (Webflow, WordPress, an old React app) needs to look current.
- A client hands you a live URL and wants it modernized.
- A redesign that must preserve content, SEO, and routes.
The workflow
- Audit. Run the
fluiddetector on the codebase (or read the live DOM and CSS). Catalogue the generic-look tells: fonts, palette, spacing, shadows, the slop list. Note what is genuinely good and worth keeping. - Draw the keep/change line. Preserve: content, information architecture, routes, anything that converts. Change: the identity (palette, type, surface, motion), the layout repetition, the bans.
- Generate the new identity with the
design-systemskill. Brief it from the brand, pick fromdata/, commit. Two redesigns in the same sector get different palettes. - Map old to new. A token migration: old hardcoded values become new CSS variables, component by component. Keep a small table so nothing is missed.
- Re-skin, do not rebuild. Keep the markup and structure, swap the look: tokens, type, motion. Add
fluidmotion where it earns its place. - Pre-flight. Run the detector again, check
design-system/reference/rules.md(locks, hero discipline, bans). Produce a before/after so the value is visible.
Rules
- Preserve what converts. A redesign that drops content or breaks routes is a rewrite, not a redesign.
- One identity, committed. Never half-redesign (new colors on old fonts).
- Show the before and after.
Pairs with: design-system (the new identity), fluid (the motion and the detector audit).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Darcos-Loft
- Source: Darcos-Loft/fluid
- License: MIT
- Homepage: https://fluid.plrstudio.fr
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.