claude-md-starter
Generates a fully structured, project-specific CLAUDE.md by scanning the repo for signal files (package.json, Makefile, .github/workflows/, .env.example, etc.), inferring stack, commands, architecture, and conventions, then asking at most 3 targeted questions for what cannot be inferred. Use whenever the user says 'create a CLAUDE.md', 'my CLAUDE.md is blank', 'generate project context', 'initialize CLAUDE.md', 'set up Claude context for this repo', 'fill in my CLAUDE.md', or any variation where someone needs their project context documented for Claude. If a CLAUDE.md already exists with conte
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill claude-md-starter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Claude.md Starter — Project Context Generator Scans the repo, infers the tech stack and conventions, asks at most 3 targeted questions, and writes a populated CLAUDE.md that gives Claude full project context from session one. ## Invocation Triggers **Explicit:** - "create a CLAUDE.md" - "my CLAUDE.md is blank" - "generate project context" - "initialize CLAUDE.md" - "set up Claude context for this repo" - "fill in my CLAUDE.md" - "run the claude-md-starter skill" **Implicit:** - User pastes a near-empty CLAUDE.md and asks Claude to populate it - User keeps re-explaining the same project context at the start of sessions Run immediately when triggered — no upfront questions before scanning. ## Workflow (6 Nodes) | Node | Role | |---|---| | 1 — Detect | Check if CLAUDE.md exists and measure content length | | 2 — Scan | Read signal files from the project root (see `references/scan-signals.md`) | | 3 — Infer | Draft all sections that can be derived from scanned signals | | 4 — Grill-me | Ask at most 3 questions for what cannot be inferred | | 5 — Generate | Write the full CLAUDE.md using the template in `references/claude-md-template.md` | | 6 — Validate | Confirm required sections ar
- Invocation Triggers
- Workflow (6 Nodes)
- Node 1 — Detect
- Node 2 — Scan
- Node 3 — Infer
- Node 4 — Grill-Me Intake
- Node 5 — Generate
- Node 6 — Validate
- Output
- Anti-Patterns To Reject
- References
What does the claude-md-starter skill do?
Generates a fully structured, project-specific CLAUDE.md by scanning the repo for signal files (package.json, Makefile, .github/workflows/, .env.example, etc.), inferring stack, commands, architecture, and conventions, then asking at most 3 targeted questions for what cannot be inferred. Use whenever the user says 'create a CLAUDE.md', 'my CLAUDE.md is blank', 'generate project context', 'initialize CLAUDE.md', 'set up Claude context for this repo', 'fill in my CLAUDE.md', or any variation where someone needs their project context documented for Claude. If a CLAUDE.md already exists with conte
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill claude-md-starter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.