Loading...
Loading...
Found 70 Skills
Apply Spatie's Laravel and PHP coding standards for any task that creates, edits, reviews, refactors, or formats Laravel/PHP code or Blade templates; use for controllers, Eloquent models, routes, config, validation, migrations, tests, and related files to align with Laravel conventions and PSR-12.
Optional, modular cleanups and style improvements to apply on new mo:core projects (or after mo:core migration). Covers import ordering, unused import cleanup, and single‑expression return removal, with detection checks and automation recipes.
Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.
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.
Review and verify Python code against PEP 8 using flake8, and optionally apply safe formatting fixes with black after explicit user confirmation. Use when users ask to check style compliance, lint Python files, or fix PEP 8 issues in a target folder.
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".
Go coding standards and style conventions grounded in Effective Go, Go Code Review Comments, and production-proven idioms. Use when writing or reviewing Go code, enforcing naming conventions, import ordering, variable declarations, struct initialization, or formatting rules. Trigger examples: "check Go style", "fix formatting", "review naming", "Go conventions". Do NOT use for architecture decisions, concurrency patterns, or performance tuning — use go-architecture-review, go-concurrency-review, or go-performance-review instead.
Guide for writing inline comments and JSDoc in the codebase. Use when generating code for bug fixes, new components, refactoring, or feature implementation.
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.
Remove AI-generated code slop from the current branch. Use when the user says "deslop" or asks to clean up AI slop, remove AI code patterns, or clean the branch before committing.
Guidance on Python code style optimization and Pythonic idioms; Based on the complete content of *One Python Craftsman* and the "Friendly Python" concept, covering variable naming, control flow, data types, container types, function design, exception handling, decorators, file operations, and SOLID principles; Providing user-friendly and maintainer-friendly design patterns, review checklists, and over 140 practical templates