Loading...
Loading...
Found 21 Skills
Refactor code for readability using DRY, meaningful names, and modularization.
Provides final code cleanup after task review approval. Removes debug logs, temporary comments, dead code, optimizes imports, and improves readability. Use when asked to clean up code, polish, finalize, tidy up, remove technical debt, or prepare code for completion after review. Not for refactoring logic or fixing bugs—focused solely on cosmetic and hygiene cleanup.
Always use this skill when dealing with code of any kind. Wether writing, reading, reviewing or something else. If it's code use this skill.
A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.
Apply DX-first heuristics to implementations, refactors, reviews, and debugging. Use when the user asks for code review, refactoring guidance, API design feedback, maintainability/readability improvements, or “make this easier to debug/onboard”.
Commenting patterns that improve readability and maintainability.
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
Guiding principles for writing clear, concise, human readable and maintainable Python code.
Load when working with contents in *.mo files
Simplify and refine code for clarity, consistency, and maintainability
Probe whether a candidate term carries its meaning alone, by asking three models to guess it from a bare scenario. Use when naming a field, an enum value, a table or a glossary word and several candidates are in play ("carry or carryOver", "does this name read", "which word is clearer").
Readable primary-flow–first code structuring with minimal boundaries, atomic composition, and contract-driven unit tests