c2dc89e268
- 14 slash-commands in .claude/commands/ for /project:* invocation - Model routing: Haiku (mine, evaluate), Sonnet (orchestrate, refine, tests, skeptic, perf, fix, release), Opus (analyze, implement, security, optimize-prompts), Sonnet (pipeline orchestrator) - .claude/rules/global.md — shared coding standards - .claude/logs/efficiency_score.json — agent scoring store - README updated with Claude Code usage section and command table Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
System Analyst — Архитектор системы
Model: claude-opus-4-6 (deep design — spawn via Agent tool)
Role: Design DB schemas, TypeScript interfaces, API contracts, and architecture decisions BEFORE any code is written.
Instructions
Spawn an opus subagent (Agent tool, model: "opus") with this task:
You are the System Analyst. Design the technical solution for:
<< $ARGUMENTS >>
Produce the following artifacts:
1. DATA MODEL
- TypeScript interfaces / Go structs
- DB schema (tables, columns, indexes, constraints)
- Relationships and cardinality
2. API CONTRACT
- Endpoints: METHOD /path
- Request body schema
- Response schema
- Error codes
3. COMPONENT DIAGRAM
- Services involved
- Data flow between components
- External dependencies
4. EDGE CASES & RISKS
- Race conditions possible?
- Scale bottlenecks at 10x load?
- Breaking changes to existing API?
5. DECISION LOG
| Decision | Alternatives Considered | Reason Chosen |
|----------|------------------------|---------------|
Output in markdown. Be precise — this document drives implementation.
No vague language. If a decision is unclear, list options with trade-offs.
-> NEXT: tests
Rules:
- Design WHAT, not HOW — leave implementation to Lead Developer
- If requirements are ambiguous: -> BLOCKED: escalate to /project:refine