codeprobe-architecture

Standalone Mode

If invoked directly (not via the orchestrator), you must first:

1. Read ../codeprobe/shared-preamble.md (resolve relative to this SKILL.md's location — the sibling codeprobe skill directory — not the user's project) for the output contract, execution modes, and constraints.
2. Load applicable reference files from ../codeprobe/references/ (same resolution) based on the project's tech stack.
3. Default to full mode unless the user specifies otherwise.

Architecture & Structure Analyzer

Domain Scope

This sub-skill detects architectural and structural issues across these categories:

1. Layer Violations — Business logic in controllers, presentation logic in models, database access in views
2. Circular Dependencies — Direct or transitive circular imports between modules
3. God Objects — Oversized files and classes that do too much
4. Anemic Domain Model — Entity classes with no behavior, all logic in service classes
5. Missing Boundaries — No clear module/domain separation, cross-feature coupling
6. Directory Structure — Framework convention violations, flat directory anti-patterns
7. Config/Environment — Hardcoded environment values, missing config abstraction

---

What It Does NOT Flag

• Small projects/scripts with fewer than 5 files — flat structure is appropriate for small codebases and adding layers would be over-engineering.
• Microservices that intentionally have thin layers — a microservice with a single controller, single service, and single repository is fine by design.
• Framework-standard monolith patterns that are idiomatic — e.g., Laravel's default structure for small-to-medium apps, Rails convention-over-configuration patterns, Next.js app directory conventions.
• Prototypes and proof-of-concept code clearly marked as such.
• Generated code directories (e.g., dist/, build/, .next/, __pycache__/).

---

Detection Instructions

Layer Violations

ID Prefix	What to Detect	How to Detect	Severity
ARCH	Controllers containing business logic	Scan files in controller directories (controllers/, Controllers/, routes/, api/). Flag controllers that contain: database queries (SQL, ORM query builders beyond simple find()/findById()), complex conditionals with business rules (3+ branches), calculations, data transformations, or validation logic beyond simple field presence checks. Controllers should delegate to services/actions.	Major
ARCH	Models/entities containing presentation logic	Scan model/entity files. Flag models that contain: HTML generation, string formatting for display (e.g., toHtml(), formatForDisplay()), view-specific transformations, CSS class computation, or response formatting. Models should contain domain logic, not presentation.	Major
ARCH	Views/components calling database directly	Scan view files (.blade.php, .vue, .jsx/.tsx components, .ejs, .pug, Jinja templates). Flag views that contain: direct database queries, ORM calls, raw SQL, or repository method calls. Views should receive data from controllers/props, never fetch it themselves.	Major