GitHub
fail-fast
Use when handling errors. Use when tempted to catch and swallow exceptions. Use when returning default values to hide failures.
Skills IA documentation architecture patterns
Découvrez les skills documentation architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Catégories: documentation architecture patterns
documentation architecture patterns Effacer les filtres
Explorer
GitHub
deadlock-prevention
Use when acquiring multiple locks. Use when operations wait for each other. Use when system hangs without crashing.
GitHub
liskov-substitution-principle
Use when creating subclasses or implementing interfaces. Use when tempted to override methods with exceptions or no-ops. Use when inheritance hierarchy feels wrong.
GitHub
interface-segregation-principle
Use when designing interfaces. Use when implementing interfaces with methods you don't need. Use when forced to implement throw/no-op for interface methods.
GitHub
you-aint-gonna-need-it
Use when tempted to add features "for later". Use when building "production-ready" systems before needed. Use when adding flexibility that isn't required yet.
GitHub
exception-hierarchies
Use when creating custom exceptions. Use when error handling feels chaotic. Use when catch blocks are too broad or too specific.
GitHub
open-closed-principle
Use when adding new functionality to existing code. Use when tempted to add if/else or switch branches. Use when extending behavior of existing classes.
GitHub
pythonarchitecture
Python application architecture with functional core, effectful shell, DDD, and data modeling. Use when designing application layers, separating pure business logic from IO, defining domain models, implementing...
GitHub
separation-of-concerns
Use when component does too many things. Use when mixing data fetching, logic, and presentation. Use when code is hard to test.
GitHub
cognitive-complexity
Use when analyzing cognitive load, code complexity, onboarding difficulty, readability concerns, maintainability issues, or applying Ousterhout principles for deep modules, reducing complexity, and strategic pr...
GitHub
frontend-design
Create distinctive, production-grade frontend interfaces with exceptional design quality. Use when building web components, pages, or applications that need creative, polished aesthetics.
GitHub
distributed-systems
Use when working with distributed systems, clustering, consensus algorithms, network partitions, CAP tradeoffs, or distributed Erlang/Elixir patterns
GitHub
elixir-patterns
Use when implementing or refactoring Elixir code, designing system architecture, working with functional programming patterns, OTP design patterns (GenServer, supervision trees), or needing idiomatic Elixir cod...
GitHub
design-system-violation-detector
Automated detection and enforcement of design system guidelines including dark mode, colors, spacing, typography, focus states, and accessibility compliance
GitHub
websocket-real-time
WebSocket real-time updates, SSE broadcasting, event buffering
GitHub
intent-assess
Assess if IDD fits your project and learn about Intent-Driven Development. Use /intent-assess to evaluate project suitability or /intent-assess --learn for IDD education.
GitHub
mo-development
This skill should be used when the user asks to "create module", "add module", "module structure", "use Res type", "return Res", "Res.Ok", "Res.Fail", "IsFailed pattern", "module registration", "module dependen...
GitHub
feature-development
Guide for developing new features in the DEVS platform following the modular feature architecture. Use this when asked to add a new feature, create a feature module, or understand the feature structure.
GitHub
refactor-flow
Improve code quality, reduce technical debt, restructure for maintainability
GitHub
trace-check
Validate and update bidirectional traceability across SDD artifacts
GitHub
doc-sys-create-system-requirements-layer-6
Create System Requirements (SYS) - Layer 6 artifact defining functional requirements and quality attributes
GitHub
adr-roadmap
Generate phased implementation roadmaps from Architecture Decision Records
GitHub
doc-ears
Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format
GitHub
doc-adr-create-architecture-decision-records-layer-5
Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format
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é.