Use to write a Ghost blog post end to end, walking the full plan→draft→revise→push flow in one guided pass. Triggers on "write a post about X end to end", "take this from idea to a ghost draft", "guide me through writing a post".
One-shot setup for a new repo's standards: feat → dev → main promotion model with a PR CI gate, GitHub repo setup (branch protection, deploy environments, required reviewers, environment-scoped OIDC), and the language-agnostic quality stack (lefthook hooks + a shared justfile, run identically in CI). The /project-init.
Use when bootstrapping a new repo's CI, setting up deploy workflows, deciding what branch a feature PR should target, or whenever someone proposes "auto-deploy prod on every main merge". Captures the feat → dev → main promotion model with separate Deploy Dev (push to dev) and Deploy Prod (push to main), and links the…
Use when bootstrapping a new repo's GitHub-side setup — branch protection / rulesets, deploy environments, environment secrets, OIDC cloud auth, or required reviewers — or whenever deploy workflows reference secrets. / environment: that don't exist yet. Captures the repo settings that make the feat → dev → main…
Apply project-workflow standards to a repo — feat → dev → main promotion model + CI gate, GitHub repo setup (branch protection, environments, secrets, OIDC), and the quality stack (skylos/fallow via lefthook + a shared justfile, run identically in CI). Detects current state and applies only the missing patterns, so it…
Use when setting up a repo's lint / static-analysis / test tooling — wiring lefthook git hooks (pre-commit auto-fixers + pre-push full verify) and a justfile that is the single source of truth both the hooks and CI call, so local checks and CI can't drift. Language-agnostic: ruff/skylos for Python…
Code-quality workflow: surface, triage, and resolve static-analysis findings (skylos for Python, fallow for TS/JS) with the same backlog-and-epic discipline that feature-workflow provides for feature work. Read-only quality-audit, structured quality-unblock that refuses bare suppressions, hook self-verification that…
Read-only static-analysis snapshot. Runs skylos (Python) and fallow (TS/JS) full audits, writes a fingerprinted snapshot to .claude/quality-snapshots/YYYY-MM-DD.json, and renders a grade card plus delta vs the previous snapshot (NEW / RESOLVED / PERSISTING findings). Use when the user asks "what's my code health?"…
Triage a failing pre-commit hook (skylos or fallow). For each finding, look up the rule in the day-1 playbook and present three options — fix in code, suppress with a required.
Verify that a project's static-analysis git hooks actually fire on bad code — works with lefthook or the pre-commit framework. Use after installing the quality stack (lefthook install), after editing lefthook.yml / .pre-commit-config.yaml, or whenever the user asks "is the hook working?" / "test the hooks" / "verify…
The rule for suppressing static-analysis findings in any language — every suppression carries an inline rationale, and bare suppressions are a quality failure to fix. Use when someone adds or proposes a lint/analysis ignore (# skylos: ignore, # noqa, # type: ignore, # fallow-ignore, // eslint-disable, @ts-ignore…
Sprint planning and team coordination. Triage backlogs by deadline, assign work with self-service specs, audit feature specs for completeness, and generate team communication. Designed for small teams (2-6 devs) with mixed experience levels preparing for demos or releases.
You are a Senior Software Architect, Security Engineer, and Staff-level Reviewer. Your role is to be a critical second set of eyes on a feature implementation — finding correctness bugs, security risks, architectural mismatches, plan drift, regressions, and unverified assumptions before the work is merged.
You are a Senior Software Architect, Security Engineer, and Staff-level Reviewer. Your role is to be a critical second set of eyes on a proposed plan before coding begins — finding weak assumptions, hidden dependencies, risky migrations, and missing test strategy early, while changes are cheap.
Use when this session should coordinate with other coding-agent sessions over the muster bus — registering on the bus, checking your inbox, sending messages or handing tasks to peers, replying on threads, and acting on the notify/nudge wake. Fires when the muster MCP tools (registeragent, sendmessage, getinbox, reply…
Use when the operator wants muster's bus to span more than one machine — deploying the optional hosted backend to their own AWS account with muster-deploy, adding a second device to an existing bus, putting a custom domain on the endpoint, or diagnosing a hosted bus that is not delivering. Fires on "one bus across my…
CLI for MixCraft - connects Claude Code to your music services via MCP. Runs locally from the mixcraft-app npm package. Needs 1 environment variable to run.
This skill should be used when the user asks anything related to music — "make me a playlist", "what should I listen to", "find me songs like X", "add something to my workout playlist", "what have I been listening to", "I need background music for coding", "curate something for a road trip", "improve my playlist"…