plugins/monorepo-standards/skills/new-monorepo/SKILL.md
Stamp a new polyglot monorepo using the AO Cyber Systems scaffold — root CLAUDE.md with Layout table, per-area CLAUDE.md, path-filtered CI workflows, comprehensive .gitignore, and the no-binaries pre-commit hook config. Use this for new product monorepos (the 5-monorepo architecture: aodex, aosentry, eden-biz, politihub, aohealth, plus future ones). Triggers on: "new monorepo", "scaffold a monorepo", "set up a monorepo", "create a new product monorepo".
npx skillsauth add ao-cyber-systems/devflow-claude new-monorepoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
CLAUDE.md with a Layout tableCLAUDE.md for every selected area (go / flutter / admin / proto).gitignore covering Go + Flutter + Node + native build artifacts.devflow/no-binaries.yml (active by default once the plugin is installed)paths: filtersmonorepo-doctor.yml workflow that runs on every PRThe skill is opinionated about the four standard areas. Product-specific extras (mobile/, pos/, api-dart/) should be added by the user after scaffolding and reflected in the Layout table. </objective>
<context> Arguments: $ARGUMENTSExpected forms:
<slug> — minimum; product name defaults to title-cased slug, target defaults to ./<slug><slug> --name "Eden Biz" --areas go,flutter --target /tmp/eden-bizStandard areas: go, flutter, admin, proto. Anything else fails.
</context>
1. Resolve plugin root.
The template lives at ${CLAUDE_PLUGIN_ROOT}/templates/monorepo-scaffold/. The CLI is ${CLAUDE_PLUGIN_ROOT}/skills/new-monorepo/lib/cli.js.
2. Confirm the plan with the user.
Before stamping, summarise:
Wait for confirmation unless --yes or --force was passed.
3. Stamp the template.
node "${CLAUDE_PLUGIN_ROOT}/skills/new-monorepo/lib/cli.js" \
--slug "<slug>" \
--name "<name>" \
--description "<desc>" \
--areas "<comma-separated>" \
--target "<target>"
4. Validate.
Run the doctor against the new repo to confirm it's clean:
node "${CLAUDE_PLUGIN_ROOT}/skills/monorepo-doctor/lib/cli.js" --root "<target>"
Exit code 0 = success.
5. Suggest next steps.
cd <target> && git init && git add . && git commit -m "chore: scaffold from monorepo-standards"monorepo-standards plugin in .claude/settings.json so the no-binaries hook is active for all collaborators (see plugin README)<when_to_use> Use new-monorepo for:
--force carefully)Do NOT use for:
cargo new, go mod init, etc.)
</when_to_use>development
Resolve a parked decision and resume autonomous execution. Use when you see a pending DECISION-NNN.md in .planning/decisions/pending/, when the user wants to choose an option for a blocked checkpoint:decision, or when you need to tell the executor which option to take. Triggers on: "resolve decision", "decide DECISION-", "pick option for DECISION-", "unblock DECISION-", "answer DECISION-", "choose option for decision", "I want option-a", "go with option-b", "my answer is".
development
Orchestrate a multi-step DevFlow workflow by chaining skills. Use when the user wants to invoke a sequence of skills as one ask (e.g., "build and sync to github", "research, plan, then build", "ship and announce"). Triggers on: "ship X to Y", "build and X", "plan and X", "X then Y", "in one go", "as a chain", "all in sequence", "chain", "ship-and-sync", "research-plan-build"
development
Validate that a monorepo follows the AO Cyber Systems layout convention — root CLAUDE.md declares every area, every area has its own CLAUDE.md, no compiled binaries are tracked in git. Reads the root `CLAUDE.md` Layout table, walks the working tree, and reports drift in a single Markdown summary. Standalone — works on any repo. Triggers on: "audit monorepo layout", "monorepo doctor", "is this monorepo healthy?", "check the layout", "find binaries in the repo".
development
Build, review, or visually inspect web pages using Hugo templates, Tailwind CSS, and the project's brand design system. Use when the user wants to create new pages, design components, audit existing UI, review frontend code, or visually test rendered pages. Triggers on: "build the UI", "design this page", "create a page", "review the frontend", "audit the UI", "check UI consistency", "make it look good", "frontend review", "visual review", "check how it looks", "inspect the page"