Fable Native Code

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.

Purpose

Enforce codebase idioms and suppress foreign AI patterns. Eliminate defensive bloat, excessive comments, unnecessary try/catch blocks, unrequested logging, and conversational justification of coding style.

When to Use

• When writing or editing code in an existing repository.
• Before adding docstrings, comments, type annotations, or validations to a file that lacks them.
• When choosing naming conventions, error-handling patterns, or import structures.
• When reviewing a completed diff before finalizing the turn.

When NOT to Use