fullstack ships one example spec where most presets ship four

[ihatesea69]

fullstack ships one worked example spec (example-stripe-checkout), where six of the nine presets ship four. Someone installing fullstack sees a much thinner spec library than someone installing backend, for no reason other than that nobody has written them yet.

What to do

Add three example specs under presets/fullstack/specs/, each a directory named example-<feature>/ containing requirements.md, design.md, and tasks.md.

Candidate topics that suit a Next.js/T3 stack and do not overlap the existing ones:

• Server-side auth with session management
• File upload with signed URLs and background processing
• Multi-tenant data isolation

Where to look

• presets/backend/specs/example-webhook-delivery-system/ — a good model: EARS acceptance criteria, an Out of Scope section, a Files & Interfaces table, and a final documentation task
• presets/fullstack/specs/_templates/ — the blank templates
• docs/creating-presets.md for the conventions

Before it can merge

Run node scripts/register-example-specs.mjs to add the .config.kiro marker (Kiro's Specs panel needs it) and declare the files in manifest.json, then npx vitest run packages/cli/tests/structural — the feature-expansion test checks every example-* directory is complete.