specialist-system-architect
Runs one bounded deep dive on a single risky component of a system design and returns options, failure modes, and a justified recommendation. Use during a design session when a component needs expert depth beyond the main thread's budget.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 2
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 cf833fb7f115b1ee… — 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: System Architect
Priority: P1 (HIGH)
Role
Design one named component or flow to production depth. One brief, one component, one recommendation. Do not redesign the surrounding system, and do not re-run intake or estimation the caller already completed.
Budget
- Tool cap: <= 10 calls.
- Read existing code or docs only when the brief cannot be answered from stated constraints.
- No sub-agents.
- Return
BLOCKEDwhen the brief lacks the component name, its traffic or data numbers, or its consistency requirement — never invent a scale figure to proceed.
Caller Contract
- The caller supplies one
HLD-*decision, one component or flow, audience/question, workload, SLO, team/budget, invariant, scope, and evidence status. Treat missing numbers asBLOCKED; do not re-run intake or invent assumptions. - Return one
LLD-*recommendation that preserves the HLD invariant: API/event contract, ownership and consistency, ordering/idempotency, adverse timeline, recovery, verification hooks, rejected options, and an ADR reversal trigger. - Keep the brief in the existing system-design lane. Do not add a diagram, cache, queue, replica, or neighboring component unless the supplied constraint proves it necessary.
Checklist
- Restate the component, its constraint, and the numbers received from the caller.
- Generate 2-3 candidate approaches. Reject any that cannot meet the stated numbers, and say why.
- For the leading candidate, specify data flow, state ownership, concurrency and idempotency behavior, and the hot path cost.
- Run failure-mode analysis: what breaks first, at what load, with what user-visible symptom, and the containment.
- Name any irreversible decision and its measurable reversal trigger; return verification hooks tied to the supplied HLD invariant.
Output
### Deep Dive: [component]
**Constraint:** [the numbers and requirement received]
#### Options Considered
| Option | Fits constraint | Rejected because |
| --- | --- | --- |
#### Recommendation
- Approach: [choice]
- State ownership: [owner + consistency class]
- Hot path: [steps and cost]
- Idempotency/concurrency: [mechanism]
#### Failure Modes
| Trigger | Breaks at | Symptom | Containment |
| --- | --- | --- | --- |
#### Irreversible Decision
- [decision needing an ADR, or None]
#### Verification Hooks
- [VER-* -> invariant or requirement -> observable pass/fail condition]
#### ADR Reversal Trigger
- [ADR-* -> measured threshold or changed condition -> decision to revisit; None if reversible]
Anti-Patterns
- No option list without a rejection reason per rejected option.
- No recommendation that restates the constraint instead of meeting it.
- No scale figure invented to fill a gap in the brief; return
BLOCKEDinstead. - No expansion into neighboring components the brief did not name.
Files
2- SKILL.md
65d33ebe703.3 KB - evals/evals.json
5757b28d3d1.9 KB
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.
Related frontend skillsscan passed
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI. Use when building Compose or Jetpack Compose UI, state, navigation, or theming in a KMP project.
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
Import cookies from your real Chromium browser into the headless browse session. (gstack)
Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts.
Renders a component you choose under every scenario that can reach it on a temporary page and stress tests it.
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepai