User Input:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmcp:setup-codemap-cliExecute the skills CLI command in your project's root directory to begin installation:
Fetches mcp:setup-codemap-cli from neolabhq/context-engineering-kit and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate mcp:setup-codemap-cli. Access via /mcp:setup-codemap-cli in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
757
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
757
stars
User Input:
$ARGUMENTS
Ask the user where they want to store the configuration:
Options:
Project level (shared via git) - Configuration tracked in version control, shared with team
./CLAUDE.md./.claude/settings.jsonProject level (personal preferences) - Configuration stays local, not tracked in git
./CLAUDE.local.md./.claude/settings.local.json.gitignore, add them if notUser level (global) - Configuration applies to all projects for this user
~/.claude/CLAUDE.md~/.claude/settings.jsonStore the user's choice and use the appropriate paths in subsequent steps.
Check whether codemap is installed by running codemap -help.
If not installed, proceed with setup.
Read the following documentation to understand Codemap's capabilities:
brew tap JordanCoin/tap && brew install codemap
scoop bucket add codemap https://github.com/JordanCoin/scoop-codemap
scoop install codemap
After installation, verify codemap works:
codemap .
Use the path determined in step 1. Once Codemap is successfully installed, update the appropriate CLAUDE.md file with the following content:
## Use Codemap CLI for Codebase Navigation
Codemap CLI is available for intelligent codebase visualization and navigation.
**Required Usage** - You MUST use `codemap --diff --ref master` to research changes different from default branch, and `git diff` + `git status` to research current working state.
### Quick Start
```bash
codemap . # Project tree
codemap --only swift . # Just Swift files
codemap --exclude .xcassets,Fonts,.png . # Hide assets
codemap --depth 2 . # Limit depth
codemap --diff # What changed vs main
codemap --deps . # Dependency flow
| Flag | Description |
|---|---|
--depth, -d <n> |
Limit tree depth (0 = unlimited) |
--only <exts> |
Only show files with these extensions |
--exclude <patterns> |
Exclude files matching patterns |
--diff |
Show files changed vs main branch |
--ref <branch> |
Branch to compare against (with --diff) |
--deps |
Dependency flow mode |
--importers <file> |
Check who imports a file |
--skyline |
City skyline visualization |
--json |
Output JSON |
Smart pattern matching - no quotes needed:
.png - any .png fileFonts - any /Fonts/ directory*Test* - glob patternSee what you're working on:
codemap --diff
codemap --diff --ref develop
if the default branch is not `main`, but instead `master` (or something else) update content accordingly:
- use `codemap --diff --ref master` instead of regular `codemap --diff`
## 7. Update .gitignore file
Update .gitignore file to include `.codemap/` directory:
```text
.codemap/
Run a quick test to verify everything works:
codemap .
codemap --diff
Use the settings path determined in step 1. Create the settings file if it doesn't exist and add the following content:
{
"hooks": {
"session-start": "codemap hook session-start && echo 'git diff:' && git diff --stat && echo 'git status:' && git status"
}
}
if default branch is not main, but instead master (or something else) update content accordingly:
codemap hook session-start --ref=master instead of regular codemap hook session-start--ref=master flag.Ask user whether he want to add any other hooks and provide list of options with descriptions. Add hooks that he asks for.
| Command | Trigger | Description |
|---|---|---|
codemap hook session-start |
SessionStart | Full tree, hubs, branch diff, last session context |
codemap hook pre-edit |
PreToolUse (Edit|Write) | Who imports file + what hubs it imports |
codemap hook post-edit |
PostToolUse (Edit|Write) | Impact of changes (same as pre-edit) |
codemap hook prompt-submit |
UserPromptSubmit | Hub context for mentioned files + session progress |
codemap hook pre-compact |
PreCompact | Saves hub state to .codemap/hubs.txt |
codemap hook session-stop |
SessionEnd | Edit timeline with line counts and stats |
{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "codemap hook session-start"
}
]
}
],
"PreToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "codemap hook pre-edit"
}
]
}
],
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "codemap hook post-edit"
}
]
}
],
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "codemap hook prompt-submit"
}
]
}
],
"PreCompact": [
{
"hooks": [
{
"type": "command",
"command": "codemap hook pre-compact"
}
]
}
],
"SessionEnd": [
{
"hooks": [
{
"type": "command",
"command": "codemap hook session-stop"
}
]
}
]
}
}
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mcp:setup-codemap-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend mcp:setup-codemap-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
mcp:setup-codemap-cli reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in mcp:setup-codemap-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: mcp:setup-codemap-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
mcp:setup-codemap-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: mcp:setup-codemap-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
mcp:setup-codemap-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for mcp:setup-codemap-cli matched our evaluation — installs cleanly and behaves as described in the markdown.
We added mcp:setup-codemap-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 61