SolidJS

Use the official Solid documentation and the installed package version as the source of truth. Solid components establish a reactive graph once; they are not React render functions.

Workflow

1. Read the repository instructions and inspect package.json plus the lockfile to identify the installed Solid packages and versions. For SolidStart, distinguish v1 from v2 before consulting docs or changing code.
2. Read only the documentation branch needed for the task:
   • references/core.md for solid-js, JSX, reactivity, stores, resources, rendering, or tests.
   • references/router.md for @solidjs/router, navigation, route data, actions, or revalidation.
   • references/start.md for @solidjs/start, file routes, server functions, middleware, sessions, API routes, SSR, or deployment.
   • references/meta.md for @solidjs/meta or document-head management.
3. Consult the exact API page before using an unfamiliar primitive. In this documentation repository, read the mapped file under src/routes/; elsewhere, use the mapped https://docs.solidjs.com page. Confirm signatures against the installed package types when docs and dependencies differ.
4. Implement with the existing project conventions. Preserve reactive accessors and owners across module and component boundaries.
5. Run the narrowest relevant test, typecheck, lint, or build. Expand verification when the changed primitive is shared or when focused proof fails.

Core model