redesign-existing-projects

redesign-existing-projects is a skill for Claude Code, Codex from dmae97/omk. It costs 45 tokens per session (3,332 once invoked), scanned A, a copy of redesign-existing-projects, MIT.

A design skill for improving existing websites and apps while keeping their current functionality. It reviews the current interface, finds common generic design patterns, and applies higher-quality visual standards using any CSS approach.

In plain words
What is it for?
Use it to audit and redesign an existing website or app, whether it uses a CSS framework or plain CSS.
Why use it?
It helps improve an existing product without treating a visual redesign as permission to remove or break working features.

Skill for Claude CodeCodex

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

Good fit Use it to audit and redesign an existing website or app, whether it uses a CSS framework or plain CSS.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dmae97/omk/redesign-skill
View source ↗ dmae97/omk
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 dmae97/omk --skill redesign-skill
Clone the repo
git clone --depth 1 https://github.com/dmae97/omk

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/dmae97/omk/redesign-skill/github.svg)](https://agentmods.dev/skills/dmae97/omk/redesign-skill)
Your own site
<a href="https://agentmods.dev/skills/dmae97/omk/redesign-skill"><img src="https://agentmods.dev/badge/skills/dmae97/omk/redesign-skill/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/dmae97/omk/redesign-skill"><img src="https://agentmods.dev/badge/skills/dmae97/omk/redesign-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,332 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 100% 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.00045 $0.03332
Opus 5.5 $0.00018 $0.01333
Sonnet 5.5 $0.00009 $0.00666
Haiku 4.5 $0.00005 $0.00333

Measured 1mo ago against content hash 98ad3e5b051b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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

100% identical to redesign-existing-projects — 0 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.

.omk/skills/taste-skill/skills/redesign-skill/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 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 · 179 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. 1mo ago First seen · 179 lines · 45 tokens per session scan A 98ad3e5b051b

Subscribe to this mod's changes

redesign-existing-projects is a skill published in the GitHub repository dmae97/omk (148 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 3,332 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to redesign-existing-projects, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

desktop-brand-builder

Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.

QwenLM/qwen-code · 68 tokens

dataviz

Design guidance for charts, graphs, dashboards, maps, and data visualizations, including a local palette validator.

QwenLM/qwen-code · 26 tokens

frontend-design

Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.

Hmbown/CodeWhale · 21 tokens

write-zot-themes

Help the user create, install, or package zot themes, including theme-only extensions.

patriceckhart/zot · 23 tokens

anycap-human-interaction

Collect structured visual feedback from humans using AnyCap's annotation tool, or create and iterate on diagrams using the interactive whiteboard (Excalidraw). Covers image annotation, URL/web page review with screen recording, video review, audio feedback, and collaborative diagramming with Mermaid input. Use when…

anycap-ai/anycap · 190 tokens

design-skill

Use BEFORE building or restyling anything a user will see — web/mobile UIs, landing pages, dashboards, components, emails, AND creative work like Three.js/WebGL/canvas/SVG scenes, data-viz, games, and animations — to make it look intentional and polished, not generic; covers tokens, type, color, layout, motion…

Overbrilliant/ob-1 · 82 tokens