new

Load the using-triadjs skill for framework context, then the triad-schema, triad-endpoint, triad-services, triad-adapters, and triad-testing sub-skills as needed.

Scaffold a complete, working TriadJS project based on the user's description ($ARGUMENTS). Do NOT ask a stream of clarifying questions — pick sensible defaults (sqlite + Fastify + ESM + TypeScript + tsx for dev) and proceed. If the user's description is vague, scaffold a generic "Items" CRUD API as a starting point.

What to produce

Create this directory layout inside a subdirectory (or the current directory if empty):

package.json
tsconfig.json
triad.config.ts
src/
  schemas/
    <resource>.ts        # t.model + CreateX/UpdateX derivations + ApiError
  endpoints/
    <resource>.ts        # createX, getX, listX, updateX, deleteX with behaviors
  repositories/
    <resource>.ts        # in-memory repo as a starting point
  services.ts            # createServices + declare module augmentation
  test-setup.ts          # default-exported test services factory
  app.ts                 # createRouter + router.context with bounded context
  server.ts              # Fastify wiring

Mandatory rules

1. Default-export the router from src/app.ts.
2. Module-augment ServiceContainer in src/services.ts — declare module '@triadjs/core' { interface ServiceContainer extends AppServices {} }.
3. Every endpoint has at least one behavior scenario, plus ...scenario.auto() in the behaviors array for boundary coverage.
4. Use t.empty() for 204 responses, never t.unknown().optional().
5. Use ctx.respond[status](body) exclusively — never raw { status, body }.
6. Assertion strings use double quotes, match phrases from the triad-behaviors skill phrase table, and don't try to use null.
7. ApiError model is shared across every endpoint's 4xx responses.
8. Pin @triadjs/* packages to ^0.2.0 in package.json unless the user specifies otherwise. Before writing the final package.json, run npm view @triadjs/core version to confirm the current published major/minor and adjust the range to match — the plugin version may drift ahead of what's on npm.
9. Enable Swagger UI in the generated server.ts by passing docs: true to triadPlugin (Fastify), createTriadRouter (Express), or createTriadApp (Hono). This serves the live OpenAPI spec at /api-docs/openapi.json and Swagger UI at /api-docs as soon as npm run dev is running — no extra step needed. Default is "on in dev, off in production"; docs: true forces on in both.