{"owner":"antiwork","repo":"gumroad","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","CLAUDE.md"],"skills":{"AGENTS.md":"@CONTRIBUTING.md\n\n## Agent Skills\n\nProject skills live in `.agents/skills/<name>/SKILL.md`. The `.claude/skills/<name>` entries are symlinks for Claude Code compatibility. When adding or updating a project skill, edit `.agents/skills` and keep the matching Claude symlink in place.\n\n## Code comments\n\nWrite comments for a reader who already knows this codebase. They are a colleague, not a\nstudent — so say the one thing the code cannot say, and stop.\n\nKeep: the non-obvious *why*, ordering constraints, and traps that will bite the next person\nto edit this. Cut: vendor or company history, anything restating the line below it, narration\nof how the bug was found, and re-explanations of a named constant the reader can click\nthrough to. If a comment runs past about three lines, ask what you would delete.\n\nA good test: would a maintainer who knows this file find this line worth reading? If not, it\nis noise — and noise is what teaches people to skip the comments that matter.\n","CLAUDE.md":"@CONTRIBUTING.md\n\n## Agent Skills\n\nProject skills live in `.agents/skills/<name>/SKILL.md`. The `.claude/skills/<name>` entries are symlinks for Claude Code compatibility. When adding or updating a project skill, edit `.agents/skills` and keep the matching Claude symlink in place.\n\n## Code comments\n\nWrite comments for a reader who already knows this codebase. They are a colleague, not a\nstudent — so say the one thing the code cannot say, and stop.\n\nKeep: the non-obvious *why*, ordering constraints, and traps that will bite the next person\nto edit this. Cut: vendor or company history, anything restating the line below it, narration\nof how the bug was found, and re-explanations of a named constant the reader can click\nthrough to. If a comment runs past about three lines, ask what you would delete.\n\nA good test: would a maintainer who knows this file find this line worth reading? If not, it\nis noise — and noise is what teaches people to skip the comments that matter.\n"},"files":{"AGENTS.md":"@CONTRIBUTING.md\n\n## Agent Skills\n\nProject skills live in `.agents/skills/<name>/SKILL.md`. The `.claude/skills/<name>` entries are symlinks for Claude Code compatibility. When adding or updating a project skill, edit `.agents/skills` and keep the matching Claude symlink in place.\n\n## Code comments\n\nWrite comments for a reader who already knows this codebase. They are a colleague, not a\nstudent — so say the one thing the code cannot say, and stop.\n\nKeep: the non-obvious *why*, ordering constraints, and traps that will bite the next person\nto edit this. Cut: vendor or company history, anything restating the line below it, narration\nof how the bug was found, and re-explanations of a named constant the reader can click\nthrough to. If a comment runs past about three lines, ask what you would delete.\n\nA good test: would a maintainer who knows this file find this line worth reading? If not, it\nis noise — and noise is what teaches people to skip the comments that matter.\n","CLAUDE.md":"@CONTRIBUTING.md\n\n## Agent Skills\n\nProject skills live in `.agents/skills/<name>/SKILL.md`. The `.claude/skills/<name>` entries are symlinks for Claude Code compatibility. When adding or updating a project skill, edit `.agents/skills` and keep the matching Claude symlink in place.\n\n## Code comments\n\nWrite comments for a reader who already knows this codebase. They are a colleague, not a\nstudent — so say the one thing the code cannot say, and stop.\n\nKeep: the non-obvious *why*, ordering constraints, and traps that will bite the next person\nto edit this. Cut: vendor or company history, anything restating the line below it, narration\nof how the bug was found, and re-explanations of a named constant the reader can click\nthrough to. If a comment runs past about three lines, ask what you would delete.\n\nA good test: would a maintainer who knows this file find this line worth reading? If not, it\nis noise — and noise is what teaches people to skip the comments that matter.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"@CONTRIBUTING.md\n\n## Agent Skills\n\nProject skills live in `.agents/skills/<name>/SKILL.md`. The `.claude/skills/<name>` entries are symlinks for Claude Code compatibility. When adding or updating a project skill, edit `.agents/skills` and keep the matching Claude symlink in place.\n\n## Code comments\n\nWrite comments for a reader who already knows this codebase. They are a colleague, not a\nstudent — so say the one thing the code cannot say, and stop.\n\nKeep: the non-obvious *why*, ordering constraints, and traps that will bite the next person\nto edit this. Cut: vendor or company history, anything restating the line below it, narration\nof how the bug was found, and re-explanations of a named constant the reader can click\nthrough to. If a comment runs past about three lines, ask what you would delete.\n\nA good test: would a maintainer who knows this file find this line worth reading? If not, it\nis noise — and noise is what teaches people to skip the comments that matter.\n","category":"root","tokens":245},{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"@CONTRIBUTING.md\n\n## Agent Skills\n\nProject skills live in `.agents/skills/<name>/SKILL.md`. The `.claude/skills/<name>` entries are symlinks for Claude Code compatibility. When adding or updating a project skill, edit `.agents/skills` and keep the matching Claude symlink in place.\n\n## Code comments\n\nWrite comments for a reader who already knows this codebase. They are a colleague, not a\nstudent — so say the one thing the code cannot say, and stop.\n\nKeep: the non-obvious *why*, ordering constraints, and traps that will bite the next person\nto edit this. Cut: vendor or company history, anything restating the line below it, narration\nof how the bug was found, and re-explanations of a named constant the reader can click\nthrough to. If a comment runs past about three lines, ask what you would delete.\n\nA good test: would a maintainer who knows this file find this line worth reading? If not, it\nis noise — and noise is what teaches people to skip the comments that matter.\n","category":"root","tokens":245}]}