scaffold

mrinal-skills

A personal Claude Code plugin marketplace — portable personal skills, agents, hooks, and an output style, version-controlled, with zero manual sync across machines and repos. The idiomatic vehicle for keeping a personal steering layer in sync (per code.claude.com/docs: plugins, plugin-marketplaces, skills).

Plugins

Plugin	Scope	Contents
core	user-level (all repos)	4 skills (cost-aware-delegation, orchestration, git-workflow, deep-research-tiered), 5 agents (advisor-plus, code-reviewer, search, doc-sync, config-auditor), the distinguished-engineer output style, 1 guard hook (guard-secrets)
scaffold	per-repo (opt-in)	2 skills (milestone-workflow, skill-maintenance), 4 commands (/adr, /goal, /milestone, /scaffold:milestone-run), the determinism-auditor agent, 4 hooks (block-main-writes, checkpoint, subagent-trail, validate-config), and references/ for by-hand project setup. Requires core.

core is broadly/globally enabled and project-agnostic. scaffold is the project-enabled half: turn it on per-repo, and it assumes a concrete docs/ + .context/ layout (hand-set up per scaffold/references/project-setup/ — there is no generator). scaffold declares a hard dependency on core in its plugin.json ("dependencies": ["core"]), so enabling scaffold auto-enables core. Each plugin's own README is the authoritative inventory. Further plugins are added as new entries in .claude-plugin/marketplace.json.

TODO — /scaffold:adopt generator: replace the by-hand scaffold/references/project-setup/ steps with a single command that bootstraps a repo's .context/, ADR conventions, and settings.json from templates bundled in the plugin — one command instead of hand-copying, updatable via /plugin update. Not built yet; the by-hand setup works today.

What belongs here vs. not

• Belongs: personal skills/agents/hooks that apply across repos and machines.
• Does not belong: repo-specific skills saturated with one project's policy (they live in that repo's .claude/skills/), and Apple's bundled Xcode skills (swiftui-specialist, etc.) that are re-exported per Xcode update and would go stale if committed — keep those at user level.
• Does not belong: anything superpowers already does better — see below.

Relationship to superpowers

superpowers@claude-plugins-official is assumed present and is the process layer: brainstorming → writing-plans → executing-plans / subagent-driven-development → TDD → systematic-debugging → verification-before-completion → writing-skills. This marketplace does not re-implement any of it. The division:

Concern	Owner
How to write, test, and structure a skill	superpowers:writing-skills (+ skill-creator)
Executing a written plan task-by-task; dispatching per-task subagents	superpowers:executing-plans / subagent-driven-development
How to word a subagent dispatch (pack context, scope, output format)	superpowers:dispatching-parallel-agents
Evidence before claiming done	superpowers:verification-before-completion
Which model runs it, and what it costs — concrete Haiku/Sonnet/strong routing, opts.model per Workflow stage, the budget guard, checkpoint-before-loss	core — see the note below; superpowers tiers by role but never names models or Workflow primitives
Trunk-based git policy — the PR merge method (rebase vs squash), branch routing, protection, required checks, CI delegation	core:git-workflow — superpowers defines only a local git merge in finishing-a-development-branch, and never a GitHub PR merge method
Milestone substrate (docs/playbooks/, .context/, the post-merge status sweep)	scaffold:milestone-workflow
Agents, commands, output style, guard hooks	core/scaffold — superpowers ships none of these