julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
809 B
809 B
Monitoring Pattern: Parsing & Review Handling
Sub-Agent Pattern
ALWAYS use sub-agent for output parsing:
# Correct: Let haiku parse
parsed=$("$scripts" orchestrator-helper parse-output "$output_file" dev)
action=$(echo "$parsed" | jq -r '.next_action')
# WRONG: Parse yourself
# content=$(cat "$output_file") # DON'T DO THIS
# if grep -q "SUCCESS" ... # DON'T DO THIS
Why: Sub-agent costs ~200 tokens. Main context is ~50k+. Parsing yourself wastes 99% more context.
Code Review Special Handling
See code-review-loop.md for review cycle logic. Key points:
- Auto-fix via instruction:
code-review ${story_id} auto-fix all issues without prompting - No menu detection needed - instruction handles it
- After completion, verify sprint-status before proceeding