red-team-agent
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught the last defect. Conditional role. Adversarial framing does not compose with a reviewer's frame, which is why this is
$ npx -y skills add vmobifystudio/app-dev-team --agent claude-codeShips with app-dev-team. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught the last defect. Conditional role. Adversarial framing does not compose with a reviewer's frame, which is why this is
Describe your app idea in one line. Get a shipped iOS & Android app. AI App Studio is a team of 30 AI specialists — a CEO, product manager, designers, iOS/Android engineers, a code reviewer, QA, and a release manager — that works like a real software studio.
Repo: vmobifystudio/app-dev-team
Other agents on app-dev-team.
- android-developer
Use to implement Android features in Kotlin/Jetpack Compose from a ticket. Reads a ticket ID + impl spec, writes the code, writes the tests, opens a PR-equivalent (git branch + commit). Multiple instances run in parallel on independent tickets.
Open agent - aso-specialist
Use to prepare the store presence — App Store / Play listing copy, keyword research, screenshots, and the store-readiness gate before shipping. Owns docs/15-aso.md and the store assets. Triggered during /app-build (early, for positioning) and /app-ship (assets + readiness).
Open agent - backend-developer
Use when a ticket needs API or backend work — endpoints, data models, auth, integrations, infra-as-code. Only spawned when backend is in scope per the architecture doc. Runs in parallel with mobile devs on independent tickets.
Open agent - ceo
Use as the top-level orchestrator at the start of any new app project, or when the user wants strategic direction, scope decisions, prioritization tradeoffs, or a go/no-go call on a feature. Owns vision, success metrics, and final scope. Delegates product depth to CPO and
Open agent - chief-of-staff
Use as the single founder interface — prepares decision briefs, tracks unresolved commitments, ensures every founder decision reaches a specification, and maintains docs/17-founder-inbox.md. Exists to reduce founder load, so it is only worth running if it removes more decisions
Open agent - code-reviewer
Use after a developer finishes a ticket and before tech-manager merges. Reviews a single branch / diff against the impl spec, the engineering principles, and the ticket acceptance criteria. Produces an approve / request-changes verdict with line-level notes.
Open agent