Examples
Concrete install and refresh commands for Token Kits across supported IDEs.
Cursor
cd your-project
npx github:mattmerrick/cursorthings --ide cursor
Writes: .cursor/rules/token-kit.mdc
Windsurf
npx github:mattmerrick/cursorthings --ide windsurf
Writes: .windsurfrules
Claude Code
npx github:mattmerrick/cursorthings --ide claude
Writes: .claude/rules/token-kit.md
GitHub Copilot
npx github:mattmerrick/cursorthings --ide copilot
Writes: .github/instructions/token-kit.instructions.md
Cline
npx github:mattmerrick/cursorthings --ide cline
Writes: .clinerules/token-kit.md
Universal AGENTS.md
npx github:mattmerrick/cursorthings --ide agents
Writes: AGENTS.md (useful for tools that read a project-level agents file)
Zed
npx github:mattmerrick/cursorthings --ide zed
Writes: .rules/token-kit.md
Aider
npx github:mattmerrick/cursorthings --ide aider
Writes: CONVENTIONS.md
Refresh the pack
Pull the latest pack/token-kit.md into your IDE path:
npx github:mattmerrick/cursorthings pack --force --ide cursor
Change --ide to match the editor you installed for.
Typical workflow after install
- Open a focused task (bug fix or small feature)
- Let the pack enforce budgets — don’t
@Folderwhole trees - Prefer asking for one specific path when more context is needed
- Expect short plans, edits, and a single verify step