writing-plans
Create detailed implementation plans with granular tasks. Use before implementing features or complex changes.
Discover devops architecture patterns skills, compare source repositories and read the instructions for each workflow.
Create detailed implementation plans with granular tasks. Use before implementing features or complex changes.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
Technical analysis capabilities for APIs, data models, integrations, and security requirements. Use when analyzing technical aspects of systems or documenting technical requirements.
Prowler API patterns: JSON:API, RLS, RBAC, providers, Celery tasks. Trigger: When working in api/ on models/serializers/viewsets/filters/tasks involving tenant isolation (RLS), RBAC, JSON:API, or provider lifec...
Master skill for the SocioPulse V2 dual-brand monorepo platform. Provides context and references to specialized sub-skills.
Knowledge base for event-driven automation in .claude/ configuration. Teaches project-first hooks architecture with templates, security patterns, and guardrails for local project protection. Do not use for plug...
Game Designer worker agent for event-driven orchestration
Four-phase root cause investigation before attempting fixes. Use when debugging bugs, test failures, or unexpected behavior.
Patterns for optimizing database queries and preventing connection pool exhaustion. Use when writing batch operations, debugging slow queries, or reviewing code for performance.
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.
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...
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.
Comprehensive Spring Boot 3.x best practices for building scalable, maintainable enterprise applications with Jakarta EE. Use this skill when creating Spring Boot applications, designing REST APIs, implementing...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.