Agent skill · Documentation

fable-native-code

Use when writing or editing code in an existing codebase — before adding comments, docstrings, try/catch blocks, validation, logging, or TODOs the surrounding file doesn't have, and before explaining your style choices in the reply.

DizzyMiigithub.com/DizzyMiiGitHub ↗
claude-codeMIT
Install
npx skills add DizzyMii/fable-skills --skill fable-native-code --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/fable-native-code/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 52
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Native Code ## Overview Your diff should read like the file's longtime owner wrote it. The file has a style — naming, error handling, comment density, formatting. Write in it. Your personal preferences are not improvements; they're an accent. ## Rules 1. **Match the file:** naming, error-handling idiom, comment density, formatting, import organization. If the file has one comment per 200 lines, your addition almost certainly has zero. 2. **Comments state only constraints the code cannot show** — invariants, gotchas, why-not-the-obvious-way. Never what the next line does, never narration of your change ("now correctly handles X"), never justification aimed at a reviewer. Test: after the PR merges, is this comment information or noise? 3. **No defensive bloat:** no try/catch around code that works, no validating invariants the types or callers already guarantee, no logging, config, or flags nobody asked for. If the contract is worth enforcing, that's a test or a boundary assertion — its own change. 4. **Don't narrate your restraint.** The urge to explain what you *didn't* add ("note: I deliberately left out the doc comment because…") is the same urge that adds it — displaced into t

What's inside
Steps it walks through
  1. Overview
  2. Rules
  3. Contrast
  4. Rationalizations
  5. Red Flags — delete before committing
More from fable-skills
All skills →
About this skill
What does the fable-native-code skill do?

Use when writing or editing code in an existing codebase — before adding comments, docstrings, try/catch blocks, validation, logging, or TODOs the surrounding file doesn't have, and before explaining your style choices in the reply.

How do I install it?

Run `npx skills add DizzyMii/fable-skills --skill fable-native-code --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From DizzyMii/fable-skills, a repository with 52 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going