Claude Launchpad

Getting Started

Install Claude Launchpad and score your Claude Code setup in 10 seconds.

Install

npm i -g claude-launchpad
pnpm add -g claude-launchpad
yarn global add claude-launchpad

Or run directly without installing:

npx claude-launchpad

Claude Launchpad has 4 CLI commands (init, doctor, eval, memory) and 2 skills (/lp-enhance, /lp-migrate-memory). Memory is optional.

New project

Scaffold

claude-launchpad init

Generates baseline config files in-project (CLAUDE.md, TASKS.md, .claude/settings.json) and creates .claudeignore, .claude/.gitignore, and .claude/rules/conventions.md when missing. It also offers /lp-enhance install (project/global/skip) when not already installed.

Diagnose + fix

claude-launchpad doctor --fix

Catches anything init missed and auto-fixes it.

Let Claude perfect it

/lp-enhance

Inside Claude Code, run the skill. Claude reads your codebase, restructures CLAUDE.md, and fills in architecture, conventions, and guardrails with real content.

Prove it works

claude-launchpad eval

15 scenarios test if Claude actually follows your rules.

Existing project

See your score

cd your-project
claude-launchpad

A typical unconfigured project scores ~42%.

Fix the structure

claude-launchpad doctor --fix

Adds missing hooks/rules/sections, security defaults, and creates /lp-enhance only when no project/global/legacy install already exists. Jumps to ~86%.

Let Claude clean it up

/lp-enhance

Inside Claude Code, type /lp-enhance. The fixer appends sections mechanically - the skill has Claude restructure and rewrite CLAUDE.md into clean, project-specific content.

Prove it works

claude-launchpad eval

Keep your config healthy

init runs once. doctor, /lp-enhance, and eval are designed for repeat use as your project evolves. memory is optional and can be installed whenever you want persistent context.

WhenRun
Added dependencies, changed frameworks, modified hooksdoctor --fix
Major refactor, new modules, CLAUDE.md feels stale/lp-enhance
Before a release, after config changes, Claude ignoring ruleseval
You want cross-session memory with local SQLite + MCP toolsmemory

Your codebase changes. Your config should keep up. Run doctor periodically. If the score drops, --fix and /lp-enhance bring it back.

Command Map (details in each command page)

Use this as a quick map; each command page covers full flags and workflows.

CommandWhat it doesRuns
claude-launchpad initDetect stack, generate config, hooks, permissionsLocally
claude-launchpadScore your config 0-100, list issuesLocally
claude-launchpad doctor --fixAuto-fix issues: hooks, rules, sections, .claudeignoreLocally
claude-launchpad doctor --watchLive score that updates when you save config filesLocally
/lp-enhance (skill)Claude reads your code and completes CLAUDE.mdInside Claude Code
claude-launchpad evalRun Claude against test scenarios, prove config worksVia Claude CLI
claude-launchpad memorySet up persistent memory, MCP tools, and /lp-migrate-memory skillLocally
claude-launchpad memory --dashboardTUI dashboard for memory visualizationLocally

Commands marked Locally run offline with zero API calls. Commands marked Via Claude CLI require Claude Code installed and authenticated. Memory is optional - install only if you want persistent context across sessions.

Next Steps

On this page