How do I install the Mvp Builder Init skill?

Run npx skillmds@latest add app-builders-club/mvp-builder-init in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mvp Builder Init safe to use?

SkillMD's automated safety review verdict for this skill is WARNING. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mvp Builder Init?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mvp Builder Init free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mvp Builder Init?

app-builders-club (@app-builders-club) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mvp Builder Init by app-builders-club

Name: Mvp Builder Init
Author: app-builders-club

Mvp Builder Init

Initialize a project for the MVP Builder pipeline. Copies the scaffold into the current project — project instructions (CLAUDE.md), path-scoped platform rules, and curated permissions. Run once per project after installing the mvp-builder plugin; also handles upgrades and migration from pre-plugin installs.

File contents

MVP Builder Init

Materializes the plugin's scaffold into the current project. Agents, skills, and MCP servers already ship with the plugin — this step installs the parts a plugin cannot carry: always-on project instructions, path-scoped rules, and permission settings.

Input

$ARGUMENTS — rules preset:

Preset	Rules installed
`web`	frontend.md, backend.md
`mobile`	backend.md, mobile.md, ios.md
`all`	all four

If $ARGUMENTS is empty, ask in chat: "What platform is this project? (web / mobile / all)" and wait for the answer. Default to all only if the user says they don't care.

Execution

Determine [platform] from which agent you are: running as Claude Code → claude (installs CLAUDE.md, .claude/rules/, .claude/settings.json); running as Codex → codex (installs AGENTS.md with a Platform Rules section, rules in .codex/rules/, and subagent definitions in .codex/agents/).
Locate the installer inside the installed plugin. This skill's base directory (announced when the skill is invoked) is <plugin-root>/skills/mvp-builder-init, so the installer is two levels up:

test -f "<this skill's base directory>/../../scripts/install.sh" && echo found

If found, run it:

bash "<this skill's base directory>/../../scripts/install.sh" --platform [platform] --rules [preset] --yes

If NOT found (unexpected plugin layout), fall back to fetching the installer from the repository — note this pulls the latest release, which may be newer than the installed plugin:

curl -fsSL https://raw.githubusercontent.com/app-builders-club/mvp-builder/main/scripts/install.sh | bash -s -- --platform [platform] --rules [preset] --yes

The script handles all three scenarios itself:

Clean project — copies scaffold, writes .mvp-builder-manifest
Upgrade (manifest present) — overwrites only files the user has not modified; modified files are kept and the new version lands alongside as <file>.new
Legacy install (pre-plugin .claude/commands, .claude/agents, or old CLAUDE.md without a manifest) — backs everything up to .mvp-builder-backup-<timestamp>/, removes superseded files, then performs a clean install

Relay the script's report to the user verbatim — installed files, kept files, .new files, backup location.
If any <file>.new files were created, tell the user to diff and merge them manually — never merge automatically.
Finish with next steps:
- Restart the session so the new project instructions load (CLAUDE.md / AGENTS.md)
- On Codex: enable subagents first — multi_agent = true under [features] in ~/.codex/config.toml
- Then invoke the prd skill to define the product (or feature if ai-docs/PRD.md already exists)

Error Handling

Installer missing at both locations: report both paths/URLs tried; the plugin installation is likely broken — suggest reinstalling the plugin
Non-zero exit: relay the script's error output verbatim; make no partial fixes
User declines migration prompt relayed by script: stop; nothing was modified

---name: mvp-builder-initdescription: Initialize a project for the MVP Builder pipeline. Copies the scaffold into the current project — project instructions (CLAUDE.md), path-scoped platform rules, and curated permissions. Run once per project after installing the mvp-builder plugin; also handles upgrades and migration from pre-plugin installs.---# MVP Builder InitMaterializes the plugin's scaffold into the current project. Agents, skills, and MCP serversalready ship with the plugin — this step installs the parts a plugin cannot carry: always-onproject instructions, path-scoped rules, and permission settings.# Input`$ARGUMENTS` — rules preset:| Preset | Rules installed ||--------|-----------------|| `web` | frontend.md, backend.md || `mobile` | backend.md, mobile.md, ios.md || `all` | all four |If `$ARGUMENTS` is empty, ask in chat: "What platform is this project? (web / mobile / all)"and wait for the answer. Default to `all` only if the user says they don't care.# Execution1. Determine `[platform]` from which agent you are: running as Claude Code → `claude` (installs `CLAUDE.md`, `.claude/rules/`, `.claude/settings.json`); running as Codex → `codex` (installs `AGENTS.md` with a Platform Rules section, rules in `.codex/rules/`, and subagent definitions in `.codex/agents/`).2. Locate the installer inside the installed plugin. This skill's **base directory** (announced when the skill is invoked) is `<plugin-root>/skills/mvp-builder-init`, so the installer is two levels up:```bashtest -f "<this skill's base directory>/../../scripts/install.sh" && echo found```3. If found, run it:```bashbash "<this skill's base directory>/../../scripts/install.sh" --platform [platform] --rules [preset] --yes``` If NOT found (unexpected plugin layout), fall back to fetching the installer from the repository — note this pulls the latest release, which may be newer than the installed plugin:```bashcurl -fsSL https://raw.githubusercontent.com/app-builders-club/mvp-builder/main/scripts/install.sh | bash -s -- --platform [platform] --rules [preset] --yes```The script handles all three scenarios itself:- **Clean project** — copies scaffold, writes `.mvp-builder-manifest`- **Upgrade** (manifest present) — overwrites only files the user has not modified; modified files are kept and the new version lands alongside as `<file>.new`- **Legacy install** (pre-plugin `.claude/commands`, `.claude/agents`, or old `CLAUDE.md` without a manifest) — backs everything up to `.mvp-builder-backup-<timestamp>/`, removes superseded files, then performs a clean install4. Relay the script's report to the user verbatim — installed files, kept files, `.new` files, backup location.5. If any `<file>.new` files were created, tell the user to diff and merge them manually — never merge automatically.6. Finish with next steps: - Restart the session so the new project instructions load (`CLAUDE.md` / `AGENTS.md`) - On Codex: enable subagents first — `multi_agent = true` under `[features]` in `~/.codex/config.toml` - Then invoke the `prd` skill to define the product (or `feature` if `ai-docs/PRD.md` already exists)# Error Handling- **Installer missing at both locations**: report both paths/URLs tried; the plugin installation is likely broken — suggest reinstalling the plugin- **Non-zero exit**: relay the script's error output verbatim; make no partial fixes- **User declines migration prompt relayed by script**: stop; nothing was modified

Frequently asked questions