IDE extension = main build surface

Use for:

• one module
• one folder
• one authority-safe patch
• one reviewable diff

Prompt style:

• stay inside this folder only
• do not touch prisma outside actions
• page.tsx read-only
• components dumb only
• api routes external only
• return finished pluggable code

CLI = repo guardrail pass

Run after each module task:

• inspect changed files
• typecheck
• lint
• detect rule violations
• fix only high-confidence issues

Best tasks:

• find mutations in pages/components
• find prisma imports outside actions
• find api routes doing internal plumbing
• tighten imports/types after refactor

Web / Cloud = parallel thinking and bounded implementation

Send tasks like:

• audit this subsystem and produce patch plan
• compare competing implementations
• review this branch for authority drift
• prepare staged refactor sequence

Best when:

• task is long
• task can run in parallel
• you want to keep coding locally

Desktop app = command center

Use when multiple threads are alive:

• active implementation
• validation pass
• architecture audit
• docs/spec generation

Best for:

• worktrees
• git review
• parallel branches
• keeping investigations separated

1. Start in IDE extension on one vertical slice
2. Use CLI to validate and mechanically enforce rules
3. Send larger audits/reviews to Codex cloud
4. Use app only when several threads/branches are active

• one route
• one entity
• one action set
• one projection surface
• one bug family

Avoid:

• whole app rewrites
• mixed architecture + feature + styling in one prompt
• unclear mutation authority