C
ChaoBro

GitHub Skills File Revolution: From Karpathy CLAUDE.md to AI Coding Tool "Behavior Guidelines" Movement

GitHub Skills File Revolution: From Karpathy CLAUDE.md to AI Coding Tool "Behavior Guidelines" Movement

Conclusion

“Change AI coding assistant behavior with one CLAUDE.md file” — this seemingly simple idea is triggering a developer tool paradigm shift on GitHub. In late April 2026, GitHub trending was almost entirely occupied by “skills file” projects. This isn’t accidental traffic aggregation — it’s a collective confirmation of a new working method.

The Numbers

This week on GitHub trending, skills file-related projects dominated:

ProjectStarsWeekly GrowthCore Positioning
andrej-karpathy-skills105,200+21,896LLM coding pitfall guide
mattpocock/skills53,226+33,628Practical engineer skills pack
free-claude-code19,805+12,928Free terminal Claude Code

Growth Speed Analysis

mattpocock/skills gained 33,628 stars this week — that means 33 people are starring this project every minute on average. andrej-karpathy-skills has surpassed 105K cumulative stars, becoming one of the fastest-growing developer tool projects of 2026.

What Is the “Skills File” Pattern?

The core logic is extremely simple: define AI coding assistant behavior rules in a single Markdown file, placed in the project’s .claude/ or root directory.

project/
├── .claude/
│   └── CLAUDE.md    ← Tell AI how to write code for this project
├── src/
└── package.json

This file doesn’t contain code — it contains rules, conventions, and preferences:

  • “Don’t over-abstract; simple scripts don’t need factory patterns”
  • “Prefer TypeScript; never write .js files”
  • “Test files go in tests directory, use vitest”
  • “When encountering uncertain APIs, check official docs first”

Why Did This Pattern Explode?

1. Zero Dependencies

No packages to install, no environment to configure, no services to register. One Markdown file, copy-paste into your project, and it works.

2. Instant Results

Put CLAUDE.md in your project, and the next time an AI coding assistant generates code, the quality improves immediately. Because the AI finally “understands” your project style.

3. Composability

You can combine Karpathy’s general coding rules + Matt Pocock’s TypeScript best practices + your project-specific conventions. Multiple skills files can stack.

4. Platform Agnostic

Despite being called CLAUDE.md, this pattern isn’t limited to Claude Code. OpenClaw, Cursor, GitHub Copilot, and other tools are all starting to support similar project-level configuration files.

Action Recommendations

  • All AI coding tool users: Put a CLAUDE.md file in your project root with 5-10 project rules. Invest 10 minutes for massive long-term returns.
  • Team leads: Write team coding standards as CLAUDE.md — new members (and AI) automatically follow them on joining.
  • Skills authors: If you have domain expertise, package it as a skills file and share on GitHub. Community demand for high-quality skills is far from saturated.