fast-brieflisted

Turn product docs, PDFs, or requirements into a focused Astro prototype brief and JSON content plan, written to BRIEF.md at the repo root. Use before building, when the user has source material and needs to scope the smallest useful prototype slice. Treats source docs as suspect by default - flags contradictions, ambiguities, and likely AI-generated boilerplate before producing the brief.
tibichi/fast-preset · ★ 1 · Web & Frontend · score 75

Install: claude install-skill tibichi/fast-preset

# Fast Preset Brief ## Fast Preset Conventions These rules hold across every Fast Preset skill. Other skills assume them - do not deviate. - **Source of truth:** `BRIEF.md` at the repo root. fast-brief writes it; every other skill reads it as step one. - **Files organized per page.** UI primitives live in `src/components/`; prototype data lives in `src/data/`. Single-page prototypes stay flat (`src/components/*.astro`, `src/data/*.json`). The moment a second page is added, each page gets its own folder (`src/components/<page>/`, `src/data/<page>/`); anything used by more than one page moves to `src/components/shared/` / `src/data/shared/`. Promote to `shared/` on the second use, not before. Pages compose components; props mirror the JSON shape they render. - **Colors:** DaisyUI semantic tokens only (`bg-primary`, `text-error`, `bg-base-100`/`200`/`300`, `text-base-content`, etc.). Never raw Tailwind palette colors (`bg-blue-500`, `text-red-600`). - **Variants:** the same purpose uses the same DaisyUI variant everywhere. Every primary CTA is `btn-primary`. Every success notice is `alert-success`. - **Assumption tags:** uncertainty stays tracked, not rendered. In `BRIEF.md` prose, every claim ends in `[verified]`, `[assumed]`, or `[unsure]` with a reason. In `src/data` JSON, records derived from `[assumed]` or `[unsure]` brief items carry `_assumed: true` (optionally `_source: "brief §X"`) so they stay findable for the designer and so `fast-review` can collect them as talkin