Loading...
Loading...
Found 815 Skills
Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.
TypeScript standards and best practices with modern tooling. Use when working with TypeScript or TypeScript React files.
Detects common LLM coding agent artifacts in codebases. Identifies test quality issues, dead code, over-abstraction, and verbose LLM style patterns. Use when cleaning up AI-generated code or reviewing for agent-introduced cruft.
Enforces the project's core TypeScript standards including explicit typing, import organization, class member ordering, and code safety rules. ALWAYS apply when creating, modifying, or reviewing any TypeScript (.ts/.tsx) file.
TypeScript assertion function for runtime type narrowing with descriptive error messages. Based on tiny-invariant.
Canonical, cross-language clean code standard with stable rule IDs (CC-*). Use when writing/reviewing code, defining team standards, or mapping lint/CI findings to consistent CC-* rule citations.
Run a comprehensive code review
Use when working with performance testing review multi agent review
Use when working with error debugging multi agent review
Quality verification before commits and deployments. Use for quality checks, running tests, checking coverage, validating changes.
Luau best practices and clean code patterns for Roblox development. Use this skill when: - Writing new Luau modules, services, or controllers - Reviewing code for quality and maintainability - Setting up project structure and organization - Implementing error handling and validation - Managing memory and preventing leaks - Writing secure server-authoritative code - Following Roblox-specific conventions - Refactoring or improving existing code Triggers: "best practices", "clean code", "code review", "refactor", "code quality", "naming convention", "code style", "module pattern", "service pattern", "memory leak", "error handling", "pcall", "security", "server authority", "validation", "code organization"
Systematically trace bugs backward through call stack to find original trigger. Use when errors occur deep in execution and you need to trace back to find the original trigger.