Loading...
Loading...
Found 17 Skills
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.
Vue 2 Project Code Style and Development Guidelines, including naming conventions, code organization, comment specifications, error handling, etc. Applicable to all code writing scenarios to ensure code consistency, readability, and maintainability.
Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)
Ruby development guidelines covering idiomatic code style, Ruby 3.x features, testing with RSpec, and best practices for building maintainable Ruby applications.
Deep codebase analysis to generate or regenerate STYLE_GUIDE.md with full evidence citations. Use when /setup-ai's quick pass isn't thorough enough, when conventions have drifted, or after a major refactor. Produces a 17-section style guide citing specific files as evidence.
Embedded C Code Style Assistant, based on the code specifications of 51 MCU teaching projects. Uses snake_case as the default naming convention, with camelCase as an option. It is used to create project structures that comply with embedded development specifications, optimize code style, and provide hardware driver templates. Suitable for embedded C project development such as 51 MCU and STM32.
Create Trae IDE rules (.trae/rules/*.md) for AI behavior constraints. Use when user wants to: create a project rule, set up code style guidelines, enforce naming conventions, make AI always do X, customize AI behavior for specific files, configure AI coding standards, or establish project-specific AI guidelines. Triggers on: 'create rule', '创建 rule', 'project rule', '.trae/rules/', 'AGENTS.md', 'CLAUDE.md', 'set up coding rules', 'make AI always use PascalCase', 'enforce naming convention', 'configure AI behavior'. Do NOT use for skills (use trae-skill-writer) or agents (use trae-agent-writer).
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".
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.
Convenciones de formato: framework Diátaxis, español/LATAM, estilos de código, Conventional Commits.
Sets up code formatting rules and style guidelines in CLAUDE.md
Write high-quality Vue 3 composables following established patterns and best practices. Use when creating new composables, refactoring existing ones, or reviewing composable code. Triggers include requests to "create a composable", "write a use* function", "extract logic into a composable", or any Vue Composition API reusable logic task.