Claude Night Market
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
<p align="center"> <img src="assets/gifs/skills-showcase.gif" alt="Night Market skills in action" width="720"> </p>Install
Requires Claude Code 2.1.16+ and Python 3.9+ for hooks.
# Add the marketplace, then install the plugins you want
/plugin marketplace add athola/claude-night-market
/plugin install sanctum@claude-night-market # Git workflows
/plugin install pensive@claude-night-market # Code review
/plugin install spec-kit@claude-night-market # Spec-driven devRun claude --init once after installing. Prefer one command?
npx skills add athola/claude-night-market installs everything;
opkg i gh@athola/claude-night-market --plugins sanctum,pensive
installs a subset. Full options are in the
Installation Guide.
If the
Skilltool is unavailable, read skill files directly atplugins/{plugin}/skills/{skill-name}/SKILL.md.
Everyday Use
Night Market is built around the loop you already work in. A typical feature runs end to end on a handful of commands:
- Start a feature.
/attune:missionroutes you through brainstorm, specify, plan, and execute phases. - Write the code.
imbueenforces a failing test first, so implementation follows the test, not the other way around. - Review before you push.
/full-reviewruns a multi-discipline pass;/refine-codecleans up duplication and dead code. - Ship it.
/prepare-prruns quality gates and leaves a clean git state ready for a pull request. - Pick up where you left off.
/catchuprebuilds context from recent git history after a break.
The commands you reach for most:
| Task | Command |
|---|---|
| Run the project lifecycle | /attune:mission |
| Initialize a new project | /attune:arch-init |
| Review a PR | /full-review |
| Address review feedback | /fix-pr |
| Implement an issue | /do-issue |
| Prepare a pull request | /prepare-pr |
| Write a spec | /speckit-specify |
| Catch up on changes | /catchup |
| Clean up the codebase | /unbloat |
| Pressure-test a decision | /attune:war-room |
Full task-by-task walkthroughs are in the Common Workflows Guide.
What's Inside
23 plugins in four layers. Each installs independently, and dependencies pull their shared runtime automatically.
Foundation is the base every other layer builds on:
leyline (auth, quotas, error patterns, trust verification),
sanctum (git, commits, PR prep, sessions), and imbue
(TDD enforcement, proof-of-work, scope guarding).
Utility handles cross-cutting concerns: conserve (context
and token optimization), conjure (delegation to Gemini and
Qwen), hookify (a behavioral rules engine with a security
catalog), egregore (autonomous agent orchestration),
herald (notifications), and oracle (local ML inference).
Domain is where the day-to-day work happens: pensive (code
and architecture review), attune (project lifecycle), spec-kit
(spec-driven development), parseltongue (Python), minister
(GitHub issues and DORA metrics), memory-palace (knowledge
organization), archetypes (architecture paradigms), gauntlet
(codebase learning), phantom (computer use), scribe
(documentation and slop detection), scry (recordings), tome
(research), and cartograph (codebase visualization).
Meta improves the system itself: abstract (skill authoring,
hook development, evaluation, and skill-stability tracking).
The full skill, command, and agent inventory is in the Capabilities Reference.
Safety
⚠️ Plugins run inside your Claude Code session and can read or edit your repo, run shell commands, and call external services. Review any plugin before installing it.
Three guards reduce the blast radius, but none replace your own review:
- TDD gates (
imbue) block implementation writes that lack a failing test. - Destructive-command blockers (
conserve,hookify) auto-approve safe commands and halt or warn onrm -rf,git push --force, and production-shaped targets. - Additive-bias audits (
leyline) flag unjustified additions before commit.
CONSTITUTION.md holds the immutable rules that override any conflicting skill or hook; STEWARDSHIP.md is the maintenance contract.
Requirements
- Claude Code 2.1.16+ (2.1.32+ for agent teams, 2.1.38+ for security features).
- Python 3.9+ for hooks (macOS ships 3.9.6). Hook code must stay 3.9-compatible; plugin packages may target 3.10+ via virtual environments. See the Plugin Development Guide for the rules.
What's New
1.9.11 adds the tome:ideate skill for diverse solution
ideation with category rotation, grounds the tome:triz channel in
the canonical TRIZ method, normalizes British spellings to American
in the scribe slop workflow, and adds a grounded-evidence review
contract: every review finding now carries a verbatim source anchor
that citation_verifier.py re-reads, so a finding cannot cite code
that was never there.
See the CHANGELOG for the full history.
Plugin Development
make create-plugin NAME=my-plugin
make validate
make lint && make testA plugin directory holds .claude-plugin/plugin.json (metadata)
plus any of commands/, skills/, hooks/, agents/, and
tests/, with a Makefile and pyproject.toml. See the
Plugin Development Guide for structure and naming
conventions.
Documentation
- Installation Guide
- Quick Start
- Common Workflows
- Plugin Development Guide
- Capabilities Reference
- Tutorials
- Architecture Decision Records
Per-plugin pages are in book/src/plugins/.
Stewardship and Contributing
Every plugin is entrusted to the community: steward rather than
own, and think several iterations ahead. Each plugin maintains
its own tests and docs; run make test at the repo root to
execute every suite, and /stewardship-health to view per-plugin
health. Contribution guidelines live in the
Plugin Development Guide.
Acknowledgements
Night Market builds on Anthropic Claude Code and
integrates with github/spec-kit (v0.5.0),
obra/superpowers (v5.0.7, see the
integration guide), and three patterns adapted
from QAInsights/Quillx. Per-plugin attributions are in
each plugin's pyproject.toml.