claude-md-authoring

Create CLAUDE.md files with XML-style sections documenting non-obvious codebase context.

155|25|Updated Apr 27, 2025
One-click install
npx skills add https://github.com/sammcj/agentic-coding --skill claude-md-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-md-authoring
Source: https://github.com/sammcj/agentic-coding/tree/main/Claude/skills/claude-md-authoring
Command: npx skills add https://github.com/sammcj/agentic-coding --skill claude-md-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves?

This Skill eliminates the problem of AI coding agents lacking crucial project context, preventing repeated explanations of non-obvious patterns and architectural decisions.

Core Features & Use Cases

  • CLAUDE.md Creation: Generate effective project memory files with non-obvious conventions and architectural patterns.
  • Context Enhancement: Add proven solutions to recurring issues and project-specific gotchas that aren't visible in code.
  • Use Case: Imagine you're onboarding a new AI agent to your codebase. Use this Skill to create a CLAUDE.md that captures why authentication tokens expire after 1 hour and how background jobs should refresh them using the specific refresh function.

Quick Start

Use the claude-md-authoring skill to create a new CLAUDE.md file for my React project, focusing on architectural patterns and non-obvious conventions.

Frequently Asked Questions about claude-md-authoring

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

FAQPage Schema
How do I create a CLAUDE.md file to help AI agents understand my codebase?

CLAUDE.md is a project memory file that documents non-obvious architectural patterns, design decisions, and conventions. Create it using XML-style sections like <ARCHITECTURE>, <CONVENTIONS>, <GOTCHAS>, and <TESTING> to capture context that code inspection alone won't reveal, then link to relevant files with line references.

What should I include in a CLAUDE.md to avoid explaining the same patterns repeatedly?

Document recurring issues, authentication token lifecycles, background job patterns, and project-specific gotchas that AI agents need to know. Use 2–4 XML sections with concrete examples: explain why design decisions were made, not what the code does, and link to existing documentation via file:line references.

When is it worth creating a CLAUDE.md instead of relying on code comments?

Create CLAUDE.md when you have architectural decisions, non-obvious conventions, or solutions to recurring issues that span multiple files or aren't visible in isolated code inspection. It's most valuable during AI agent onboarding to prevent repeated context requests.

Can I add to an existing CLAUDE.md or do I need to start fresh?

You can add architectural patterns or design decisions to an existing CLAUDE.md incrementally. Structure additions using the same XML-style tagging and avoid duplicating obvious information already captured in your codebase or existing documentation.

What's the difference between CLAUDE.md and standard documentation or README files?

CLAUDE.md is optimised for AI agent reasoning and focuses on non-obvious context: why token refresh happens via a specific function, how background jobs interact, and project gotchas. Standard docs target human readers; CLAUDE.md prevents agents from missing tacit knowledge.

Do I need special tools or setup to create a CLAUDE.md file?

No prerequisites beyond a text editor. Follow the XML-style tagging structure (2–4 sections), use Australian English spelling, and link to existing documentation. The Skill guides content selection and organisation to capture what AI agents need.