architecture-principle…
Architecture principles for manifest-dev: how its maintainer wants skills, wrappers, references, state and the workflow…
Regenerate the Codex distribution copy of the plugin skills, and the copies of the shipped verify tool, and check them for drift. Run after changing anything under claude-plugins/*/skills. OpenCode, Pi and Cursor read the source tree directly and need no sync.
Claude Code
$ npx -y skills add doodledood/manifest-dev --skill sync-tools --agent claude-code
Codex
$ npx skills add doodledood/manifest-dev --skill sync-tools -a codex -y
Cursor
$ npx skills add doodledood/manifest-dev --skill sync-tools -a cursor -y
Gemini CLI
$ npx skills add doodledood/manifest-dev --skill sync-tools -a gemini-cli -y
GitHub Copilot
$ npx skills add doodledood/manifest-dev --skill sync-tools -a github-copilot -y
OpenCode
$ npx skills add doodledood/manifest-dev --skill sync-tools -a opencode -y
Windsurf
$ npx skills add doodledood/manifest-dev --skill sync-tools -a windsurf -y
name: sync-tools description: 'Regenerate the Codex distribution copy of the plugin skills, and the copies of the shipped verify tool, and check them for drift. Run after changing anything under claude-plugins/*/skills. OpenCode, Pi and Cursor read the source tree directly and need no sync.' user-invocable: true metadata: internal: true
Every host reads the same skill files. The Claude Code plugins under `claude-plugins/` are the source; OpenCode (`dist/opencode/plugin/index.js`), Pi (repo-root `package.json`, `pi.skills`) and Cursor (`claude-plugins/*/.cursor-plugin/plugin.json`, whose plugin root is the source plugin directory) point straight at `claude-plugins/*/skills`. Only Codex needs a copy, because it installs a plugin into its own cache, and that copy is generated:
python3 scripts/sync_dist.py # regenerate dist/codex/plugins/*/skills byte-identically from source python3 scripts/sync_dist.py --check # exit 1 on any drift (tests/test_dist_skill_references.py runs this)
The same commands copy the verification tool setup-project ships (`setup-project/references/harness/verify` and `verify.mts`) to `scripts/` and into the eval scaffolds that embed it, and check those copies too.
Run the first command after any change under `claude-plugins/*/skills`, then commit the regenerated tree with the change. There is no per-host rewrite: shipped skill text names no host primitive (`tests/test_skill_frontmatter.py` enforces that), so a copy is a copy.
These are not generated. Edit them when what they describe changes:
| File | What it carries | |------|-----------------| | `dist/codex/plugins/manifest-dev/.codex-plugin/plugin.json`, `dist/codex/plugins/manifest-dev-tools/.codex-plugin/plugin.json` | Codex plugin manifests; `version` must equal the source plugin's `.claude-plugin/plugin.json` version | | `.agents/plugins/marketplace.json` | Codex marketplace registry pointing at the two plugin directories | | `dist/opencode/plugin/index.js`, `dist/opencode/plugin/package.json` | OpenCode plugin entry (registers the source skill dirs and slash-command wrappers); `version` tracks `manifest-dev`'s | | `dist/opencode/AGENTS.md` | OpenCode instructions file the plugin registers | | `dist/pi/prompts/*.md` | Pi prompt-template aliases (`/do`, `/auto`, `/babysit-pr`) | | `claude-plugins/*/.cursor-plugin/plugin.json`, `.cursor-plugin/marketplace.json` | Cursor plugin manifests and marketplace; `version` must equal the source plugin's | | `dist/codex/README.md`, `dist/opencode/README.md`, `dist/pi/README.md`, `dist/cursor/README.md` | Per-host install and update instructions |
Version bumps follow the repo's Versioning rules; this skill does not bump anything.
Hand your agent a task. Get back work you can trust. manifest-dev is a set of free, open-source skills for coding agents.
Architecture principles for manifest-dev: how its maintainer wants skills, wrappers, references, state and the workflow…
Ship a change to a file setup-project copies or emits into projects (ADR_FORMAT.md, NORTH_STAR_FORMAT.md, the verification…
Design principles for manifest-dev: how its maintainer wants the visual and interaction design guidance the plugin ships, and the…
Harden a manifest-dev task guidance file for one-shot quality — either /define''s quality-gate/Default set or figure-out''s probe…
Analyze Claude Code sessions to learn what went right/wrong and suggest high-confidence improvements to skills. Use when asked to…
The red-flag lists mirrored between figure-out''s and define''s task files, so a change to one side lands on the other. Use when…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.