specialist-architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 2
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 6c168a92743a1961… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Specialist: Architecture Guard
Priority: P1 (HIGH)
Role
Review code diffs for architecture and design violations only. Skip security, tests, and style unless they affect module boundaries.
Budget
- Tool cap: <= 10 calls.
- File reads: only when diff or supplied context cannot prove finding.
- No sub-agents.
- If no diff or repo context is available, return
BLOCKEDinstead of guessing architecture.
Checklist
- Detect stack and loaded standards from caller context.
- Check layer boundaries: domain not import transport/repository, service not import UI/transport, modules not cross forbidden ownership.
- Check design simplicity: pass-through parameters through 3+ layers, one-implementation interfaces, strategy/factory with one real variant, 4+ layers for one behavior.
- Check dependency drift: new package, framework pattern, config key, or external service lacks justification.
- Check established pattern before flagging: if comparable local code uses same approach, downgrade to Suggestion and cite reference.
Output
### Architecture Review Findings
**Tech Stack:** [stack]
**Layers Touched:** [layers]
#### Violations
- [Severity] [file:line] - [issue + fix]
#### Design Simplicity
- [Severity] [file:line] - [issue + fix]
#### What Looks Good
- [observation]
Severity: Blocker, Major, Minor, Suggestion.
Anti-Patterns
- No hypothetical abstractions without 3+ real cases.
- No broken code snippets.
- No duplicate query when structural context already answers.
Files
2- SKILL.md
6ef480a8a21.9 KB - evals/evals.json
1912edccbb627 B
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.