菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use before writing any code, spec, or store asset on a Mobify Studio app — loads the relevant House Knowledge Base pack(s) so output matches the studio's established conventions instead of generic defaults. Every IC and exec agent invokes this first.
Use when pointing the team at an EXISTING, already-built app instead of a blank project — detects the stack, reverse-engineers the as-built architecture, and classifies remediation work as safe-to-auto-fix vs risky-needs-approval. Triggered by /app-onboard, /app-audit, and by /app-run when it detects a non-empty app directory.
Use to actually launch multiple developer agents in parallel via the subagent tool (Task/Agent), given a sprint plan and board. Triggers from /app-build or when the tech-manager says "spawn the pod". Encapsulates the rules for safe concurrent agent execution.
Use to construct a complete Product Requirements Document for a mobile app from a vision file. Used primarily by the CPO agent. Triggers on requests to "write the PRD", "spec out the product", or as part of /app-plan.
Use at the very start of a new app project to convert a one-line idea or rough brief into a structured requirements document the CEO/CPO/CTO agents can act on. Triggers when the user says "build an app", "I have an idea for an app", or kicks off /app-init with a fuzzy prompt.
Use to convert the backlog into a runnable sprint with parallel ticket assignment and dependency tracking. Used primarily by the tech-manager. Triggers on "plan the sprint", "what does the pod do next", or as part of /app-build.
| name | architecture-builder |
| description | 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. |
Produce docs/20-architecture.md and docs/21-engineering-principles.md from docs/00-vision.md + docs/10-prd.md.
Platform decision — iOS / Android / both, with order if sequential.
iOS stack —
Android stack —
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.
A short rulebook. Examples to include or adapt:
!! (Android)print / Log.d in shipped codeREADME.md at the module rootEvery decision in §2 and §3 has one paragraph of "why" tied to the PRD. If you can't write the "why", reconsider the choice.