Discover documentation architecture patterns skills, compare source repositories and read the instructions for each workflow.
Database schema and persistence layer for BookArchivist. Covers BookArchivistDB structure, book entry schema, Repository pattern for dependency injection, indexes (item/object/title), migrations (v1→v2), and da...
Provides guidance on React design patterns like Composition, Render Props, and Custom Hooks. Use when architecting complex UI components.
Comprehensive spec-driven development workflow combining artifact management with systematic implementation. Use when starting new features, creating specs/plans, implementing from specifications, or coordinati...
Optimize API performance, database queries, caching, and profiling. Use when improving system performance to meet
Design and evolve the architecture of the Paracle multi-agent framework. Use when discussing system design, architecture decisions, component structure, or technical debt.
Optimize API performance, database queries, caching, and profiling. Use when improving system performance to meet
Design and implement DAG-based workflows with parallel execution, retries, and error handling. Use when building complex multi-step agent workflows.
Design and implement DAG-based workflows with parallel execution, retries, and error handling. Use when building complex multi-step agent workflows.
Optimize API performance, database queries, caching, and profiling. Use when improving system performance to meet
Design and implement DAG-based workflows with parallel execution, retries, and error handling. Use when building complex multi-step agent workflows.
Design and evolve the architecture of the Paracle multi-agent framework. Use when discussing system design, architecture decisions, component structure, or technical debt.
Structured problem-solving workflow for debugging. Use after 3 failed attempts at solving an issue, when stuck on a problem, or when encountering repeated errors.
Maintain, retrieve, and normalize shared project context (decisions, constraints, standards, task state) for multi-skill workflows. Use when Codex must be the source of truth for project context, summarize cons...
Use when a single file is difficult to understand top-down because the public surface is buried or definitions appear before the behavior they support. Goal: restore a clear reading flow without changing semant...
Use when navigation is costly or module boundaries feel blurry due to messy directories, inconsistent naming, or cross-boundary imports. Goal: make architecture and dependency direction readable from the tree a...
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications...
Master REST API design principles to build intuitive, scalable, and maintainable APIs. Applicable for designing new APIs, reviewing API specifications, or establishing API design standards in Java Spring projec...
Systematically reverse-engineers business requirements from legacy codebases using the Horseshoe Model to bridge the gap between implementation details and architectural intent.
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Test-Driven Development workflow with RED-GREEN-REFACTOR, lore from Kent Beck, Michael Feathers, and Ousterhout's counterpoint
Design, implement, and maintain applications using hexagonal architecture (ports and adapters). Use when (1) designing new systems requiring clear separation between domain logic and infrastructure, (2) refacto...
Create detailed implementation strategies and architecture documentation
Code refactoring patterns, techniques, and best practices for improving code structure without changing behavior
Integration testing patterns, strategies for testing component interactions, and managing test dependencies
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.