Architecture builder
Skill vmobifystudio/app-dev-team/skills/architecture-builder
Use to produce the technical architecture doc and engineering principles for a mobile app. Used primarily by the CTO agent. Triggers on "design the architecture", "pick the stack", or as part of /app-plan.From its SKILL.md
npx -y skills add vmobifystudio/app-dev-team --skill architecture-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.4 KB, as published. Nobody here has run it
Architecture builder
Produce docs/20-architecture.md and docs/21-engineering-principles.md from docs/00-vision.md + docs/10-prd.md.
docs/20-architecture.md sections
-
Platform decision — iOS / Android / both, with order if sequential.
-
iOS stack —
- Swift version (latest stable)
- Minimum iOS target — resolve
knowledge/stack-defaults.md's relative rule (flagship = latest major minus one) to a concrete number here, and record how you resolved it - UI: SwiftUI by default; UIKit only if PRD demands something SwiftUI struggles with
- State:
@Observable+@MainActoron ViewModels only (Combine /@Published/ObservableObjectare forbidden —knowledge/ios-conventions.md) - Networking: URLSession + async/await, or a named lib
- Persistence: SwiftData (content apps) or GRDB+SQLite/FTS5 (camera/media) — pick by PRD complexity
- DI: lightweight — protocol + initializer injection
- Testing: Swift Testing (
@Test/@Suite) for unit and domain tests, not XCTest. UI automation stays XCUITest — it is XCTest-based, has no Swift Testing equivalent, andruntime-gateruns it, so a blanket "never XCTest" would ban the suite the release gate expects. Name the snapshot lib. State the coverage floor for the pure-Swift domain engine package (knowledge/stack-defaults.md)
-
Android stack —
- Kotlin version
- minSdk / targetSdk (set based on PRD users)
- UI: Jetpack Compose
- Architecture: MVVM or MVI, picked once
- Networking: Retrofit + OkHttp + Kotlinx Serialization (or named alternative)
- Persistence: Room (or named alternative)
- DI: Hilt (flagship) or Koin (utility tier)
- Async: Coroutines + Flow
- Testing: JUnit, Turbine, MockK, Paparazzi (screenshot), Compose UI test
-
Shared concerns — auth, analytics, crash reporting, feature flags, remote config, push.
-
Backend interface — sketch the APIs the apps need. If backend is in scope, name the service shape.
-
Repository layout —
/ ├── ios/ # Xcode project / SwiftPM workspace ├── android/ # Gradle multi-module ├── backend/ # if in scope ├── docs/ # all team docs └── specs/ # ticket-level specs if any -
CI / release — branch model, build pipeline, signing, distribution channel (TestFlight, Play internal track).
-
Non-functional budgets — cold start, memory, payload size, accessibility floor (WCAG 2.1 AA).
-
Risks — top 3 with mitigations.
docs/21-engineering-principles.md
A short rulebook. Examples to include or adapt:
- Every PR ships with tests
- No force-unwraps (iOS) / no
!!(Android) - Every screen has accessibility labels and a snapshot test
- No new third-party dep over 200KB without written exception
- Strings are localized from day one
- Logs go through the named logger; no
print/Log.din shipped code - Public API for a module is documented in a
README.mdat the module root
Quality bar
Every decision in §2 and §3 has one paragraph of "why" tied to the PRD. If you can't write the "why", reconsider the choice.