Loading...
Loading...
Found 77 Skills
Unify EliteForge Java coding specifications, covering code style, comment specifications, POJO/enum/util classes, control statements, logging, concurrency, MyBatis-Plus, transactions, Spring, inter-service calls, Maven, databases, gateways, interface management, project structure, etc. Use this when users mention terms like "Java specification", "coding specification", "code style", "enum writing", "POJO specification", "logging specification", "transaction processing", "inter-service calls", "interface prefix", "domain model", "Maven version", "internationalization".
Guide for writing inline comments and JSDoc in the codebase. Use when generating code for bug fixes, new components, refactoring, or feature implementation.
Ruby development guidelines covering idiomatic code style, Ruby 3.x features, testing with RSpec, and best practices for building maintainable Ruby applications.
Setup TypeScript best practices and code style rules in CLAUDE.md
Next Friday coding standards - naming conventions, code style, imports, types, React/JSX patterns, Next.js rules. Use when writing or reviewing TypeScript/React/Next.js code.
Rust code style and conventions for Syncpack. Use when writing or modifying Rust code. Covers functional patterns, imports, naming, and quality standards.
Convenciones de formato: framework Diátaxis, español/LATAM, estilos de código, Conventional Commits.
Runs a second-pass cleanup over AI-written code using the repo's style guide in style.md. Prefers parallel subagents to simplify recently modified files without changing behavior. Use when the user says "deslop", "clean this up", "make this less AI", "apply my style guide", "second pass", or asks to simplify generated code after implementation.
Personal C# conventions - style/structure (file layout, naming, member/ctor ordering, methods, types, visibility, modern C# 11/12/13 syntax, forbidden patterns, XML doc) and runtime behavior (DateTime/IClock, async, dispose, exceptions + Result, structured logging, secrets/config, LINQ, System.Text.Json, decoupling + DI lifetimes). Load before creating or editing any `.cs` file - writing, reviewing, or refactoring C#; do not lean on recalled conventions.
Write systems code in the style of Linus Torvalds, creator of Linux and Git. Emphasizes pragmatic excellence, performance awareness, subsystem design, and uncompromising code review. Use when writing kernel-level code or high-performance systems.
Python coding standards with automatic version detection. Use when writing, reviewing, or refactoring Python to ensure adherence to LBYL exception handling patterns, modern type syntax (list[str], str | None), pathlib operations, ABC-based interfaces, absolute imports, and explicit error boundaries at CLI level. Also provides production-tested code smell patterns from Dagster Labs for API design, parameter complexity, and code organization. Essential for maintaining erk's dignified Python standards.
Improve code readability without altering functionality using idiomatic best practices