Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Quick Start Guide

Common workflows and patterns for Claude Night Market plugins.

Workflow Recipes

Feature Development

Start features with a specification:

# (Optional) Resume persistent speckit context for this repo/session
/speckit-startup

# Create specification from idea
/speckit-specify Add user authentication with OAuth2

# Generate implementation plan
/speckit-plan

# Create ordered tasks
/speckit-tasks

# Execute tasks
/speckit-implement

# Verify artifacts stay consistent
/speckit-analyze

Code Review

Run a detailed code review:

# Full review with intelligent skill selection
/full-review

# Or specific review types
/architecture-review    # Architecture assessment
/api-review            # API surface evaluation
/bug-review            # Bug hunting
/test-review           # Test quality
/rust-review           # Rust-specific (if applicable)

Context Recovery

Get up to speed on changes:

# Quick catchup on recent changes
/catchup

# Or with sanctum's git-specific variant
/git-catchup

Context Optimization

Monitor and optimize context usage:

# Analyze context window usage
/optimize-context

# Check skill growth patterns
/analyze-growth

Skill Invocation Patterns

Basic Skill Usage

# Standard format
Skill(plugin:skill-name)

# Examples
Skill(sanctum:git-workspace-review)
Skill(imbue:diff-analysis)
Skill(conservation:context-optimization)

Skill Chaining

Some skills depend on others:

# Pensive depends on imbue and sanctum
Skill(sanctum:git-workspace-review)
Skill(imbue:review-core)
Skill(pensive:architecture-review)

Skill with Dependencies

Check a plugin’s README for dependency chains:

spec-kit depends on imbue
pensive depends on imbue + sanctum
sanctum depends on imbue (for some skills)

Command Quick Reference

Git Operations (sanctum)

CommandPurpose
/commit-msgGenerate commit message
/prPrepare pull request
/fix-prAddress PR review comments
/do-issueFix GitHub issues
/update-docsUpdate documentation
/update-readmeModernize README
/update-testsMaintain tests
/update-versionBump versions

Specification (spec-kit)

CommandPurpose
/speckit-specifyCreate specification
/speckit-planGenerate plan
/speckit-tasksCreate tasks
/speckit-implementExecute tasks
/speckit-analyzeCheck consistency
/speckit-clarifyAsk clarifying questions

Review (pensive)

CommandPurpose
/full-reviewUnified review
/architecture-reviewArchitecture check
/api-reviewAPI surface review
/bug-reviewBug hunting
/test-reviewTest quality

Analysis (imbue)

CommandPurpose
/catchupQuick context recovery
/structured-reviewStructured review with evidence
/feature-reviewFeature prioritization

Plugin Management (leyline)

CommandPurpose
/reinstall-all-pluginsRefresh all plugins
/update-all-pluginsUpdate all plugins

Environment Variables

Some plugins support configuration via environment variables:

Conservation

# Skip optimization guidance for fast processing
CONSERVATION_MODE=quick claude

# Full guidance with extended allowance
CONSERVATION_MODE=deep claude

Memory Palace

# Set embedding provider
MEMORY_PALACE_EMBEDDINGS_PROVIDER=hash  # or local

Tips

1. Start with Foundation

Install foundation plugins first:

/plugin install imbue@claude-night-market
/plugin install sanctum@claude-night-market

Then add domain specialists as needed.

2. Use TodoWrite Integration

Most skills output TodoWrite items for tracking:

git-review:repo-confirmed
git-review:status-overview
pr-prep:quality-gates

Monitor these for workflow progress.

3. Chain Skills Intentionally

Don’t invoke all skills at once. Build understanding incrementally:

# First: understand state
Skill(sanctum:git-workspace-review)

# Then: perform action
Skill(sanctum:commit-messages)

4. Use Superpowers

If superpowers is installed, commands gain enhanced capabilities:

  • /create-skill uses brainstorming
  • /test-skill uses TDD methodology
  • /pr uses code review patterns

Next Steps