runbooks-structure
Runbooks - Structure
Creating clear, actionable runbooks for operational tasks, maintenance, and troubleshooting.
What is a Runbook?
A runbook is step-by-step documentation for operational tasks:
- Troubleshooting - Diagnosing and fixing issues
- Incident Response - Handling production incidents
- Maintenance - Routine operational tasks
- On-Call - Reference for on-call engineers
Basic Runbook Structure
Minimum Viable Runbook
# Service Name: Task/Issue
More from thebushidocollective/han
android-jetpack-compose
Use when building Android UIs with Jetpack Compose, managing state with remember/mutableStateOf, or implementing declarative UI patterns.
1.1Kfastapi-async-patterns
Use when FastAPI async patterns for building high-performance APIs. Use when handling concurrent requests and async operations.
785storybook-story-writing
Use when creating or modifying Storybook stories for components. Ensures stories follow CSF3 format, properly showcase component variations, and build successfully.
487atomic-design-fundamentals
Use when applying Atomic Design methodology to organize UI components into quarks, atoms, molecules, organisms, templates, and pages. Core principles and hierarchy.
367solid-principles
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
250angular-rxjs-patterns
Use when handling async operations in Angular applications with observables, operators, and subjects.
216