git-workflow
Git best practices for version control and collaboration
api-designer
Design RESTful APIs with best practices for consistency and usability
coding-assistant
Provides coding assistance with best practices and code review
debug-helper
Systematic debugging approach for identifying and fixing issues
test-writer
Write thorough tests following TDD and BDD principles
html-portal-generator
Convert a codebase into a self-contained HTML portal app for ingestion into AI application systems. Produces a single deployable HTML file with embedded CSS, JS, and data.
claude-code-plugin-reference
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
night-market-architecture-contract
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use night-market-change-control.
night-market-build-and-env
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.
night-market-change-control
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use night-market-debugging-playbook.
night-market-collective-memory
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.
night-market-completion-integrity-campaign
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.
night-market-config-catalog
Catalog every config axis, its defaults and guards. Use when adding or auditing configuration. Do not use for running gates; use night-market-operations.
night-market-debugging-playbook
Triage night-market failures by symptom (hooks, CI, tests). Use when a check fails unexpectedly. Do not use for routine gates; use night-market-operations.
night-market-diagnostics-toolkit
Run and interpret repo diagnostic scripts (ratchets, validators, token stats). Use when measuring health. Do not use to run tests; use night-market-operations.
night-market-docs-and-writing
Maintain docs of record, ADRs, changelog, and house style. Use when writing repo docs. Do not use for release steps; use night-market-operations instead.
night-market-failure-archaeology
Chronicles settled battles, reverts, and dead ends. Use when a fix echoes a past failure. Do not use for live triage; use night-market-debugging-playbook.
night-market-model-and-harness-updates
Sweep plugins, skills, agents, commands, and hooks after a model release or Claude Code version bump. Use when upstream ships. Do not use for routine edits; use night-market-change-control.
night-market-operations
Run and ship this repo: make targets, artifacts, release runbook. Use when testing, linting, or releasing. Do not use for setup; use night-market-build-and-env.
night-market-research-frontier
Map open problems where this repo can advance SOTA. Use when scoping research. Do not use to run the campaign; use night-market-completion-integrity-campaign.
night-market-research-methodology
Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
night-market-validation-and-qa
Enforce evidence bar, coverage gates, and regression guards. Use when adding tests or claiming done. Do not use to run suites; use night-market-operations.
friction-detector
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
hook-scope-guide
Select hook scope (plugin, project, global) by audience. Use when authoring a hook.
skill-graph-audit
Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.
architecture-paradigm-domain-driven
Models a business in its own language. Use when the domain has real business rules to capture.
architecture-paradigm-functional-core
Applies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.
architecture-paradigm-hexagonal
Applies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.
architecture-paradigm-layered
Applies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.
architecture-paradigm-microkernel
Applies microkernel architecture with minimal core and plugin extensibility. Use when building platforms where third parties extend core functionality.
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
architecture-paradigm-modular-monolith
Applies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.
architecture-paradigm-pipeline
Applies pipes-and-filters for sequential data transformations. Use when data flows through discrete stages like ETL, streaming analytics, or CI/CD pipelines.
architecture-paradigm-serverless
Applies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.
architecture-paradigm-service-based
Applies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.
architecture-paradigm-space-based
Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.
architecture-paradigms
Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.
architecture-aware-init
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
makefile-generation
Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.
mission-orchestrator
Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase. Use when starting or resuming a project mid-workflow.
precommit-setup
Configures pre-commit hooks for linting, type checking, formatting, and testing. Use when setting up a new project or adding quality gates to an existing one.
project-brainstorming
Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
project-init
Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.
project-planning
Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
project-specification
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
skill-library-mission
Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review. Use when packaging tribal knowledge. Do not use for one skill.
war-room-checkpoint
Assesses decision reversibility and risk at critical checkpoints. Use when a workflow reaches a high-stakes branch needing escalation check.
war-room
Convenes a multi-LLM expert panel to pressure-test hard-to-reverse decisions. Use when reversibility score is low and adversarial review is warranted.
Page 1 of 5 · 232 results