folder-specific-claude-and-agents-md

Creates folder-scoped CLAUDE.md files with AGENTS.md symlinks for agent context.

60|11|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/matyasstoch/david-skills --skill folder-specific-claude-and-agents-md-matyasstoch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: folder-specific-claude-and-agents-md
Source: https://github.com/matyasstoch/david-skills/tree/main/skills/folder-specific-claude-and-agents-md
Command: npx skills add https://github.com/matyasstoch/david-skills --skill folder-specific-claude-and-agents-md-matyasstoch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working in a specific folder lack the local context that a global CLAUDE.md cannot cover, leading to repeated mistakes, re-litigated decisions, and ignored conventions. This Skill generates a focused, folder-scoped CLAUDE.md plus an AGENTS.md symlink so any future agent (Claude Code, Codex, etc.) starts with the right context. ## Core Features & Use Cases - Guided folder analysis: Reads every file in the target folder in full before drafting, so the generated file reflects real content rather than boilerplate. - Structured section templates: Drafts candidate sections such as Constraints (MUST NOT), Conventions, Locked Decisions, and Essential Files, then iterates with the user before writing. - AGENTS.md symlink creation: Creates a symlink (ln -s CLAUDE.md AGENTS.md) so both Claude Code and other agents stay in sync from a single source. - Use Case: You have an active project folder with evolving conventions and past decisions. Ask the agent to create a CLAUDE.md for it, review the drafted bullet sections, edit directly, and end with a synced AGENTS.md. ## Quick Start Ask the agent to create a CLAUDE.md with an AGENTS.md symlink for a specific folder in your workspace.

Frequently Asked Questions about folder-specific-claude-and-agents-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a CLAUDE.md file for a specific folder?▼

Confirm the target folder, read every file in it fully, then draft a bullet list of candidate sections for review before writing. Finish by creating an AGENTS.md symlink pointing to the CLAUDE.md so all agents share one source.

What sections should a folder-level CLAUDE.md include?▼

Common sections include Product/Purpose, Essential Files, Constraints (MUST NOT), Conventions, Locked Decisions, and Context. Skip any section that does not apply, and keep bullets short since the file is edited aggressively for brevity.

Should AGENTS.md be a copy or a symlink of CLAUDE.md?▼

AGENTS.md must be a symlink created with `ln -s CLAUDE.md AGENTS.md`, not a copy. A symlink keeps both files in sync automatically so edits to CLAUDE.md apply to every agent without manual duplication.

When should a folder NOT get its own CLAUDE.md?▼

Skip folders containing only static reference files, since agents can read those on demand. Only create the file when the folder has context needed across multiple sessions, such as active work, conventions, or ongoing decisions.

What is the difference between Constraints and Conventions in CLAUDE.md?▼

Constraints are explicit hard negatives (MUST NOT rules), while Conventions are 'usually do X' patterns like naming styles or status emojis. Splitting them improves agent adherence because hard rules and soft habits are enforced differently.