contingency-module-architecture
Design contingency module architectures for failure scenarios.
Discover testing security architecture patterns skills, compare source repositories and read the instructions for each workflow.
Design contingency module architectures for failure scenarios.
Execute context preservation protocols for session continuity.
TDD workflow for Rails applications. Use when implementing features or fixing bugs. Provides Red-Green cycle with test decision framework.
This skill provides expert guidance on implementing Ruby on Rails applications using 37signals (Basecamp/HEY) patterns and conventions. Use when building Rails features, implementing authentication, authorizati...
Feature-Sliced Design (FSD) architectural methodology for frontend applications. Use this when structuring code, creating new features, refactoring folder structure, or ensuring proper layer/slice/segment organ...
Elixir programming
Deliberately impose artificial constraints and simplification rules to counteract organizational drift toward complexity. Complexity kills companies—fight it with binary rules.
An organizational model where a single leader is fully accountable for a specific goal and controls all cross-functional resources needed, minimizing external dependencies. Amazon's alternative to matrixed orga...
Project-specific patterns, conventions, and learnings for docker-containers. Triggers: "project patterns", "how does this project", "project conventions", "local setup", "build order", "test setup", "project-sp...
Document learnings, capture repeatable workflows as skills, and prepare to compound an opence change.
Break down complex tasks into actionable, atomic steps that can be executed by individual agents.
Observability patterns for metrics, logs, and traces. Use when implementing monitoring, setting up Prometheus/Grafana, configuring logging pipelines, implementing distributed tracing, or designing alerting syst...
Best practices for containerizing applications with Docker.
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible | 無効なデータが実行の...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and ve...
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and increm...
Navigate and understand Octopus structure across spaces, environments, and projects
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
This skill provides expert guidance on implementing Ruby on Rails applications using 37signals (Basecamp/HEY) patterns and conventions. Use when building Rails features, implementing authentication, authorizati...
When a solution needs simplifying, load this skill with the map-reduce skill to find its essence.
Modern async ORM with type-safe models and efficient queries
Best practices for async Python code, avoiding common pitfalls like await precedence bugs and sync-in-async anti-patterns.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing A...
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.