Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Enforces architectural rules that prevent structural decay: circular dependencies, implicit coupling, barrel abuse, and misplaced validation. These rules are mechanical — an AI coding agent can follow them without subjective judgment.
Before architecture work, read dev for classification, fast paths, rule authority, family invariants, verification, and safety; current/public evidence follows its Conditional Routes.
Use browser verification only after candidate URLs exist.
| Condition | Reference |
|---|---|
| Change boundaries, seams, layers, shared packages, or public exports above C0/C1; choose module owners/depth | Module boundaries (ARCH-DECISION-01, ARCH-MAP-01) |
| Detect/fix import cycles or classify coupling | Import structure, cycle commands, coupling examples |
| Create/modify index or re-export files | Barrel policy, barrel examples |
| Place shape parsing, domain invariants, or security checks | Validation matrices and exceptions |
| Review structural changes, add CI conformance, query structural indexes, or use decision trees | Architecture review |
| Durable architecture documentation | cxc-dev-scaffolding |
| Security policy/auth, observability, review, RCA, or infrastructure boundaries | Cross-skill owners |
Severity: CRITICAL Rule: Parse untrusted data at trust boundaries and avoid repeating shape validation inside one trusted typed boundary. Domain invariants (valid ranges, state transitions, relational constraints) belong to the domain owner even for in-process callers. Authorization and assertions for genuinely reachable invalid states remain allowed.
Ownership: this section distinguishes ingress shape parsing, domain invariants and
reachable-state assertions. dev-security owns security validation and authorization
policy; placement must not erase a business invariant or required defense-in-depth.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
The English summary is being prepared. Showing the original description.
Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.
The English summary is being prepared. Showing the original description.
Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.
The English summary is being prepared. Showing the original description.
Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.
The English summary is being prepared. Showing the original description.
Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.
The English summary is being prepared. Showing the original description.
Use for debugging and system comprehension. Triggers: debug this, root cause, how does X work, reverse engineer, 왜 안 돼, 디버깅, 원인 분석, 로직 파악, 뜯어봐.
The English summary is being prepared. Showing the original description.