From mz-dev-base
ALWAYS invoke when the user wants to install development rules for a project or globally. Triggers:"init rules","set up rules","install rules","configure coding rules","onboard project".
npx claudepluginhub doctormozg/claude-pipelines --plugin mz-dev-baseThis skill is limited to using the following tools:
Install curated development rules based on detected project context. Two delivery modes:
phases/run.mdrules/agent-workflow.mdrules/code-quality.mdrules/coding-standards.mdrules/context-safety.mdrules/edit-safety.mdrules/git-conventions.mdrules/housekeeping.mdrules/pre-commit-conventions.mdrules/python-conventions.mdrules/self-evaluation.mdrules/strict-typing-python.mdrules/strict-typing-typescript.mdMandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Install curated development rules based on detected project context. Two delivery modes:
--target=rules (default) — write rule files into .claude/rules/ (project) or ~/.claude/rules/ (global). Files with paths: frontmatter stay path-scoped.--target=claudemd — inject rule content directly into ./CLAUDE.md (project) or ~/.claude/CLAUDE.md (global), wrapped in sentinel blocks for idempotent re-runs and clean uninstall.Triggers: "init rules", "set up rules", "install rules", "configure coding rules", "onboard project".
--target=rules; claudemd mode cannot path-scope.project (default) → scope to working directoryglobal → scope to ~/.claude/--target=rules (default) → write as individual rule files--target=claudemd → inject into CLAUDE.md with sentinel blocks--force → overwrite existing rule files / replace existing sentinel blocks--uninstall → remove rules previously installed by this skill (mode-aware)Parse from $ARGUMENTS. Unknown or conflicting tokens → AskUserQuestion; never guess.
| Phase | Goal | Details |
|---|---|---|
| 0 | Setup + user approval | Inline below |
| 1 | Install / update / uninstall | phases/run.md |
$ARGUMENTS: scope (project/global), target (rules/claudemd), --force, --uninstall. Unknown token → AskUserQuestion.task_name = <YYYY_MM_DD>_init_rules_<scope>_<target> where <YYYY_MM_DD> is today's date (underscores); on same-day collision append _v2, _v3..mz/task/<task_name>/.state.md with Status: running, Phase: 0, Started: <ISO>, Scope: <project|global>, Target: <rules|claudemd>, Force: <bool>, Uninstall: <bool>, DetectedContexts: [], Installed: [], Replaced: [], Skipped: [], Removed: [].For --target=claudemd installs, the approval gate in Phase 1 Step 4b must run before any write. A single run-level confirmation covers all subsequent writes in the run.
Read phases/run.md and proceed to Phase 1.
Techniques: delegated to phase files — see Phase Overview table above.
N/A — collaboration/reference skill.
Red Flags: delegated to phase files — see Phase Overview table above.
Verification: delegated to phase files — see Phase Overview table above.
${CLAUDE_PLUGIN_ROOT} is unset or the bundled rules/ directory is not readable, AskUserQuestion with the failing path.unknown for the version tag and note it in the report.After each phase, update .mz/task/<task_name>/state.md with:
Status: running | complete | aborted_by_user | failedPhase: current phase numberDetectedContexts: list of detected language/tooling tagsInstalled: / Replaced: / Skipped: / Removed: filenames or rule ids touched in this runNever rely on conversation memory for cross-phase state — context compaction destroys specific paths and decisions.