improve-existing-website
Use when improving an existing website or codebase while retaining its recognizable identity, especially when evidence, scope, or redesign approval is uncertain.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 12
- Forks
- 8
01 前言 Front Matter
- name
- improve-existing-website
- description
- Use when improving an existing website or codebase while retaining its recognizable identity, especially when evidence, scope, or redesign approval is uncertain.
02 资源文件 9
- 资产文件assets/improve-checklist.md1.8 KB
- 资产文件assets/INFERRED-SYSTEM.template.md952 B
- 参考文档contract.json2.2 KB
- 参考文档references/audit-procedure.md2.4 KB
- 参考文档references/decision-records.md2.2 KB
- 参考文档references/inspection-state-machine.md1.5 KB
- 参考文档references/interview-contract.generated.md1.0 KB
- 参考文档references/repair-handoffs.md1.2 KB
- 参考文档references/signal-vs-drift.md2.5 KB
03 SKILL.md 正文
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 proposed change names what survives and why it is authorized.
3. Form the smallest coherent direction
Complete assets/INFERRED-SYSTEM.template.md across audience, territory, type, color, layout,
components, voice, and accessibility. Score readiness with references/inspection-state-machine.md.
Ask only questions that change the safe direction; otherwise state inference and evidence.
Do not solve a system problem with isolated polish. Choose a narrow vertical slice proving the direction across a real path (navigation, content section, form/state, narrow layout) before propagating it.
Done when: the direction can be approved, rejected, or resumed without reconstructing the investigation.
4. Approve, repair, and verify
For each repair, record observed failure, preserved signal, smallest coherent edit, owner/
approval source, and proof. After approval, use references/repair-handoffs.md for specialist
passes. Verify the same path/viewports; comparison must show defect changed and signal survived.
If work pauses, save current state, unresolved question, evidence, and exact next decision using
references/inspection-state-machine.md. Resume from that checkpoint, not a fresh opinion.
Done when: report distinguishes repaired drift, preserved identity, browser/static proof, and deliberately deferred ambiguity.
Reference files
references/audit-procedure.md— extraction order.references/signal-vs-drift.md— identity versus accident.references/decision-records.md— scope ADR rules.references/inspection-state-machine.md— readiness/approval.assets/improve-checklist.md— completion ledger.references/repair-handoffs.md— routing/skip rules.references/interview-contract.generated.md— canonical authority.
Self-check
assets/improve-checklist.md is completion authority for inspection, labels, approval,
handoffs, and evidence.
<!-- contract:v1:start -->
Contract (generated)
Canonical detail: contract.json.
- Route: An existing site or codebase needs improvement while preserving its intended identity (+1 in contract.json); avoid: A greenfield project needs direction before anything exists to inspect (+1 in contract.json)
- Exclude: Do not prescribe or edit before inspecting evidence (+1 in contract.json)
- Stop / handoff: Pause when evidence is insufficient for a safe inference (+2 in contract.json); receives [none] -> sends [a11y-pass, art-direction, cognitive-a11y, color-system, component-states, data-viz, deslop-ui, empty-states, humanize-copy, i18n-ready, responsive-layout, spacing-system, tasteroll, theming, web-typography]
- Output: An evidence-labelled inferred system, readiness decision, and scoped repair plan or implementation report
- Evidence:
table_with_evidencewithstatus,reason,remediation,evidence,provenance. <!-- contract:v1:end -->
04 同仓库更多 Skills
example
暂无简介
web-typography
Use when a web product needs a contextual type system, resilient font loading, multilingual glyph or wrap coverage, or readable hierarchy across operational and editorial surfaces.
theming
Use when semantic roles must map coherently across light, dark, forced-colors, or saved theme preferences without contrast or no-flash regressions.
tasteroll
Rapid prototyping through constrained randomness. Audits what exists, fixes what is broken, generates fresh design candidates from context, then rolls the dice between valid alternatives. Lock what works, re-roll what doesn't, converge on a direction. Use for design exploration, rapid prototyping, or when a user wants surprise within guardrails.
tastecheck-pass
Use when finished frontend work needs an honest SHIP or HOLD — a fast evidence pass by one agent in minutes, or a fail-closed deterministic release gate when stakes justify machinery. Verdict first, from the real rendered artifact; checkmarks are not execution evidence.
spacing-system
Use when layout rhythm, density, or gaps feel arbitrary or inconsistent, or when one product needs different reading pressures without splitting into unrelated spacing systems.