vndangkhoa/open-design
1
0
Fork 0
mirror of https://github.com/nexu-io/open-design.git synced 2026-05-31 19:04:39 +07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
open-design/skills/eng-runbook/SKILL.md
Tom Huang 6f6bf31dd2
Refactor project name from "Open Claude Design" to "Open Design" (#1) 
* Refactor project name from "Open Claude Design" to "Open Design"

- Updated project name in package.json, package-lock.json, and README files.
- Changed CLI commands and references from "ocd" to "od".
- Adjusted file structure references in documentation and code to reflect new naming conventions.
- Enhanced .gitignore to include new runtime data files.
- Updated metadata in LICENSE file to match new project name.

* Add contributing guidelines in English and Chinese

- Introduced CONTRIBUTING.md and CONTRIBUTING.zh-CN.md to provide clear instructions for contributors.
- Outlined contribution types, local setup instructions, and merging criteria for skills and design systems.
- Enhanced README files to reference the new contributing guidelines.
2026-04-28 16:03:35 +08:00

1.5 KiB
Raw Blame History

name description triggers od
eng-runbook 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 "运维手册".
runbook
ops doc
on-call
sre doc
service runbook
运维手册
mode platform scenario preview design_system example_prompt
prototype desktop engineering
type entry
html index.html
requires sections
true
color
typography
layout
components
Write a runbook for our auth service — alerts, dashboards, common procedures, on-call rotation.

Engineering Runbook Skill

Produce a single-page engineering runbook.

Workflow

  1. Read DESIGN.md.
  2. Identify the service from the brief.
  3. Layout:
    • Header: service name, owner team, severity tier, version.
    • Service summary paragraph + dependency list.
    • Alerts table: alert name / severity / what it means / first response.
    • Dashboards & links list.
    • Common procedures block (3–4) with code blocks (deploy, rollback, rotate keys).
    • On-call rotation table (week / primary / secondary / backup).
    • Incident response checklist (5 numbered steps).
  4. One inline <style>, semantic HTML, monospace for code blocks.

Output contract

<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>