Add initial project structure with essential files
- Created .gitignore to exclude build artifacts and dependencies. - Added index.html as the main entry point for the application. - Included LICENSE file with Apache 2.0 terms. - Initialized package.json and package-lock.json for project dependencies. - Added pnpm-lock.yaml for package management. - Created QUICKSTART.md for setup instructions. - Added README.md and README.zh-CN.md for project documentation in English and Chinese.
This commit is contained in:
@@ -0,0 +1,51 @@
|
||||
---
|
||||
name: eng-runbook
|
||||
description: |
|
||||
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 "运维手册".
|
||||
triggers:
|
||||
- "runbook"
|
||||
- "ops doc"
|
||||
- "on-call"
|
||||
- "sre doc"
|
||||
- "service runbook"
|
||||
- "运维手册"
|
||||
ocd:
|
||||
mode: prototype
|
||||
platform: desktop
|
||||
scenario: engineering
|
||||
preview:
|
||||
type: html
|
||||
entry: index.html
|
||||
design_system:
|
||||
requires: true
|
||||
sections: [color, typography, layout, components]
|
||||
example_prompt: "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>
|
||||
```
|
||||
Reference in New Issue
Block a user