skyroc-admin-prd-prototype

Invoke the skill by name and specify the target module. It reads the current FastAPI routes, schemas, and React pages, writes a Markdown PRD separating facts from assumptions, then generates one standalone index.html per real page with working interactions.

Each prototype is a self-contained HTML file with functional drawers, dialogs, filters, toasts, and dark theme toggling. Pages link to each other via relative paths and must pass a static verification script plus browser checks at 1440px, 1024px, and 390px widths.

No. Prototypes use in-memory demo data and never call real write endpoints or embed tokens. The PRD explicitly marks which capabilities are implemented, partially implemented, or still design assumptions pending backend work.

It re-reads the current FastAPI source code on every task and treats historical or external references only as business context. Conflicts are resolved in favor of the current backend contract, and unverifiable items are recorded as design assumptions.

The skill runs Oxfmt formatting checks and its verify-prototypes.mjs script, which enforces doctype, lang, viewport, focus styles, media queries, aria attributes, and absence of template placeholders. Browser testing then covers interactions, console errors, and three viewport sizes.

Avoid it when you only need production React code changes, since the skill does not modify production frontend code unless explicitly requested. It is also unnecessary for trivial single-field changes that do not warrant a full PRD and prototype cycle.