Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add elayadesign/redesign-skill --skill redesign-existing-projectsgit clone --depth 1 https://github.com/elayadesign/redesign-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/elayadesign/redesign-skill/redesign-existing-projects)<a href="https://agentmods.dev/skills/elayadesign/redesign-skill/redesign-existing-projects"><img src="https://agentmods.dev/badge/skills/elayadesign/redesign-skill/redesign-existing-projects/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/elayadesign/redesign-skill/redesign-existing-projects"><img src="https://agentmods.dev/badge/skills/elayadesign/redesign-skill/redesign-existing-projects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00100 | $0.04420 |
| Opus 5 | $0.00050 | $0.02210 |
| Sonnet 5 | $0.00020 | $0.00884 |
| Haiku 4.5 | $0.00010 | $0.00442 |
Grade A, and why
redesign-existing-projects scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redesign Existing Projects
This skill is a diagnostic. It finds what is wrong with an existing interface and fixes it in place.
Design values
All concrete values (fonts, background colors, spacing, radius, icon sets, motion timing) live in the Design Values section at the bottom of this file. That section is the single source of truth. The audit below tells you what to look for; Design Values tells you what to replace it with.
Never invent a font, hex value, spacing number, radius, or easing curve that is not in Design Values. If a situation is not covered there, ask rather than guessing.
To adapt this skill to a different design system, edit only the Design Values section. The entire audit follows it automatically.
How this works
- Scan — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, CSS modules), and the current design patterns.
- Diagnose — Run the full audit below. List every generic pattern, weak point, and missing state you find. Report before fixing.
- Fix — Apply targeted upgrades inside the existing stack, in the Fix Priority order. Do not rewrite from scratch. Improve what is there.
Design audit
Typography
- Browser default fonts, or Inter / Roboto / Arial / Open Sans / Helvetica. Replace with an approved font from the Design Values section.
- Two typefaces on one site. Consolidate to one, unless the project brief explicitly calls for a pair.
- Italic type anywhere. Remove it. Use weight, size, or color for emphasis instead.
- Ultra bold weights (800, 900, black). Cap at semibold or bold.
- Only Regular (400) and Bold (700) in use. Introduce Medium (500) and SemiBold (600) for finer hierarchy.
- Headlines lack presence. Increase display size and tighten letter spacing so headlines feel heavy and intentional. Adjust tracking only within the line height the type scale already provides.
- Body text too wide. Cap paragraph measure at roughly 65 characters.
- Numbers in a proportional font. Enable
font-variant-numeric: tabular-numsfor data heavy interfaces. - Missing letter spacing adjustments. Negative tracking on large headers, positive tracking on small labels and caps.
- All caps subheaders everywhere. Switch to sentence case or small caps. Do not switch to italics.
- Orphaned words. A single word alone on the last line. Fix with
text-wrap: balanceon headings andtext-wrap: prettyon body. - Hyphens inside copy. Do not use
-in headings, body text, or labels. Rewrite the phrase. - Arbitrary or off scale font sizes. Resolve every size to the Tailwind type scale. Never leave
text-[19px],font-size: 22px, or1.4remin place. If a size does not land on a step, snap to the closest step below and take its paired line height. Do not combine this with independently set custom line heights from the two fixes above; adjust only within the matched step's value so the rules do not fight. - Buttons with off scale type. Main buttons
text-basesemibold. Header buttonstext-smsemibold.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 260 lines · 100 tokens per session scan A 8ed4b9f5301e
redesign-existing-projects is a skill published in the GitHub repository elayadesign/redesign-skill (235 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 4,420 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…