Loading...
Loading...
Found 259 Skills
Simplify and refine recently modified code while preserving functionality. Use when asked to "deslop", "clean up code", "simplify code", or after making changes that could benefit from refinement.
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.
Used to audit codebases to ensure their naming complies with established terminology and specifications. This Skill should be used when you need to enforce a project's 'Ubiquitous Language', identify deviations in method/variable/parameter naming, and propose modification suggestions.
Find high-value ways to deepen a codebase's modules, present them visually, and explore the chosen change.
Create Scratch project with TypeScript using Hikkaku; use when the user asks how to build or structure a Scratch project in this repo.
Core Go style principles and formatting guidelines from Google and Uber style guides. Use when writing any Go code to ensure clarity, simplicity, and consistency. This is the foundational skill - other Go style skills build on these principles.
Simplify coding implementations and reviews by reusing existing capabilities and removing unjustified abstractions, dependencies, configuration, and duplication. Use when implementation complexity or over-engineering is in scope. Do not use to weaken required behavior, safety, accessibility, or compatibility.
Executa refatoração segura e incremental para projetos Go, preservando comportamento e reduzindo complexidade. Use quando o usuário pede para refatorar, simplificar ou melhorar manutenibilidade. Não use para correção de bug (usar bugfix) nem para review/auditoria (usar reviewer).
Use this skill when implementing or reviewing a change that may contain unnecessary code, abstractions, dependencies, configuration, indirection, or generated boilerplate. Do not use it to remove required behavior or redesign unrelated parts of a system.
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.