Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
Karpathy Guidelines turns common LLM coding failure modes into a concise operating discipline: think before editing, prefer the smallest solution, preserve surrounding code, and define a checkable finish line.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: Installs the repository's behavioral guidelines as a per-project CLAUDE.md file. · Claude Code
Before you start
The curl command-line tool must be available.
Claude Code for applying the project instructions
Platform: A shell providing the documented curl command and redirection syntax
Run from: The new project's root directory
In a terminal opened at the new project's root directory, download the guidelines as CLAUDE.md. Use this new-file route only when the project has no CLAUDE.md to preserve; otherwise choose the documented append route.
Installs: Appends the repository's behavioral guidelines to CLAUDE.md in an existing project. · Claude Code
Before you start
The curl command-line tool must be available.
Claude Code for applying the project instructions
Platform: A shell providing the documented curl command and redirection syntax
Run from: The existing project's root directory
In a terminal opened at the existing project's root directory, add a blank line and append the downloaded guidelines to CLAUDE.md. Run the complete two-line command unit as shown.
Replace `[path/to/relevant/file]` with the relevant project file or directory.
Replace `[describe the observed bug and expected behavior]` with the observed failure and the desired outcome.
Use the karpathy-guidelines skill to address the bug in `[path/to/relevant/file]`. First state any assumptions or ambiguities. Write a test that reproduces `[describe the observed bug and expected behavior]`, then make the smallest change needed for that test to pass. Match the existing style, avoid unrelated refactoring, and report the verification performed.
Claude
Cursor