From antigravity-awesome-skills
Enforces a house style for writing dense, correct, idiomatic code across all programming tasks. Reduces code bloat and agent operation overhead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/antigravity-awesome-skills:super-codeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce code that is short, correct, idiomatic, and maintainable — in that priority order.
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:
Both matter. Fixing only one is not enough.
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.
Before touching a file, decide:
Write that down mentally (not in a prose block to the user). This is the target shape.
Read the relevant reference file for the language in use:
bash/SKILL.mdc/SKILL.mdcpp/SKILL.mdcsharp/SKILL.mddart/SKILL.mdelixir/SKILL.mdgo/SKILL.mdjava/SKILL.mdkotlin/SKILL.mdphp/SKILL.mdpython/SKILL.mdruby/SKILL.mdrust/SKILL.mdscala/SKILL.mdswift/SKILL.mdtypescript/SKILL.mdApply idiomatic patterns from that file. They replace verbose imperative code with correct, concise equivalents that are still readable.
Before presenting any code, scan it for:
| Anti-pattern | Fix |
|---|---|
| Comment restates what code does | Delete comment, or rewrite to say why |
| Single-use helper function/class | Inline it |
| Stdlib/framework already does this | Replace with the primitive |
| Defensive handling for impossible case | Remove |
| Verbose loop replaceable by idiomatic expression | Replace |
| Logging/print nobody asked for | Remove |
| Extra config/files/parameters not requested | Remove |
| Unused import or variable | Remove |
Ask yourself (silently):
If yes to any: undo that specific compression and keep the rest.
Always:
Never:
These apply in every language. The language-specific files extend this list.
// Loop through the list and add each item → ❌ delete// Order matters: process refunds before charges → ✅ keep (explains why)// TODO: add error handling — either add it or don'tThese govern how you operate inside the session, not just what you produce:
| Language / Stack | File |
|---|---|
| Bash / Shell | bash/SKILL.md |
| C | c/SKILL.md |
| C++ | cpp/SKILL.md |
| C# / .NET | csharp/SKILL.md |
| Dart / Flutter | dart/SKILL.md |
| Elixir / Erlang | elixir/SKILL.md |
| Go | go/SKILL.md |
| Java | java/SKILL.md |
| Kotlin + Compose (Android) | kotlin/SKILL.md |
| PHP | php/SKILL.md |
| Python | python/SKILL.md |
| Ruby | ruby/SKILL.md |
| Rust | rust/SKILL.md |
| Scala | scala/SKILL.md |
| Swift (iOS/macOS) | swift/SKILL.md |
| TypeScript / JavaScript | typescript/SKILL.md |
Read the relevant file at Step 2. If the language isn't listed, apply the universal checklist above and use the language's own idioms for loops, error handling, and data transformation.
// Anti-pattern
List<String> names = new ArrayList<>();
for (User u : users) {
if (u.isActive()) {
names.add(u.getName());
}
}
// Super-code idiomatic (Java)
List<String> names = users.stream().filter(User::isActive).map(User::getName).toList();
Symptoms: Reviewer complains or logic is unreadable. Solution: Revert the overly compressed section. Clarity and correctness always win over conciseness.
@karpathy-guidelines - For behavioral guidelines on surgical changes and simplicity.npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-aas-mobile-app-builderEnforces token-efficient prose and disciplined code generation via two orthogonal layers: SPEAK (caveman compression) and THINK (surgical edits, simplicity).
Encourages writing code that follows language-specific conventions and patterns. Useful when code compiles but feels foreign, or when contributors from different backgrounds produce conflicting styles.
Enforces universal code quality rules — KISS, DRY, clean code, code review. Use when writing or reviewing any code.