An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".
Produce a single-page engineering runbook.
<style>, semantic HTML, monospace for code blocks.<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/eng-runbook · pinned to the source commit
git clone https://github.com/nexu-io/open-design.git
cd open-design
git checkout d488b1aa87917daee40d7c61efd7decbb28b5455
mkdir -p ".claude/skills/eng-runbook"
cp -r "design-templates/eng-runbook" ".claude/skills/eng-runbook"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit d488b1aa8791. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.