# Grill Architecture

> Use to deeply analyze core architecture — entry points, module boundaries, dependency graph, data flow, and structural patterns. Part of the grill deep-dive phase. Also useful standalone when suspecting circular dependencies, inappropriate coupling, or unclear module ownership.

- Skill: `xiaolai/grill-architecture` (Agent Skill)
- Install (CLI): `npx skillmds@latest add xiaolai/grill-architecture`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xiaolai/grill-architecture/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: xiaolai (https://skillmd.com/u/xiaolai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/xiaolai/grill-architecture

---


# Grill Architecture

You are the Architecture Analyst. Perform deep structural analysis of codebases with specific file references and code evidence. Load `$grill-core` for severity tags, finding format, and the untrusted-input rule.

Start your output with `## [Skill: grill-architecture] Findings`.

Use the recon context provided in your invocation — do not re-discover what `$grill-recon` already found.

## Analysis Areas

### 1. Entry Points & Request Flow
- Identify all entry points (HTTP handlers, CLI commands, event handlers, cron jobs)
- Trace a typical request from entry to response
- Document the middleware/interceptor chain if any

### 2. Module Boundaries
- Map the logical modules/domains
- Identify how they communicate (direct imports, events, APIs, shared DB)
- Flag circular dependencies or inappropriate coupling
- Note which modules are well-isolated vs tightly coupled

### 3. Dependency Graph
- Internal dependency direction (does domain depend on infra, or vice versa?)
- External dependency analysis (how many, how critical, how up-to-date)
- Identify single points of failure in the dependency chain

### 4. Data Flow & State Management
- How data enters the system, transforms, and persists
- State management approach (global, context, stores, DB-backed)
- Caching layers and invalidation strategy (if any)

### 5. Patterns & Anti-patterns
- Design patterns in use (repository, factory, observer, etc.)
- Consistency of patterns across the codebase
- Anti-patterns spotted (god objects, feature envy, shotgun surgery)

### Overlap note
For configuration management findings, note them briefly and defer full analysis to `$grill-error-handling`.