// Run the docs site, blog, or Storybook locally. Use when contributing to documentation, previewing blog posts, or developing UI components in isolation. Not needed for regular frontend development.
| name | setup-docs |
| description | Run the docs site, blog, or Storybook locally. Use when contributing to documentation, previewing blog posts, or developing UI components in isolation. Not needed for regular frontend development. |
| allowed-tools | Bash |
These are all independent of the main dev server — you don't need the database or Auth0 configured to run any of them. Just make sure dependencies are installed first (pnpm install --filter frontend from the repo root).
All commands run from the frontend/ directory.
VitePress docs served at http://localhost:5173:
cd frontend && pnpm docs:dev
Build and preview the production output:
cd frontend && pnpm docs:build && pnpm docs:preview
VitePress blog served at http://localhost:5174:
cd frontend && pnpm blog:dev
Build and preview:
cd frontend && pnpm blog:build && pnpm blog:preview --port 5174
Component development and documentation, served at http://localhost:6006:
cd frontend && pnpm storybook
Build static Storybook:
cd frontend && pnpm storybook:build
--port <N>pnpm install --filter frontend from the repo root firstRecord an architecture decision as an ADR in docs/adr/. Use when choosing between frameworks, libraries, databases, or architectural patterns; stating a decision with reasoning ("we decided X instead of Y because..."); or querying past decisions ("why did we choose X?").
Generate a commit message and commit staged changes using git commit -s -S.
Pre-PR validation — license headers, format, lint, TypeScript check, build, and protected file check. Use before submitting any PR, to check if code is ready, validate changes, or verify a branch before review.
Review a pull request against Insights architecture standards — fetches PR diff, verifies previous comments are addressed, validates PR metadata (title, branch, JIRA, size), runs a code-standards check against every file in `.claude/rules/` and `.claude/hooks/guard-protected-files.sh`, and drafts inline review comments with suggested fixes. NEVER auto-posts comments or submits reviews — always presents a draft in the terminal for user approval before any comment lands on the PR. Use when reviewing PRs, checking PR quality, validating code changes, or when the user says "review", "check this PR", or "audit code".
Full development environment setup from scratch — prerequisites, dependencies, .env file, optional local PostgreSQL database (for auth/collections/chat work), and dev server. Use for first-time setup, broken environments, missing env vars, or when the app won't start.