How do I install the Config Setup skill?

Run npx skillmds@latest add jordancoin/config-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Config Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Config Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Config Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Config Setup?

jordancoin (@jordancoin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Config Setup by jordancoin — Agent Skill

Name: Config Setup
Author: jordancoin

File contents

Codemap Config Setup

Goal

Write or improve .codemap/config.json so future Codemap calls stay focused on the code that matters for this repo.

Use this when

.codemap/config.json is missing
The existing config looks like a bare bootstrap instead of a real project policy
Codemap output is dominated by assets, fixtures, generated files, vendor trees, PDFs, screenshots, models, or training data
The project stack is obvious, but Codemap is not prioritizing the right parts of the repo

Workflow

Inspect the repo quickly before writing config
- Run codemap .
- If needed, run codemap --deps .
- Note the stack markers (Cargo.toml, Package.swift, *.xcodeproj, go.mod, package.json, pyproject.toml, etc.)
- Identify large non-code directories and noisy extensions
Decide whether config is missing, boilerplate, or tuned
- Missing: no .codemap/config.json
- Boilerplate: only generic only values, no real shaping, no excludes despite obvious noise
- Tuned: contains intentional project-specific includes/excludes, depth, or routing hints
Write a conservative code-first config
- Keep primary source-language only values when they help
- Add exclude entries for obvious non-code noise
- Set a moderate depth when the repo is broad
- Avoid overfitting or excluding real source directories
Prefer stack-aware defaults
- Rust: focus src, tests, benches, examples; de-prioritize corpora, sample PDFs, training data, large generated artifacts
- iOS/Swift: focus app/framework source, tests, package/project manifests; de-prioritize .xcassets, screenshots, snapshots, vendor/build outputs
- TS/JS: focus src, apps, packages, tests; de-prioritize dist, coverage, Storybook assets, large fixture payloads
- Python: focus package roots, tests, tool config; de-prioritize notebooks, data dumps, models, fixtures when they overwhelm code
- Go: focus packages, cmd, internal, tests; de-prioritize generated assets, sample data, vendor-like noise
Preserve user intent
- If config already looks curated, do not replace it wholesale
- Make minimal edits and explain why
Verify immediately
- Rerun codemap .
- If the repo still looks noisy, refine exclude and possibly depth
- Only rerun codemap --deps . after tree output looks reasonable

---name: config-setupdescription: Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo. Use when config is missing, boilerplate, noisy, or mismatched to the stack.---# Codemap Config Setup## GoalWrite or improve `.codemap/config.json` so future Codemap calls stay focused on the code that matters for this repo.## Use this when1. `.codemap/config.json` is missing2. The existing config looks like a bare bootstrap instead of a real project policy3. Codemap output is dominated by assets, fixtures, generated files, vendor trees, PDFs, screenshots, models, or training data4. The project stack is obvious, but Codemap is not prioritizing the right parts of the repo## Workflow1. Inspect the repo quickly before writing config - Run `codemap .` - If needed, run `codemap --deps .` - Note the stack markers (`Cargo.toml`, `Package.swift`, `*.xcodeproj`, `go.mod`, `package.json`, `pyproject.toml`, etc.) - Identify large non-code directories and noisy extensions2. Decide whether config is missing, boilerplate, or tuned - Missing: no `.codemap/config.json` - Boilerplate: only generic `only` values, no real shaping, no excludes despite obvious noise - Tuned: contains intentional project-specific includes/excludes, depth, or routing hints3. Write a conservative code-first config - Keep primary source-language `only` values when they help - Add `exclude` entries for obvious non-code noise - Set a moderate `depth` when the repo is broad - Avoid overfitting or excluding real source directories4. Prefer stack-aware defaults - Rust: focus `src`, `tests`, `benches`, `examples`; de-prioritize corpora, sample PDFs, training data, large generated artifacts - iOS/Swift: focus app/framework source, tests, package/project manifests; de-prioritize `.xcassets`, screenshots, snapshots, vendor/build outputs - TS/JS: focus `src`, `apps`, `packages`, `tests`; de-prioritize `dist`, `coverage`, Storybook assets, large fixture payloads - Python: focus package roots, tests, tool config; de-prioritize notebooks, data dumps, models, fixtures when they overwhelm code - Go: focus packages, cmd, internal, tests; de-prioritize generated assets, sample data, vendor-like noise5. Preserve user intent - If config already looks curated, do not replace it wholesale - Make minimal edits and explain why6. Verify immediately - Rerun `codemap .` - If the repo still looks noisy, refine `exclude` and possibly `depth` - Only rerun `codemap --deps .` after tree output looks reasonable

Frequently asked questions

Config Setup