Agent skill · writing content · sickn33

folder-specific-claude-and-agents-md

Create folder-scoped CLAUDE.md and AGENTS.md guidance for future agents working in that area.

Why this skill is useful

Provides structured templates and domain-specific guidance for creating folder-specific documentation that enhances agent understanding.

What it needs

About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.

What this skill does

Folder CLAUDE.md Creation When to Use Use when the user asks for folder-specific agent instructions or local context files. Use when a subdirectory needs a CLAUDE.md and AGENTS.md handoff for future agents. Generate a focused CLAUDE.md inside a target folder, plus an AGENTS.md symlink pointing at it. The file gives any future agent (Claude Code, Codex, etc.) the folder-specific context the global CLAUDE.md doesn't cover. Background reference: library/claude-code/claude-and-agents-md.md. Process Step 1: Confirm the target folder + sanity-check it deserves a file Ask the user which folder. Use absolute path under ~/Documents/code/workspace/. Only create a file if the folder has context needed across multiple sessions — active evolving work, specific conventions, ongoing decisions. A folder of static reference files does NOT need one (agents can read on demand). If unsure, ask the user. Step 2: Read every file in the folder IN FULL Use ls -la first to enumerate files and subfolders. Read every markdown, config, and key source file. For large tldraw/Vite subprojects: read package.json, src/App.tsx, one representative module file, and the folder's own module-details.md-style files. Do NOT skim. Do NOT skip. The user's later edits depend on you having full context. Step 3: Draft a bullet list of candidate content Before writing the file, give the user a bullet list grouped by section — let them react first. Candidate sections (skip any that don't apply): Product / Purpose — what this folder/project is, current state, key metrics Avatar / Audience — who it's for (if applicable) Essential Files — one-line role for each important file, including cross-folder references (use @path/file.md import syntax) Constraints (MUST NOT) — explicit hard negatives. Highest-ROI content in the file. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills sickn33/folder-specific-claude-and-agents-md

View the source on GitHub

Browse the @skills marketplace