typescript
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
Découvrez les skills documentation architecture patterns, comparez leurs dépôts et consultez leurs instructions.
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
Platform/Language agnostic API delivery and correctness auditor. Use when project contains API endpoints to verify contract alignment, endpoint behavior, and test coverage.
Structured escalation with evidence. Surfaces blocking issues for human decision, referencing the Manifest hierarchy.
Transform rough ideas into detailed designs through structured dialogue. Use before implementation to refine requirements.
Dynamic plugin enumeration and capability mapping with delegation priority and explicit routing announcements
Creates comprehensive implementation plans through codebase exploration, research, and iterative clarification. Use when asked to plan, design, architect, or figure out how to implement a feature, refactor, or...
Top 1% development standard for OC Pipeline and federal-grade construction software. Use when Bill asks to build features, fix bugs, write code, create components, or do any software development work. Activates...
Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a non-trivial task or when you need to align on a complex implementation strategy.
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.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.