Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By athola
Generate Mermaid diagrams of your codebase—architecture, data flows, dependency graphs, call chains, class hierarchies, and workflows—by analyzing modules and imports in Python, JS/TS, and Rust projects.
npx claudepluginhub athola/claude-night-market --plugin cartographGenerate Mermaid architecture diagrams from codebase structure. Use for onboarding, PR reviews.
Trace execution paths from entry points through the code knowledge graph. Shows call chains with criticality scores and generates Mermaid flowcharts.
Generate class diagrams showing classes, interfaces, inheritance, and composition
Detect architectural clusters in the codebase using community detection on the code knowledge graph. Shows module boundaries, cohesion, and coupling warnings.
Generate Mermaid data flow diagrams showing how data moves between components. Use for tracing requests and API call chains.
Executes bash commands
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Diagrams-as-code tools for visualizing code, data, and systems using Mermaid and PlantUML
Generate, validate, render Mermaid diagrams from text or code
Excalidraw diagramming toolkit — auto-diagram any codebase, architecture diagrams, data flows, with PNG/SVG/URL export
General development utilities including Mermaid diagram creation for software documentation
Analyzes a codebase and generates animated HTML architecture reports — diagrams, data flows, component directories, metrics, and insights.
MCP server for previewing Mermaid diagrams in Claude Code
Autonomous agent orchestrator for full development lifecycles with zero human input, session budget management, and crash recovery
Documentation review, cleanup, and generation with AI slop detection, style learning, and human-quality writing enforcement
Media generation capabilities for terminal recordings (VHS), browser recordings (Playwright), GIF processing, and media composition
Git and workspace operations for active development workflows - commit messages, PR prep, documentation updates, and version management
Modern Python development suite - testing, performance optimization, async patterns, and packaging
A plugin marketplace for Claude Code, Anthropic's agentic coding tool.
Night Market extends Claude Code with 23 plugins covering git workflows, code review, spec-driven development, architecture selection, codebase visualization, autonomous agents, multi-LLM delegation, ML-enhanced scoring, and multi-source research. 161 skills, 146 slash commands, and 50 agents. Each plugin installs independently.
Requires Claude Code 2.1.16+ and Python 3.9+ for hooks. See Requirements for details.
# Add the marketplace
/plugin marketplace add athola/claude-night-market
# Install plugins you need
/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 dev
# Use them
/prepare-pr # Prepare a pull request
/full-review # Run code review
Alternative: Install via npx with
npx skills add athola/claude-night-market (installs all plugins at once).
After installation, run claude --init for one-time setup.
Note: If the
Skilltool is unavailable, read skill files directly atplugins/{plugin}/skills/{skill-name}/SKILL.md.
# Install specific plugins
opkg i gh@athola/claude-night-market --plugins sanctum
opkg i gh@athola/claude-night-market --plugins pensive,conserve
# Plugins that depend on shared runtime skills (e.g. attune, conjure)
# automatically pull packages/core as a dependency
See the Installation Guide for detailed setup options.
23 plugins organized in four layers. Domain specialists depend on utility plugins, which depend on foundation plugins, which depend on the meta layer.
flowchart TB
classDef domainClass fill:#e8f4f8,stroke:#2980b9,stroke-width:2px,color:#2c3e50
classDef utilityClass fill:#f8f4e8,stroke:#f39c12,stroke-width:2px,color:#2c3e50
classDef foundationClass fill:#f4e8f8,stroke:#8e44ad,stroke-width:2px,color:#2c3e50
classDef metaClass fill:#e8f4e8,stroke:#27ae60,stroke-width:2px,color:#2c3e50
subgraph Domain["Domain Specialists"]
direction LR
D1[archetypes]:::domainClass
D2[pensive]:::domainClass
D3[parseltongue]:::domainClass
D4[memory-palace]:::domainClass
D5[spec-kit]:::domainClass
D6[minister]:::domainClass
D7[attune]:::domainClass
D8[scry]:::domainClass
D9[scribe]:::domainClass
D10[tome]:::domainClass
D11[gauntlet]:::domainClass
D12[cartograph]:::domainClass
end
subgraph Utility["Utility Layer"]
direction LR
U1[conserve]:::utilityClass
U2[conjure]:::utilityClass
U3[hookify]:::utilityClass
U4[egregore]:::utilityClass
U5[herald]:::utilityClass
U6[oracle]:::utilityClass
end
subgraph Foundation["Foundation Layer"]
direction LR
F1[imbue]:::foundationClass
F2[sanctum]:::foundationClass
F3[leyline]:::foundationClass
end
subgraph Meta["Meta Layer"]
direction LR
M1[abstract]:::metaClass
end
Domain ==> Utility ==> Foundation ==> Meta