Découvrez les skills business architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Expert at creating continuous improvement feedback loops for Claude's responses. Use when establishing self-improvement processes, tracking progress over time, or implementing iterative refinement workflows.
AI-friendly architecture patterns for TypeScript projects including Domain-Driven Design, Clean Architecture, Hexagonal Architecture, and Page Object Model testing patterns
Dispatch two competing reviewers (arch-reviewer and impl-reviewer) before deep analysis. Competition produces more thorough results. Use before creating code, modifying architecture, making technical decisions,...
API design and developer experience for TypeScript libraries. Use when designing APIs, reviewing architecture, evaluating DX, or checking ergonomics. Covers extensibility, progressive disclosure, type inference...
Build accessible, headless UI components with modern architecture patterns. Use when creating component libraries, design systems, or reusable UI primitives. Handles compound components, state management, acces...
Expert guidance on Swift Concurrency concepts. Use when working with async/await, Tasks, actors, MainActor, Sendable, isolation domains, or debugging concurrency compiler errors. Helps write safe concurrent Swi...
Orchestrate large projects through hierarchical planning with init, review, and build phases.
Method clarity-driven planning workflow using zen-mcp tools (chat, planner, consensus). Phase 0 uses chat to judge if user provides clear implementation method. Four execution paths based on automation_mode × m...
Epic architecture agent for creating comprehensive epics with full task decomposition. Use when user says "create epic", "plan epic", "decompose into tasks", "architect the work", "break down this project", "ep...
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.
Competence in data analytics and machine learning, enabling developers to build data-driven features and integrate AI/ML capabilities.
Communicating the intended behavior and context of code through clear documentation and comments, and sharing knowledge with the team.
The practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.
Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases.
Leveraging AI coding assistants and tools to boost development productivity, while maintaining oversight to ensure quality results.
Writing clean, understandable, and self-documenting code that is easy to review and maintain over time.
Incorporating security at every step of software development – writing code that defends against vulnerabilities and protects user data.
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app pro...
Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.
Reference for Splitrail's core data types. Use when working with ConversationMessage, Stats, DailyStats, or other type definitions.
Performance optimization guidelines for Splitrail. Use when optimizing parsing, reducing memory usage, or improving throughput.
Common logging patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Common testing patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
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é.