agentleFS
Sign inStart free
landim32landim32/awesome-ai-skills/CLAUDE.md

awesome-ai-skills

CLAUDE.md1 starsChanged 7 months agoMITView on GitHub

A curated collection of Claude AI skills — reusable instructional guides and templates for AI-assisted development across React/TypeScript and .NET/C# stacks. Each skill lives in skills/<skill-name>/SKILL.md and provides implementation patterns, code templates, and best practices. Uses GitVersion (ContinuousDelivery mode) configured in GitVersion.yml. Version bumps are driven by commit message prefixes: An optional scope in parentheses is accepted (e.g. feat(skills):, fix(workflows):). Any other prefix falls back to the branch default (Patch on main). This config is the same as the gitversion…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Create a directory under skills/ with a SKILL.md file.

    line 45
  2. Distinctive:

    Follow existing skills as examples for structure and depth of documentation.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

A curated collection of Claude AI skills — reusable instructional guides and templates for AI-assisted development across React/TypeScript and .NET/C# stacks. Each skill lives in skills/<skill-name>/SKILL.md and provides implementation patterns, code templates, and best practices.

Repository Structure

  • skills/ — Main skills collection. Each subdirectory contains a SKILL.md with metadata (name, description, allowed-tools) and detailed implementation guides.
  • workflows/ — Reusable GitHub Actions workflow templates (version-tag, create-release, npm-publish).
  • prompts/ — Prompt templates for specific use cases.
  • .github/workflows/ — CI/CD pipelines that consume the workflow templates.
  • scripts/ — Repository utility scripts. scripts/collect-skills.ps1 scans C:\repos for .claude/skills/ directories in other projects and copies new skills into this repo's skills/ folder. Also scripts/copy-dependency.ps1, scripts/push-skill.ps1, scripts/replace-skill.ps1.
  • agents/ — Role-based agent definitions (Claude Code flat-file convention, agents/<agent-name>.md).
  • rules/ — Machine-readable rules and constraints.
  • commands/ — Named invokable commands.
  • docs/ — Human-facing documentation (bilingual: EN or PT-BR with .pt-BR.md suffix).

Versioning and Releases

Uses GitVersion (ContinuousDelivery mode) configured in GitVersion.yml. Version bumps are driven by commit message prefixes:

PrefixBump
major: or breaking:, or any type with ! (e.g. feat(api)!:)Major
feat: or feature: or minor:Minor
fix: or patch:Patch

An optional scope in parentheses is accepted (e.g. feat(skills):, fix(workflows):). Any other prefix falls back to the branch default (Patch on main). This config is the same as the gitversion skill template (skills/gitversion/templates/GitVersion.yml).

Tag prefix accepts both v and V (e.g., v1.2.3). The CI pipeline auto-tags on push to main and creates a GitHub Release (plus a releases/vX.Y.Z branch) for every new version — major, minor or patch.

Collecting Skills from Other Projects

powershell -File scripts/collect-skills.ps1

This scans all repos under C:\repos for .claude/skills/ directories and copies any skill not already present into skills/.

Adding a New Skill

Create a directory under skills/ with a SKILL.md file. The file must include frontmatter-style metadata at the top:

---
name: skill-name
description: Brief description
allowed-tools: Tool1, Tool2
user-invocable: true|false
---

Follow existing skills as examples for structure and depth of documentation.

Download now (ZIP)

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