johantor
UserClaude Code plugin marketplace: an orchestrated multi-agent crew for feature delivery, a pointer-driven tech-debt & dependency-upgrade fixer, and a shared code-review rubric — installable together or standalone.
Categories
Indexed Skills (37)
mid-run-direction
How to treat an instruction that arrives mid-run rather than in your delegation prompt — a steer from the orchestrator, delivered in a system-reminder-shaped block. Use when direction appears mid-task that your original prompt did not carry: authenticate it on the steer token your dispatch carried, correct wrong premises without discarding the message, and surface anything unanchored or out of bounds.
code-review
Review a pull request or diff in the Zion plugin marketplace — Bash guard hooks, Markdown agent/command/skill prompts, plugin manifests and changelogs. Use when asked to review code, a PR, or a diff in this repository.
backend-go
Go backend stack conventions — modules and workspace layout, go build/vet as the gate, error-handling idiom, build tags. Load when the resolved backend stack is go.
backend-java
Java/JVM backend stack conventions — Maven vs Gradle detection, Spring conventions, the src/main/java layout, and running the build as strictly as the project configures. Load when the resolved backend stack is java.
backend-python
Python backend stack conventions — FastAPI/Django/Flask service conventions, packaging and virtualenv awareness, typecheck-as-build, ruff/black lint. Load when the resolved backend stack is python.
backend-rust
Rust backend stack conventions — cargo workspaces, check/build/clippy as the gate, features and editions, and the inline `#[cfg(test)]` ownership split with oracle. Load when the resolved backend stack is rust.
backend-shell
Shell/Bash project conventions — POSIX vs bash, the traps in `set -euo pipefail`, BSD/macOS portability, shellcheck as the gate, and matching in-process rather than forking. Load when the resolved backend stack is shell.
debt-lane
morpheus's debt lane — pointer-driven tech-debt remediation and dependency upgrades. Use when the task is a pointer to known debt rather than a feature: a suppression (`file:line`), a rule ID (`CS8602`, `no-explicit-any`), a package + target version, or pasted build/lint output; also `/crew:debt`. Classify, enumerate the blast radius, gate, fix in verified batches through the lane workers, commit per batch. An audit scope is `crew:keymaker`'s, not this skill's.
review-gate
How the crew runs a build, test or lint gate: one build location with one writer at a time, one-shot bounded commands, full strictness with warnings as findings, contention told from a code failure, findings routed to the implementer. Preloaded by morpheus and loaded by /crew:review, so the rules hold whichever of the two dispatches the gate. Not for standalone use.
tests-cargo
Rust backend test conventions — the inline unit test vs tests/ integration split and who owns which, cargo test filters for targeted reruns, nextest. Load when the resolved backend stack is rust.
tests-go
Go backend test conventions — _test.go beside the source, table-driven subtests, targeted reruns with -run, the race detector. Load when the resolved backend stack is go.
tests-junit
JVM backend test conventions — JUnit 5 in src/test/java, Surefire vs Failsafe, Maven and Gradle targeted reruns. Load when the resolved backend stack is java.
tests-pytest
Python backend test conventions — pytest layout and naming, conftest fixtures, parametrize, targeted reruns, unittest fallback. Load when the resolved backend stack is python.
tests-shell
Shell test conventions — bats where the project uses it, a plain-bash harness otherwise, asserting on both the allow and the block side. Load when the resolved backend stack is shell.
worker-contract
The rules every crew worker with a shell follows on any dispatch from morpheus: never run git except a plain git mv, ask rather than guess what the delegation left out, treat the build and full suites as morpheus's final gate and run them as the handoff says, never leave a command running at hand-back, hand back with a completion marker and a remaining: line, name an MCP server you expected but cannot see, use a docs MCP over memory, and keep local memory. Preloaded by tank, trinity, oracle, dozer and neo; not for standalone use.
engineering-principles
Core code-quality rules — YAGNI, KISS, DRY with judgment, small single-purpose units, clear naming, minimal-scope diffs. Preload into implementer agents and consult during any code review. Use whenever writing, refactoring, or reviewing code.
loop-engineering
Loop-mode discipline for orchestrated runs — recognize loop intent ("keep going until done", "loop this", "finish it", "clear all the stale ones", "bump everything SAFE"), offer to loop on open-ended work, and run to completion under explicit stop rules that always end at the run's terminal gate. Preload into orchestrator agents (crew's morpheus, keymaker); each defines its own bindings. Use whenever the user asks to keep going, loop, or finish the work without further check-ins.
debt-taxonomy-dotnet
.NET / C# suppression mechanisms, safe-removal recipes, NuGet package-manager variance, and upgrade-tier examples for crew's debt lane. Apply when stack detection (debt-taxonomy) finds a .NET project.
debt-taxonomy-typescript
TypeScript / JavaScript suppression mechanisms, safe-removal recipes, npm/pnpm/yarn package-manager variance, and upgrade-tier examples for crew's debt lane. Covers any JS/TS project — React frontend or Node backend/CLI. Apply when stack detection (debt-taxonomy) finds a JS/TS project.
debt-taxonomy
Stack-neutral core for crew's debt lane — stack detection, classification rubric, blast-radius gate, upgrade tiers, batch commit shape, and handoff-outline format. Pairs with a per-stack taxonomy skill (debt-taxonomy-dotnet, debt-taxonomy-typescript). Loaded by the `debt-lane` skill.
design-tokens
Reading a project's design tokens and reporting visual findings in token terms rather than raw pixels — where tokens live per system (CSS custom properties, Tailwind, SCSS, a tokens JSON, Figma variables), which of them survive to runtime, and how to map a measured value back to the token it should have been. Load when checking rendered UI against a design reference.
backend-dotnet
.NET backend stack conventions — MVC controllers, Razor server-side ownership, dotnet build specifics. Load when the resolved backend stack is dotnet. If the project also uses Optimizely CMS, also load `cms-optimizely`.
zion-review
Review a PR, branch or working diff in this repo against its own rubric, run the repo's checks, and reproduce each finding before reporting it. Use when asked to review code or a PR in Zion.
backend-node
Node backend stack conventions — service framework conventions (NestJS/Express/Fastify), headless CMS/Graph client usage, npm/pnpm/yarn workspace awareness. Load when the resolved backend stack is node.
context-discipline
Token/context discipline — process large data with code and surface only the answer, never read raw bulk output into context. Preload into agents that run verbose commands (tests, builds, log/data analysis). Use whenever about to read a large file, command output, or big API/tool response.
frontend-headless
Conventions for decoupled/headless frontends — a React SPA (or Next.js) consuming Optimizely's Content Delivery API / Optimizely Graph (GraphQL) rather than Razor server rendering. Use for tasks involving a headless/decoupled Optimizely frontend, Content Delivery API or Optimizely Graph, or a React/Next.js SPA against a CMS. Load when the repo's frontend mode is "headless".
frontend-nextjs
Next.js frontend stack conventions — App Router, Server/Client Components, data fetching (e.g. Optimizely Graph), npm build specifics. Load when the resolved frontend stack is nextjs.
frontend-server-rendered
Conventions for server-rendered frontends — a server template renders the page shell, with a client-side framework layered in as islands/widgets rather than a full SPA. Covers Razor (.NET/Optimizely) and Blade (Laravel). Next.js/RSC is not covered here — crew's mode vocabulary treats Next.js as headless (see frontend-nextjs) even though it server-renders. Load when the repo's frontend mode is "server-rendered".
tests-cypress
Cypress test conventions — e2e spec writing and component testing. Load when the resolved frontend e2e tool is cypress, or when cypress is the resolved frontend unit test tool.
tests-jest-frontend
Jest frontend component/unit test conventions — test authoring with React Testing Library, mocking patterns, and running. Load when the resolved frontend unit test tool is jest.
tests-node
Node backend test conventions — Vitest or Jest, detected by config file (vitest.config.* vs jest.config.*/package.json "jest" key). Load when the resolved backend stack is node.
tests-playwright
Playwright e2e test conventions — spec writing, fixture/mock patterns, and running. Load when the resolved frontend e2e tool is playwright.
tests-vitest
Vitest component/unit test conventions — test authoring with React Testing Library, mocking patterns, and running. Load when the resolved frontend unit test tool is vitest.
operator-voice
ASD-STE-100 (Simplified Technical English) for operator-facing messages — short sentences, active voice, one term per thing, exact numbers. Preload into agents that report to the operator directly (plans, gates, summaries, blockers). Use whenever writing a message the operator reads to make a decision.
tests-xunit
.NET backend test conventions — xUnit test authoring and running, integration tests for the .NET layer. Load when the resolved backend stack is dotnet.
frontend-react
React frontend stack conventions — React, Redux (slices/selectors), vanilla JS, HTML, SCSS/CSS, Vite/npm build specifics. Load when the resolved frontend stack is react.
cms-optimizely
Optimizely CMS conventions — content types, blocks, IContentRepository, scheduled jobs, init modules. Composes on top of `backend-dotnet`; load additionally when the project references EPiServer.CMS/Optimizely.CMS.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.