code-quality-tools
Automated code quality fixes for linting, types, unused variables, and error handling; use when fixing code quality issues in bulk
发现 数据库 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Automated code quality fixes for linting, types, unused variables, and error handling; use when fixing code quality issues in bulk
Debug token-level penalty alignment issues. Use when banned tokens aren't being penalized correctly or when investigating tokenizer edge cases.
Audit and fix AI-generated or existing code for RadOS design compliance. Use after generating UI code or when reviewing PRs. Catches common mistakes like wrong shadows, hardcoded colors, missing components, and...
Use when writing or reviewing TypeScript code. Enforces strict mode standards, explicit typing, and best practices. Prevents 'any' types, @ts-ignore comments, and non-null assertions. This is a COMPREHENSIVE sk...
Use when you need to find code by concept (not just text). Uses Serena MCP for semantic code search across the codebase with minimal token usage. Ideal for understanding architecture, finding authentication flo...
Reviews and generates .NET/C# code following Microsoft conventions and modern patterns. Use when reviewing C# files, writing .NET code, refactoring, or when user mentions "C#", ".NET", "dotnet", "csharp", or as...
Guides design decisions for a low-code CSS layout generator. Use this skill when the user asks for help with UI/UX choices, component architecture, layout presets, canvas interactions, or design system decision...
Auto-loads when discussing composition, notes, patterns, or creating EtherScore files
Guide layer selection for Claude Code. Use when choosing between CLAUDE.md rules, skills, subagents, hooks, or MCP. Do not use for general coding questions or non-architecture tasks.
Fix linting and formatting issues automatically
Modern backend patterns, API design, OWASP security checklist, testing pyramid. For Node.js, Python, Go backends.
Review and manage ontological propositions for the Genesis Semantic Design System. Evaluate PRs for semantic purity, check redundancy, ensure universal applicability, and maintain the living genome architecture...
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design,...
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Apply to backend, hooks, state management, and any code where functionality matters.
Conflict identification and resolution patterns for requirements, decisions, and plans
System architecture design for scalable, maintainable systems. Includes architecture diagrams, design patterns, tech stack decisions, and dependency analysis.
Organizational coding standards and architectural patterns. References comprehensive skills for detailed patterns. Use when making architecture decisions or implementing features.
Task structure and atomic commit patterns for granular, verifiable work units
Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.
Comprehensive NestJS framework mastery with Drizzle ORM, TypeORM, Prisma, BullMQ queues, and 40 best practice rules. Use for NestJS applications, APIs, authentication, database integration, queue processing, mi...
Command Query Separation (CQS) and CQRS patterns for .NET. Use when designing methods, handlers, and application architecture. Ensures predictable, testable code.
Use when making technical decisions, choosing technologies, or documenting architectural choices. Creates ADRs (Architecture Decision Records).
Resolve unknown patterns by converting them into concrete reskin instructions and removing the unknown-patterns entry.
Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。