Loading...
Loading...
Found 169 Skills
Use when writing code, documentation, or comments - always use accessible and respectful terminology
Applies general coding standards and best practices for Kafka development with Scala.
Generate pure mapper functions for transformations between layers, HTTP DTOs to use case inputs dtos, use case to response dto, etc.
Improve code readability without altering functionality using idiomatic best practices
Proxy2.0 后端全局编码规范：命名、注释、分层架构、代码风格、依赖注入、复杂度限制等全局约束。 Use when writing, reviewing, or modifying any Java code in the proxy2.0-api project. Triggers on: (1) Creating new Java classes, (2) Code review, (3) Refactoring, (4) Any backend development task in this project.
Authoritative reference for Odoo 19 syntax conventions across Python ORM, XML views, OWL/JavaScript, controllers, manifests, and SCSS. Use this skill BEFORE writing or modifying any Odoo code, whenever the user mentions Odoo, an Odoo module, an Odoo model, an XML view, an OWL component, or any file under an Odoo addons directory. Odoo 19 introduces breaking changes (130 model renames, res.groups privilege refactor, hr.contract→hr.version, models.Constraint, attrs removal continued, type='jsonrpc') that older training data does NOT reflect. Always consult this skill before generating code, even if the request looks routine — a model that "obviously" works in Odoo 18 may be wrong in Odoo 19. Trigger this skill on phrases like "create an Odoo module", "add a field to res.partner", "write a controller", "make an OWL component", "fix this Odoo view", "_sql_constraints", "tree view", or any time you see a `__manifest__.py`, `models/*.py`, `views/*.xml`, or `static/src/**/*.js` file in an Odoo project.
Expert in implementation and coding. Implements high-quality code while complying with project conventions and structure based on design documents. Acts as a specialist in the corresponding programming language according to the language being used.
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers pragma version, naming conventions, project layout, and OpenZeppelin integration. Trigger: any task involving creating, editing, or reviewing .sol source files.
Applies general rules for Convex development, emphasizing schema design, validator usage, and correct handling of system fields.
iOS code style guide for Swift and Objective-C. Use this skill whenever the user mentions code style, formatting, naming conventions, code organization, Swift/Objective-C coding standards, indentation, comments, or needs to enforce consistent code quality across the project. This skill covers formatting rules, naming patterns, documentation standards, and file organization.
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.
Full-process specification for software development, covering requirements analysis, design, pre-development, development, testing, and delivery, including review mechanisms, coding specifications and Git workflow