fabricate

Audit and improve Fabricate's Svelte UI, Foundry window layouts, and interaction flows. Use for UX reviews, visual design proposals, accessibility checks, responsive behavior, screenshot analysis, or creating UI backlog tasks for `src/ui/`, `styles/`, and related specs.

Implement a single planned Fabricate change in the JavaScript, Svelte, and Vite codebase with assignment-approved focused checks. Use when the issue's OpenSpec delta defines the task and code, canonical spec, or test files need to change under `src/`, `openspec/specs/`, `tests/`, or related runtime files, with the driver responsible for complete validation after integration.

Plan and coordinate Fabricate work from GitHub issues into an OpenSpec change delta authored in the issue. Use when starting any non-trivial change, selecting the next unblocked issue, re-planning after scope changes, or routing work through implementer, reviewer, and docs stages without writing production code.

Perform an independent review of Fabricate changes for correctness, regression risk, test quality, and Foundry V13 compatibility. Use after implementation is complete, when the user asks for a review, or before docs and issue closure.

Verify Fabricate's integration with the Foundry VTT API and lifecycle. Use at design time and in implementation review whenever a change calls Foundry APIs or hooks into Foundry's lifecycle; it researches Foundry sources, then the official API docs, then community discussions to confirm the real shape and behaviour of Foundry and keep Fabricate's integration seamless.

Audit and refine Fabricate's crafting domain model, ubiquitous language, and spec-to-code alignment. Use for naming decisions, DDD modelling, DOMAIN.md updates, spec or code audits, research into other crafting systems, or backlog tasks about domain fidelity.

Scan Fabricate for likely defects, edge cases, testing gaps, and unreliable UI behavior, then record actionable issues. Use for bug hunts, reliability audits, regression-risk analysis, or creating GitHub issues instead of directly implementing fixes.

Research Fabricate's competitive landscape, product differentiation, and monetization options, then maintain `COMPETITIVE_ANALYSIS.md`. Use for market-fit analysis, rival module comparisons, crafting UX research, pricing research, or monetization strategy updates.

Synchronize Fabricate documentation with approved code changes. Use after review approval or for docs-only maintenance involving JSDoc in `src/` and the Jekyll site in `docs/`, without modifying runtime logic or tests.

Structure JavaScript modules, objects, and collaborators so code is readable, explicit in its dependencies, easy to change, and easy to test. Use when designing or refactoring JS boundaries, reviewing maintainability or testability, or deciding how responsibilities should be split.

Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.