Skip to content
PopKit Documentation

Quick Start

Quick Start

Section titled “Quick Start”

This guide helps you get PopKit running in the host you already use.

Prerequisites

Section titled “Prerequisites”
  • Claude Code 2.1.33 or higher for plugin installs, or an MCP-compatible client for popkit-mcp
  • Python 3.11+ for PyPI/MCP installs
  • Git installed
  • Node.js 18+ only if you are developing PopKit itself

Pick Your Install Path

Section titled “Pick Your Install Path”
HostInstall pathFirst validation step
Claude CodeClaude Code pluginRun /popkit-dev:next
VS Code / GitHub CopilotVS Code MCP setupAsk Copilot Chat: Use PopKit health_check and summarize the result.
CursorCursor MCP setupStart popkit-mcp --transport stdio through Cursor
Codex CLICodex MCP setupStart popkit-mcp --transport stdio through Codex
Generic MCP clientMCP provider setupConfigure popkit-mcp as a stdio MCP server

First Steps

Section titled “First Steps”

After installing PopKit, run the validation step for your host. Then try the workflow entry point that matches your surface.

Claude Code: Check Your Project Status

Section titled “Claude Code: Check Your Project Status”
Terminal window
/popkit-dev:next

This command analyzes your project state and recommends context-aware next actions.

Claude Code: Run Morning Routine

Section titled “Claude Code: Run Morning Routine”
Terminal window
/popkit-dev:routine morning

Get a comprehensive project health check with “Ready to Code” score.

Claude Code: Try a Feature Workflow

Section titled “Claude Code: Try a Feature Workflow”
Terminal window
/popkit-dev:dev "Add user authentication"

Guided 7-phase feature development workflow from discovery to implementation.

MCP Clients: Start With Health Check

Section titled “MCP Clients: Start With Health Check”
Use PopKit health_check and summarize the result.

Once the MCP server is connected, use the listed PopKit tools for handoffs, recommendations, and package-aware workflows. Tool names and availability depend on the installed PopKit MCP version, so use the client’s tool list as the source of truth.

Key Commands

Section titled “Key Commands”

Claude Code exposes PopKit as slash commands:

CommandDescription
/popkit-dev:nextGet context-aware next actions
/popkit-dev:git commitSmart git commit with auto-generated messages
/popkit-dev:git prCreate pull request with comprehensive summary
/popkit-dev:routine morningMorning health check and setup
/popkit-dev:routine nightlyEnd-of-day cleanup and summary

Next Steps

Section titled “Next Steps”