Loading...
Loading...
Found 166 Skills
Use when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
C# and .NET development expert using the dotnet CLI.
Use when writing code, documentation, or comments - always use accessible and respectful terminology
This skill should be used when implementing code that requires SOLID principles and clean code practices. It provides detailed guidance on Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles with comparison examples in TypeScript.
Enforces JSDoc documentation standards for this TypeScript project. This skill should be used when writing or reviewing TypeScript code to ensure proper documentation with file preambles, function docs, interface docs, and the critical distinction between documenting "what" vs "why". Use this skill to understand the project's JSDoc ESLint rules and established patterns.
Specifies Poetry or Rye for dependency management in Python projects.
Applies general rules for Convex development, emphasizing schema design, validator usage, and correct handling of system fields.
This skill should be used when the user asks to "write JavaScript code", "follow JavaScript style guide", "format JS files", "create Node.js scripts", or needs guidance on JavaScript/Node.js coding standards and best practices.
Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
SAP Converged Cloud Go coding conventions extracted from sapcc/keppel and sapcc/go-bits PR reviews. Enforces architecture patterns, library usage rules, error handling conventions, testing patterns, and anti-over-engineering principles. Use when working in sapcc/* repos, when code imports github.com/sapcc/go-bits, or when targeting SAP CC code review standards. Do NOT use for general Go projects without sapcc dependencies.