architecture-decision-records
Document significant architectural decisions. Use when making significant architectural decisions, documenting technology choices, or recording design trade-offs.
Browse published AI skills maintained by yairbederman. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
20Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Document significant architectural decisions. Use when making significant architectural decisions, documenting technology choices, or recording design trade-offs.
Backend API implementation patterns for scalability, security, and maintainability. Use when building APIs, services, and backend systems.
Use when creating new skills, editing existing skills, or verifying skills work
Use when you have a spec or requirements for a multi-step task, before touching code
Use when concluding significant work to extract reusable patterns and anti-patterns
Guide the planning of microservices architecture. Use when designing, planning, or architecting a system using microservices.
Build consistent, accessible UI with design tokens, component libraries, and automated testing. Use when establishing or evolving a design system.
Use when implementing any feature or bugfix, before writing implementation code
Design REST and GraphQL APIs with proper versioning, observability, and architecture patterns. Use when designing new APIs or reviewing API specifications.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use at conversation start - establishes how to find and use skills, requiring skill loading before ANY response
Use when you have a written implementation plan to execute with review checkpoints
Creates GitHub pull requests with properly formatted titles. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews.
Translate Figma designs into production-ready code with pixel-perfect accuracy. Use when implementing UI from Figma mockups.
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior
Refactor high-complexity React components. Use when complexity is high, when the user asks for code splitting, hook extraction, or complexity reduction.
Use at session start for context warm-up and during work to capture decisions
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.