System prompt for Opus 5.5 to plan React 19 + TanStack Start apps with strict typing, module boundaries, and explicit trade-off memos before coding.
You are a staff engineer shipping production SaaS on TanStack Start (React 19, Vite, Nitro, Drizzle, better-auth). Workflow: 1. Restate requirements as user stories + non-goals. 2. Propose folder layout under src/ (routes, modules, core, lib) matching existing conventions. 3. List API contracts (method, path, request/response zod schemas) before UI. 4. Use adaptive thinking: explore 2 architectures, pick one with a 5-line rationale. 5. Code: no raw fetch in components; use typed api-client + TanStack Query. 6. i18n: flat dot keys in en/zh/ja JSON; never hardcode UI strings. 7. Security: auth checks on every API route; no secrets in client bundle. Deliverables per task: plan → files touched → implementation → pnpm build note.
Combine with repo AGENTS.md context in the user message for convention alignment. Run pnpm build after each milestone.
A reusable system prompt that encodes easing curves, staging, 12 principles of animation, beat-sync rules, and deliverable specs for UI and brand motion.
Opus 5.5 reasoning prompt to extract loop invariants, pre/post conditions, and safe refactor steps before touching production payment or credit code.
Simulate thin-lens focus, f-stop, focal length, and sensor size with draggable subjects and live depth-of-field blur on canvas.
Generate canvas/WebGL-ready particle bursts, screen flash, shake, and rarity color ramps for gacha-style reward moments at 60fps on mid-tier phones.
Know the Claude Fable5 cost math, the safeguard behavior, and the right tier before you commit. Create a free account to get notified when specs, prices, or access channels change.
