architecture-review

Files (1)

• SKILL.md

SKILL.md (first lines)

# Architecture Review

## Workflow

1. **Map the components**
   ```bash
   find . -name "*.ts" -o -name "*.js" | head -50
   ls -R src/ lib/ app/ 2>/dev/null
   ```
   Identify: services, models, controllers, utils, configs

2. **Trace data flow** — follow a request from entry to response
   - Where does input enter?
   - What transforms it?
   - Where does output go?

3. **Identify boundaries**
   - What talks to external services?
   - What accesses the database?
   - What's the public API vs internal?

4. **Draw ASCII diagram**
   ```
   ┌─────────┐     ┌─────────┐     ┌─────────┐
   │ Client  │────▶│   API   │────▶│   DB    │
   └─────────┘     └─────────┘     └─────────┘
   ```

5. **Check for concerns**
   - Circular dependencies?
   - God modules that do too much?
   - Missing abstractions?
   - Unclear ownership?

6. **Document findings** — write to `docs/architecture.md`

From franciscsimon/harness, MIT.

More from franciscsimon/harness