菜单
Content strategy for uFawkes.dev — narrative structure, page-level content hierarchy, tone guidelines, CTA copy patterns, and trust signal rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | content-strategy |
| description | Content strategy for uFawkes.dev — narrative structure, page-level content hierarchy, tone guidelines, CTA copy patterns, and trust signal rules. |
| license | MIT |
| compatibility | opencode |
Every page follows this structure — in this order:
Why → What problem does this solve? (1–2 sentences max)
What → What is this, specifically? (name, category, key feature)
How → How do I get it running? (quick start, docker compose)
Proof → Why should I trust it? (real metrics, real examples, honest status)
Next → What do I do after this? (compose with, learn more, contribute)
Visitors skim. If "How" is buried under three paragraphs of "Why", builders drop off.
| Do | Don't |
|---|---|
| Direct and specific | Vague and promotional |
| "60 seconds to running" | "Get started today" |
| "Prometheus + Grafana + AI" | "Powerful observability solution" |
| "Repos launching soon" (once) | "GitHub repo coming soon" (five times) |
| "Built by @paruff" | "Enterprise-grade" |
| Honest about early status | Fake social proof (zero-star badges) |
Voice: confident engineer talking to engineers. Not a sales page. Not a startup pitch deck.
[ H1: hidden sr-only "uFawkes" ]
[ Hero: "Production platform engineering, open source." ]
[ Subhead: 2 sentences — what it is and why it exists ]
[ Primary CTA: "See the stacks ↓" — scrolls to stack family ]
[ Stack Family: 5 cards — emoji, name, one-line hero, quick start ]
[ Dojo callout: "Practice in the Dojo →" ]
[ DORA AI Capabilities: 2-col table with descriptions ]
[ From the blog: 1 latest post card ]
[ Email form: "Get notified when stacks launch" ]
[ Hero: stack name + one-line hero ]
[ Quick start: 3 docker compose commands ]
[ Features: 4–6 bullet points with real descriptions ]
[ Compose with: links to related stacks ]
[ Get notified / GitHub link ]
| Context | Good copy | Bad copy |
|---|---|---|
| Primary homepage | "See the stacks ↓" | "Get started" |
| Stack quick start | "Run in 60 seconds" | "Try it now" |
| Coming soon | "Notify me when it launches" | "Coming soon" |
| Learn hub | "Read the DORA primer →" | "Learn more" |
| Dojo | "Practice in the Dojo →" | "Click here" |
| Contribute | "View on GitHub →" | "GitHub" |
Real trust signals (use these):
Anti-trust signals (remove these):
Each page must have a unique description in front matter:
| Page | Description pattern |
|---|---|
| Homepage | "uFawkes — open source platform engineering stacks. Prometheus, Grafana, DORA metrics, and AI capabilities. 60 seconds to running." |
| Stack page | "[StackName] — [what it is] for [who]. [key differentiator]." |
| Learn guide | "[Topic] explained for platform engineers. [what you'll learn]." |
| Blog post | Use the excerpt field |
Never use the global tagline as a page description.
Code quality standards for uFawkes.dev — Jekyll/Liquid linting rules, CSS validation, HTML structure checks, and review thresholds. Used by Review and Build agents.
Full lifecycle for uFawkes components — anatomy definition, implementation spec, styling rules, and Jekyll/Liquid integration patterns. For UI and Build agents.
Handoff protocol, dependency sequencing, and parallel task rules for the uFawkes agent team. Ensures agents don't conflict, block each other, or duplicate work.
Prioritization framework, sprint sequencing, and success criteria for uFawkes.dev work. Used by Planning agent to sequence issues across PRs and agents.
Three-phase accessibility workflow for uFawkes.dev — audit (find issues), remediate (fix specifications), verify (confirm compliance). Covers WCAG AA, Jekyll/HTML patterns, and vanilla CSS focus states.
Process for evolving the Fawkes Design System (FDS) — token definition, pattern library maintenance, compliance checking, and documentation. Currently in bootstrap phase.