sohaibdevvsohaibdevv/claude-skills/templates/CLAUDE.md

claude-skills / templates

CLAUDE.md2 starsChanged 42 days agoMITView on GitHub

This guide explains the template system for agents, commands, and standardized workflows. Location: templates/ Purpose: Reusable templates for consistent agent development, slash command creation, and workflow automation across all domains. Location: templates/agent-template.md Usage: Starting point for creating new cs-* agents Contains: - YAML frontmatter structure - Required markdown sections - Workflow documentation format - Integration examples pattern When to Use: Creating any new agent in agents/ directory Not yet created. There is no command template or workflow template file in…

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Not yet created. There is no command template or workflow template file in templates/ today — when creating slash commands, copy an …
line 29

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

CLAUDE.md

Templates - Claude Code Guidance

This guide explains the template system for agents, commands, and standardized workflows.

Template Purpose

Location: templates/

Purpose: Reusable templates for consistent agent development, slash command creation, and workflow automation across all domains.

Available Templates

Agent Templates

Location: templates/agent-template.md

Usage: Starting point for creating new cs-* agents

Contains:

YAML frontmatter structure
Required markdown sections
Workflow documentation format
Integration examples pattern

When to Use: Creating any new agent in agents/ directory

Command Templates and Workflow Templates

Not yet created. There is no command template or workflow template file in templates/ today — when creating slash commands, copy an existing command in commands/ (e.g. commands/cs-backend-review.md for the argument-hint + gate pattern) instead of looking for a template here.

Template Usage Pattern

# 1. Copy template
cp templates/agent-template.md agents/domain/cs-new-agent.md

# 2. Customize for your agent
vim agents/domain/cs-new-agent.md

# 3. Follow template structure exactly

# 4. Test relative paths and integrations

# 5. Commit with conventional commit
git commit -m "feat(agents): implement cs-new-agent from template"

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free