Claude Code
Install the marketplace plugin, restart Claude Code, then run /popkit-dev:routine morning.
PopKit is a workflow layer for AI-assisted software development. It keeps the product model centered on repeatable development jobs, then exposes those jobs through the Claude Code plugin surface and the popkit-mcp server for other MCP-compatible tools.
This site is the documentation home at docs.popkit.dev. The separate public product site will live at popkit.dev.
Claude Code
Install the marketplace plugin, restart Claude Code, then run /popkit-dev:routine morning.
VS Code / Copilot
Install popkit-mcp, configure the MCP server, then ask Copilot Chat to use health_check.
Cursor / Codex CLI
Install popkit-mcp, add the client config snippet, then start popkit-mcp --transport stdio.
Standalone CLI
Install popkit[full] or popkit-cli, then run popkit --help.
Workflow Routing
PopKit turns project context into concrete next actions, routines, and feature workflows.
Provider-Neutral Surfaces
Slash commands, MCP tools, skills, agents, and output contracts let each host expose the same workflow model.
7-Phase Feature Development
Structured workflow from discovery through architecture to implementation and review.
Context Preservation
Session capture/restore skills maintain state between sessions, enabling long-running processes.
Context-aware commands recommend the next useful action, run day-bracketing routines, and route larger work into structured feature-development flows.
For Claude Code, start with:
/popkit-dev:nextFor MCP clients, start with:
Use PopKit health_check and summarize the result.Guided 7-phase process: Discovery -> Exploration -> Questions -> Architecture -> Implementation -> Review -> Summary
Unified commands for commits, PRs, and publishing to public repos with automatic context gathering.
Day-bracketing workflow with health checks and cleanup, providing “Ready to Code” and “Sleep Scores”.
PopKit is organized around:
Ready to set up PopKit?