Use this skill when the user mentions "mastermind", "track projects", "project overview", "sync sessions", "project progress", or wants to manage multiple ongoing projects from a central location.
Tracks multiple project progress by analyzing Claude Code sessions and generating reports.
npx claudepluginhub mconcat/mastermindThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/report-properties.mdreferences/vault-structure.mdUse this skill when the user mentions "mastermind", "track projects", "project overview", "sync sessions", "project progress", or wants to manage multiple ongoing projects from a central location.
Trust the specifications. Do NOT verify documented structures.
All mastermind commands include complete specifications for:
When executing a command:
Anti-patterns:
head/grep to "understand" file formats already documentedls to "discover" directory structures already specifiedThe specifications are authoritative. If something doesn't match, report the discrepancy - don't try to "figure out" the actual format through exploration.
Mastermind is a markdown-based framework for tracking progress across multiple projects via Claude Code session analysis. It maintains a central "vault" with project specs, session reports, and daily digests.
Vault: The mastermind directory containing all tracking data. Location configured in ~/.claude/mastermind.local.md.
Projects: Registered directories that mastermind monitors for Claude Code session activity.
Session Reports: Property-based narrative reports generated from Claude Code conversation history, capturing decisions, issues, learnings, and user preferences.
Specs: Source-of-truth documents defining each project's purpose, scope, and direction.
[vault]/
├── config.yaml # Project registry
├── state/
│ └── sync-state.yaml # Sync tracking (last synced timestamps)
├── projects/
│ └── [project-name]/
│ ├── spec.md # Project specification
│ ├── status.md # Current state summary
│ └── sessions/
│ └── YYYY-MM-DD-descriptive-title.md # Session reports
└── daily/
└── [YYYY-MM-DD].md # Cross-project daily digests
Session filename format: YYYY-MM-DD-descriptive-title.md
2026-01-15-implementing-jwt-authentication.md| Command | Purpose |
|---|---|
/mm:init <vault-path> | Initialize a new vault (first-time setup) |
/mm:add <name> <path> | Register a new project to monitor |
/mm:sync [project] | Analyze new Claude Code sessions and generate reports |
/mm:overview | Dashboard of all monitored projects |
/mm:status <project> | Deep dive on one project |
/mm:plan [project] | Create or update a project spec |
/mm:daily | Generate today's cross-project digest |
/mm:init ~/path/to/vault/mm:add my-project /path/to/project/mm:sync/mm:plan my-projectThe vault path is stored in ~/.claude/mastermind.local.md (created by /mm:init):
# Mastermind Configuration
vault: /path/to/your/mastermind/vault
All commands work from any directory - they read the vault location from this config file.
Reports are narrative documents (like blog posts) that capture these properties when present:
/mm:init ~/your/vault to create vault/mm:add <name> <path> for each project to track/mm:sync (from any directory)/mm:plan/mm:dailyFor detailed specifications, see:
references/vault-structure.md - Complete vault formatreferences/report-properties.md - Session report property definitionsExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.