菜单
Étoile's review manual — the adversarial protocol (assume broken, prove it), Styleframe's anti-pattern checklist, per-area review checklists (engine, theme, docs, tooling, apps), blocking rules, verdict format, and the quality machinery in testing/. Consult at the start of every review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Step 3 of the create-recipe chain. Writes the recipe TypeScript file(s) at theme/src/recipes/<name>/, the per-recipe barrel index, the root barrel update, and Vitest tests. Uses the approved design.md to decide color/variant-style patterns, compound-variant strategy (flatMap or map-per-style), and whether the recipe needs a setup callback (e.g., for @keyframes). Tests are required by default. Writes .context/recipe-<name>/implementation.md.
Step 6 (final) of the create-recipe chain. Runs pnpm typecheck, pnpm --filter @styleframe/theme test, and pnpm lint to verify the recipe is correct. Reports failures with file:line references and suggested fix locations. Does NOT attempt auto-fix. Standalone-capable — runs against any existing recipe without prior artifacts. Writes .context/recipe-<name>/verification.md.
Maître's front-of-house manual — the positioning canon (single source of truth for outbound claims), developer-marketing rules, channel playbooks, the launch checklist, and templates for announcements and copy briefs. Consult before writing any outbound piece, planning a launch, or briefing another seat.
Open a Styleframe pull request in the house style — conventional-commit title, a What/Why/How-verified body, a linked issue, and a changeset when a publishable package changed. Enforces the hard rule that PR descriptions never @mention agents (PRs are public; agent handles must not leak), and routes the review-request mention to the Multica issue comment instead. Invoke with /create-pr whenever you are about to open a PR.
Institutional knowledge for the Styleframe documentation site (apps/docs, Nuxt Content) — content structure and numbered categories, link/route resolution quirks, component-doc anatomy and reference pages, runnable-example rules, voice, framework switcher, and the no-changeset rule for docs. Consult before every apps/docs task.
Institutional knowledge for building Styleframe theme work — the /create-recipe chain, recipe pitfalls unique to this codebase (modifier-registry selectors, utility decomposition, variant-axis ordering, eager ref resolution), shared builders, naming conventions, colocated tests, and Storybook conventions. Consult before EVERY theme/** or storybook task.
| name | adversarial-review |
| description | Étoile's review manual — the adversarial protocol (assume broken, prove it), Styleframe's anti-pattern checklist, per-area review checklists (engine, theme, docs, tooling, apps), blocking rules, verdict format, and the quality machinery in testing/. Consult at the start of every review. |
Builder agents grade their own work generously — that is a property of the species, not a character flaw. The review seat exists to compensate. Operating assumption: the PR is broken; your job is to prove it. When you genuinely fail to prove it, approve it — slow approvals stall eight seats, so run one complete pass, not a drip.
.multica/skills/ (the compounding rule) are always in scope.styleframe-verification): the affected package suites, typecheck, lint. For recipes, run /verify-recipe. For transpiler-output changes, demand the before/after diff and run pnpm test:integration.file:line, reproduction or concrete failure scenario. End with: Approve, or Block + the minimal set of changes that earns approval.ref() / "@token").{ default: true }.color.blue) instead of semantic (color.primary).ref() not destructured from the instance / raw var(--…) strings.export default s from config/extension files.export *).@styleframe/* sub-packages instead of the styleframe barrel.virtual:styleframe imported for the global instance outside *.styleframe.ts.css template literal.any in engine code; missing type predicates on new token types.dist/, .styleframe/).style="" in storybook/docs/app code (utility classes exist; arbitrary values via _prop:[value]).dist/ targets match exports/bin.&:after-style registry keys (never &::after)? Custom-prop utility keys that processRecipeUtilities would reject? Overriding axis declared last? Tests colocated in theme/src/recipes/<name>/? Storybook run once so shims regenerated?theme/ source)? Links resolve (flattened component routes, /docs/theme/ prefix)? Framework-switcher variants present where usage differs? Sentence-initial inline code? (Docs are changeset-ignored — do not demand one.)Taste no convention backs, hypothetical future needs, or style the formatter already accepts. Note them once and move on. Reviews that relitigate settled conventions teach builders to ignore reviews.
testing/integration — the ground-truth harness: builds all packages → packs tarballs → scaffolds a fresh Vite+Vue app via styleframe init → production build → asserts browser-computed styles in Chromium/Firefox/WebKit. Extend it when new public surface ships; it is the only place "works in a real project" is actually proven.testing/benchmark — utility-output vs Tailwind. Any performance claim in any PR gets a number from here or gets rewritten without the claim.