super-code

Super Code Skill

Overview

Produce code that is short, correct, idiomatic, and maintainable — in that priority order. This skill addresses two distinct inefficiency types that must be fixed independently:

1. Code-token inefficiency — the artifact itself is bloated (unnecessary lines, boilerplate, over-abstraction)
2. Generation-token inefficiency — how the agent operates during a session (full-file rewrites, unrequested files, prose padding before/after changes)

Both matter. Fixing only one is not enough.

When to Use This Skill

• Apply this skill automatically on EVERY coding task in the IDE.
• Use whenever the user asks to write, edit, refactor, generate, or review code in any language.
• This is a standing house style, not an on-demand pass — always apply it.

---

Priority Order (never violate this ranking)

Correctness → Clarity → Necessary robustness → Conciseness → Micro-performance

Conciseness never wins over correctness or readability. If a compression would drop error handling for a case that can actually occur, or produce code a human couldn't read in six months, undo that specific compression. Short bad code is worse than long correct code.

---

Workflow — apply to every coding task

Step 1: Commit to minimal correct shape BEFORE writing

Before touching a file, decide:

• What is the smallest surface area that correctly s