← ClaudeAtlas

improve-existing-websitelisted

Use when improving an existing website or codebase while retaining its recognizable identity, especially when evidence, scope, or redesign approval is uncertain.
KyaniteLabs/tastecheck · ★ 8 · Web & Frontend · score 71
Install: claude install-skill KyaniteLabs/tastecheck
# Improve Existing Website Improve what is weak without sanding away identity. Existing work contains signal and drift; evidence decides which is which. ## 1. Inspect the product people actually use Open the rendered priority path before prescribing. Trace entry, decision, action, and recovery at wide/narrow widths. Inspect hierarchy, tokens, repeated components, content, supplied analytics/user evidence, and business cues. Label what you can point to **EVIDENCE** and interpretations **INFERRED**. “The primary action changes label across three screens” is direct; “the brand values warmth” is inferred unless brief/product evidence says so. **Done when:** priority path, recurring choices, and highest-cost failures are observable. ## 2. Separate identity from drift Record signals worth preserving: distinctive type, color relationships, interaction patterns, voice, layout logic, or recognizable assets. Classify each change: | Class | Meaning | Authority | | --- | --- | --- | | **Preserve** | coherent, repeated, brief-supported identity | repair defects without replacing the signal | | **Normalize** | accidental variation against an established pattern | safe to align when evidence is strong | | **Approval needed** | a new hierarchy, palette, voice, or material redesign | show the choice and wait for owner agreement | Use `references/signal-vs-drift.md` when repetition, age, or inconsistency could be intentional. Age alone is not drift evidence. **Done when:** every prop