redesign-existing-projects

redesign-existing-projects is a skill for Claude Code, Codex from Kevin-Liu-01/Agent-Machines. It costs 85 tokens per session (3,453 once invoked), scanned A, a copy of redesign-existing-projects, MIT.

A workflow for improving an existing website or app by examining its code and applying targeted visual changes without replacing the whole project.

In plain words
What is it for?
Use it to upgrade an existing frontend built with a CSS framework or plain CSS.
Why use it?
It helps fix generic styling, weak typography, missing interface states, and other design problems while preserving existing functionality.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to upgrade an existing frontend built with a CSS framework or plain CSS.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kevin-liu-01/agent-machines/taste-redesign
Install

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.

Any agent
npx skills add Kevin-Liu-01/Agent-Machines --skill taste-redesign
Clone the repo
git clone --depth 1 https://github.com/Kevin-Liu-01/Agent-Machines

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for redesign-existing-projects

README.md
[![agentmods](https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/taste-redesign/github.svg)](https://agentmods.dev/skills/kevin-liu-01/agent-machines/taste-redesign)
Your own site
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/taste-redesign"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/taste-redesign/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.

agentmods 80×15 button for redesign-existing-projects

Your own site · 80×15
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/taste-redesign"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/taste-redesign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,453 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.03453
Opus 5 $0.00043 $0.01726
Sonnet 5 $0.00017 $0.00691
Haiku 4.5 $0.00009 $0.00345

Measured 9d ago against content hash 63404e528f8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

Origin

This is a copy

95% identical to redesign-existing-projects — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

knowledge/skills/taste-redesign/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Redesign Skill

How This Works

When applied to an existing project, follow this sequence:

  1. Scan — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, etc.), and current design patterns.
  2. Diagnose — Run through the audit below. List every generic pattern, weak point, and missing state you find.
  3. Fix — Apply targeted upgrades working with the existing stack. Do not rewrite from scratch. Improve what's there.

Design Audit

Typography

Check for these problems and fix them:

  • Browser default fonts or Inter everywhere. Replace with a font that has character. Good options: Geist, Outfit, Cabinet Grotesk, Satoshi. For editorial/creative projects, pair a serif header with a sans-serif body.
  • Headlines lack presence. Increase size for display text, tighten letter-spacing, reduce line-height. Headlines should feel heavy and intentional.
  • Body text too wide. Limit paragraph width to roughly 65 characters. Increase line-height for readability.
  • Only Regular (400) and Bold (700) weights used. Introduce Medium (500) and SemiBold (600) for more subtle hierarchy.
  • Numbers in proportional font. Use a monospace font or enable tabular figures (font-variant-numeric: tabular-nums) for data-heavy interfaces.
  • Missing letter-spacing adjustments. Use negative tracking for large headers, positive tracking for small caps or labels.
  • All-caps subheaders everywhere. Try lowercase italics, sentence case, or small-caps instead.
  • Orphaned words. Single words sitting alone on the last line. Fix with text-wrap: balance or text-wrap: pretty.

Color and Surfaces

  • Pure #000000 background. Replace with off-black, dark charcoal, or tinted dark (#0a0a0a, #121212, or a dark navy).
  • Oversaturated accent colors. Keep saturation below 80%. Desaturate accents so they blend with neutrals instead of screaming.
  • More than one accent color. Pick one. Remove the rest. Consistency beats variety.
  • Mixing warm and cool grays. Stick to one gray family. Tint all grays with a consistent hue (warm or cool, not both).
  • Purple/blue "AI gradient" aesthetic. This is the most common AI design fingerprint. Replace with neutral bases and a single, considered accent.
  • Generic box-shadow. Tint shadows to match the background hue. Use colored shadows (e.g., dark blue shadow on a blue background) instead of pure black at low opacity.
  • Flat design with zero texture. Add subtle noise, grain, or micro-patterns to backgrounds. Pure flat vectors feel sterile.
  • Perfectly even gradients. Break the uniformity with radial gradients, noise overlays, or mesh gradients instead of standard linear 45-degree fades.
  • Inconsistent lighting direction. Audit all shadows to ensure they suggest a single, consistent light source.
  • Random dark sections in a light mode page (or vice versa). A single dark-background section breaking an otherwise light page looks like a copy-paste accident. Either commit to a full dark mode or keep a consistent background tone throughout. If contrast is needed, use a slightly darker shade of the same palette — not a sudden jump to #111 in the middle of a cream page.
  • Empty, flat sections with no visual depth. Sections that are just text on a plain background feel unfinished. Add high-quality background imagery (blurred, overlaid, or masked), subtle patterns, or ambient gradients. Use reliable placeholder sources like https://picsum.photos/seed/{name}/1920/1080 when real assets are not available. Experiment with background images behind hero sections, feature blocks, or CTAs — even a subtle full-width photo at low opacity adds presence.

Read the full file on GitHub · 186 lines

Changes

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.

  1. 9d ago First seen · 186 lines · 85 tokens per session scan A 63404e528f8a

Subscribe to this mod's changes

redesign-existing-projects is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 3,453 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to redesign-existing-projects, differing in 11 lines, and is treated as a copy.

Related

Other skills, from other repositories

21st-ui

Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.

21st-dev/magic-mcp · 63 tokens

theme

Apply brand and visual direction in a Mantle application using its repo-owned theme and UI contracts.

aotter/mantle · 21 tokens

design-taste-frontend

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

dmae97/omk · 61 tokens

saglitzdesign

Design, redesign, build, restyle, improve, critique, review, audit, simplify, polish, or animate a user interface — the front door into SaglitzDesign's eight design skills, for whichever one the work actually needs. Covers landing pages, marketing sites, dashboards, app screens, components, forms, onboarding, empty…

HalidSaglam/saglitzdesign-mcp · 204 tokens

figma-code-connect-design-system

Use when a FigJam board, product requirements document, reference image, Figma design file, published library, or codebase must become or update an evidence-traceable Figma design system, DTCG token hierarchy, platform-specific UI templates, production components, and verified Code Connect mappings. Covers create…

srinitude/skills · 105 tokens

mobile-first-website-design

Use when designing landing pages and marketing websites.

srinitude/skills · 15 tokens