Data Pipeline Orchestration DAG Blueprint
Designs a robust Airflow or Dagster DAG with proper task partitioning and error handling.
2,142 engineered scaffolds across 26 categories. Pick a category, drill into a subcategory, then open one straight into the engine.
Designs a robust Airflow or Dagster DAG with proper task partitioning and error handling.
A safe, fast pre-release checklist with rollback notes and named owners.
Designs the conditional logic and architecture for no-code automation workflows (Zapier/Make).
Restructure a module without changing observable behaviour, protected by characterisation tests
Convert raw incident timeline data into a blameless write-up with contributing causes and prioritised follow-ups
Trace a browser memory leak in a single-page application to the JavaScript reference retaining removed DOM nodes
Separate under-provisioned heap from a genuine retention leak in a service that dies with out-of-memory errors
Produce an ordered kubectl investigation runbook for a failing or crash-looping workload
Turn a production bug report into ranked root-cause hypotheses with a staged investigation plan
Analyzes insurance denial patterns to pinpoint upstream registration or coding failures.
Defines a self-healing workflow for agents executing complex sequences of API calls.
Investigates a specific quality failure in supplied parts using 5-Why and Ishikawa frameworks.
Design an API contract that is hard to misuse and easy to version.
Review a design for failure modes, coupling and operational cost.
Reproducible steps, likely root causes and a minimal fix plan with an acceptance test.
Review a change for correctness, blast radius and reversibility.
Write a migration runbook with verification and a tested rollback.
Updates a README or guide with setup, usage and working examples.
Triage a production failure from symptoms to a ranked set of hypotheses.
Write a blameless postmortem that ends in dated, owned prevention work.
Explain unfamiliar code and mark the parts that are risky to change.
Audit what we cannot see and prescribe the smallest useful instrumentation.
Find the true bottleneck before optimising anything.
A concise pull request review surfacing risks, tests to add and merge readiness.
Plan a refactor in safe increments that keep the system shippable.
A pragmatic test plan covering unit, integration and edge cases to prevent regressions.
Design a test strategy focused on the riskiest behaviours, not coverage vanity.
Creates a comprehensive developer-centric error catalog with actionable resolution steps.
Creates step-by-step incident response playbooks for specific cloud security scenarios.
Analyzes how an outage or bug affected the external developer community and ecosystem.
Structures a technical post-mortem for data pipeline failures or ML production incidents.
Define a structured error payload whose codes clients can branch on safely across versions
Converts raw incident logs and timelines into a structured, blameless Post-Mortem report.
Synthesizes system logs and timelines into a structured incident report for stakeholders and engineering teams.
Defines meaningful Service Level Indicators and Objectives based on user journeys.