styleframe

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.

É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.

Orchestrator that runs the 6-step recipe creation chain end-to-end. Invokes research-recipe, design-recipe, implement-recipe, showcase-recipe, document-recipe, and verify-recipe in order, chaining via .context/recipe-<name>/ artifacts. Users may invoke any sub-skill standalone (/verify-recipe, /document-recipe, etc.) to resume or re-run a single step without restarting the chain. Starts by asking the component name, then checks for existing artifacts before each step.

Step 2 of the create-recipe chain. Classifies the component (color pattern Full/Container/Minimal, variant-style pattern Interactive/Display/Container), picks a base-style template, defines variant axes, chooses a compound-variant strategy, sets defaults, and lists sub-recipes for multi-part components. Requires user approval before writing .context/recipe-<name>/design.md. Run after research-recipe.

Famille's product manual — architecture of apps/app (Supabase auth + license portal), apps/playground, and apps/shared; the friction-report template; the dogfood migration epic; and how to consume Styleframe from application code. Consult before every apps/app, apps/playground, or apps/shared task.

Institutional knowledge for working on Styleframe's engine packages (core, transpiler, loader, runtime, scanner, barrel) — architecture map, AST invariants, the new-token-type checklist, output-stability discipline, tsdown packaging traps, and the Pro license path. Consult before any engine/** change.

Institutional knowledge for Styleframe's tooling and seams — plugin architecture (virtual modules, importree HMR, recipe tree-shaking) across 9 bundlers, CLI conventions, DTCG/Figma sync, the changesets release train, packaging traps, and deploy configs. Consult before every tooling/**, config/**, .github/**, or release task.

Step 1 of the create-recipe chain. Gather component metadata (name, type, multi-part status, color pattern, HTML element) via AskUserQuestion, then WebFetch one or more UI library component pages (Nuxt UI, Shadcn, Radix, Chakra, Mantine) to extract variant axes, styles, sub-parts, states, and accessibility patterns. Writes .context/recipe-<name>/research.md so the next step (design-recipe) has a classified summary to work from. Run this first when creating a new Styleframe recipe.

Staj's research manual — the RFC template with exit criteria, the competitive landscape map (styling engines and UI kits), the CSS platform watchlist, citation discipline, and the teardown format. Consult before starting any research task, RFC, or competitive analysis.

How the Styleframe brigade operates in Multica — the three-loop map (task, issue, flywheel), stall-prevention rules, comment discipline, scope fences, @-mention trigger discipline (a mention wakes its target immediately — fire only when ready), git/PR conventions, definition of done, and the knowledge-compounding rule. Read at the start of every task; consult when unsure how to hand off, when blocked, or when finishing.

How to build and verify work in the Styleframe monorepo — fresh-workspace build order, per-package test/typecheck/lint commands, Storybook shim regeneration, integration-test costs, and CI gates (codecov patch). Consult before running any verification and before claiming any task done.

Mise's triage manual — the path-based routing table, issue decomposition rules, the issue template with acceptance criteria, collision serialization via dependency links, portfolio balance across the four fronts, and the synthesis format. Consult when triaging any issue, planning an epic, or writing a synthesis.

Step 5 of the create-recipe chain. Runs a 4-phase documentation flow (pattern extraction → source analysis → draft → conformance check) grounded 100% in existing recipe doc pages and the recipe TypeScript source. Reference pages auto-select based on color pattern — badge.md for Full, card.md for Container, spinner.md for Minimal. Writes the final doc to apps/docs/content/docs/05.components/<category-dir>/<nn>.<name>.md. Standalone-capable — runs against an existing recipe even without prior artifacts. Absorbs the previous generic write-docs skill.

Step 4 of the create-recipe chain. Creates the Storybook showcase — the styleframe.ts registration file, the stories.ts meta + per-variant stories, the main Vue component, and the <Name>Grid.vue and <Name>SizeGrid.vue preview components. For multi-part recipes, also creates sub-part Vue components (e.g., CardHeader.vue, CardBody.vue, CardFooter.vue). Reads design.md and implementation.md. Writes .context/recipe-<name>/showcase.md with story IDs for document-recipe to reference.