frontend
Detect a repo's current frontend state and bring it to a professional, cohesive look with minimal design decisions from the user — install or wire an appropriate component system, write a project DESIGN.md, and verify the result with a screenshot-critique loop. Manually invoked via /frontend against any repo, regardless of how much frontend work already exists there.
- License 许可
- MIT
- 最近更新
- 2026-09-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- frontend
- description
- Detect a repo's current frontend state and bring it to a professional, cohesive look with minimal design decisions from the user — install or wire an appropriate component system, write a project DESIGN.md, and verify the result with a screenshot-critique loop. Manually invoked via /frontend against any repo, regardless of how much frontend work already exists there.
02 资源文件 6
- 参考文档references/bootstrap-react.md4.1 KB
- 参考文档references/existing-system-react.md1.4 KB
- 参考文档references/non-react.md1.5 KB
- 参考文档references/retrofit-react.md1.7 KB
- 参考文档references/visual-loop.md2.0 KB
- 脚本scripts/detect.py5.8 KB
03 SKILL.md 正文
Frontend polish
Turn whatever frontend state a repo is in — nothing, something inconsistent, or an already mature design system — into a cohesive, professional result, while making as few design decisions on the user's behalf as possible without asking for their taste directly. Follow these steps in order.
1. Precondition: aesthetic guardrails
This skill orchestrates what gets changed; it deliberately does not carry its own aesthetic
guidance, because the official frontend-design skill already covers that (avoiding generic
AI-slop palettes and typography, a plan-review-build-critique process). Check whether that
skill is available in this session.
If it is not available: tell the user it's required for good results and offer to install it
(/plugin install frontend-design@claude-plugins-official). Only continue without it if the
user explicitly says to proceed anyway — and if so, note in the final report that aesthetic
guardrails were skipped for this run.
2. Precondition: git safety
Run git status --porcelain in the target repo. If it's not a git repository, or the working
tree isn't clean, stop and ask the user whether to proceed anyway, commit/stash first, or create
a throwaway branch. Do not write any files until the tree is clean or the user has explicitly
accepted the risk.
3. Detect
Run python "<skill-dir>/scripts/detect.py" <repo-root> (substitute the actual path to this
skill's directory and the repo being worked on). This is a deterministic scan — trust its
evidence field over any impression from skimming the repo yourself, and show that evidence to
the user later rather than restating a bare verdict.
It returns:
framework:next,react, orothermaturity:bootstrap(no real UI system yet) orexisting(some system is present)signal:foundornone—nonemeans detection was inconclusive, not that the repo is emptyevidence: the concrete facts behind the classification
4. Classify and pick a path
frameworkisnextorreact,maturityisbootstrap→references/bootstrap-react.mdframeworkisnextorreact,maturityisexisting→ read theevidence, then form a recommendation between two paths (do not treat this as fact — it's your read of the evidence, and the user can override it at the confirm gate):references/retrofit-react.mdif the evidence points to inconsistent or ad hoc styling (many small CSS files, mixed/no component library, no coherent token system)references/existing-system-react.mdif the evidence points to one coherent system already in place (a real component library, a design-token setup, few one-off styles)
frameworkisother, orsignalisnone→references/non-react.md, regardless ofmaturity. Ifsignalisnone, tell the user at the confirm gate that detection was inconclusive so they can correct the path before anything is touched.
5. Confirm gate
Before writing anything, present:
- the detected classification and its evidence
- the chosen path (and the recommended alternative, for react+existing repos, so the user can switch)
- the theme or token direction you'd apply, already picked — don't ask the user to choose a theme, just show what you picked and why
- a draft
DESIGN.mdfor the target repo - the file allowlist this run will stay inside — the specific files/directories relevant to the
chosen path (see each reference file for its scope), plus
DESIGN.mdand, if a component library is being installed,package.json
Treat this as a negotiation, not a yes/no gate. If the user pushes back on any part — wrong path, disagrees with the theme, wants a file excluded — revise that part and present again rather than starting over or proceeding regardless. Only move to execution once the user gives an explicit go-ahead.
6. Execute
Follow the chosen reference file. Stay inside the allowlist confirmed in step 5. Write
DESIGN.md into the target repo — this is the one artifact from this whole skill that's
project-specific, since it describes that project's actual design system, not this skill's
process.
7. Enforce the allowlist
Before reporting anything as done, run git diff --name-only and git status --porcelain in
the target repo and check every changed or new path against the allowlist confirmed at the gate.
If anything falls outside it, stop and tell the user exactly what was touched beyond scope — let
them decide whether to keep it, rather than shipping it silently.
8. Verify
Follow references/visual-loop.md for a bounded screenshot-critique-fix pass against the
running app.
9. Report
Summarize: which path was taken, which files changed (cross-checked against the allowlist in step 7), what the visual loop found and fixed, screenshots if available, and anything left unresolved within its iteration budget.
04 同仓库更多 Skills
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
research
Research a topic exhaustively before planning or building — discuss the goal, draft a comprehensive question set, dispatch parallel research agents against it, and synthesize a findings report. Stops there; does NOT chain into /grill-me or plan mode. Use when the user wants to research, investigate, or survey a topic/technology/approach before deciding what to do about it.
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
grill
A relentless interview to sharpen a plan or design.