One place for everything the Rapid teams need to build the Aircraft Performance Tool with Claude Code — across three tracks: the frontend design kit (tokens, prototypes, component specs, page commands), the backend skillset (architecture, data model, API contracts, security, DevOps, per-module guides), and the product documentation (PRDs, user flows, user stories). Pick a track below, download its kit, and start building.
.claude/, design/, docs/, CLAUDE.md).
That's Claude Code configuration + reference material — not application architecture.
You still design your own src/ however you like..claude/, design/, docs/ folders and CLAUDE.md alongside your project.import './design/tokens.css' — and (recommended) wire design/tailwind.tokens.js into your tailwind.config./mobile loginTwo slash commands generate any screen for either surface. Add the page name as an argument; run the command alone to be asked which page.
/mobile login # mobile login page /mobile home # mobile home / dashboard /mobile takeoff # core takeoff calculator /tablet login # tablet login (side-rail layout)
Available pages: login · home · takeoff · landing · aircraft · notams · mel · charts · manuals · messages · settings · subscription
Read CLAUDE.md, then design/component-inventory.md and docs/prd.md. We're building the Rapid Pilot App frontend (mobile + tablet) in React + Tailwind + shadcn/ui. Import design/tokens.css at the root. Scaffold the project in the structure YOU think is best, then stop and show me before we build screens. After I approve, I'll generate pages one at a time with /mobile and /tablet. Rules: tokens only (never hex); mobile↔tablet parity; IBM Plex Mono for numeric/aviation values; status by text+color; every list gets empty/loading/error/ success states.
| File | What it is |
|---|---|
| CLAUDE.md | Design rules + asset map + command usage. Auto-loaded by Claude Code. Architecture-free. |
| .claude/commands/ | mobile.md & tablet.md — the /mobile and /tablet page generators. |
| design/tokens.css | Color / type / spacing / radius as CSS variables. The single source of truth for color — import it. |
| design/tokens.json | Same tokens, machine-readable. |
| design/tailwind.tokens.js | Tokens mapped into a Tailwind theme (drop into tailwind.config). |
| design/component-inventory.md | Every component → variants → states → shadcn mapping, incl. future-panel additions. |
| design/prototypes/*.html | Visual source of truth. Compiled bundles — open in a browser to view, don't scrape their source. |
| docs/prd.md | Functional requirements per screen (FR-XX-YY), calc logic, input ranges (§7.3.1), empty-state copy (§11). |
| docs/user-stories.md | User stories with Gherkin acceptance criteria. |
| docs/user-flows.md | Navigation topology and primary flows. |
| docs/docs.html | Human-readable spec hub (all three docs, styled). |