القائمة
Protocol for auditing uFawkes.dev pages — what to check, severity ranking, output format, and persona models. Used by UX and Planning agents to produce ranked, actionable findings.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
Content strategy for uFawkes.dev — narrative structure, page-level content hierarchy, tone guidelines, CTA copy patterns, and trust signal rules.
| name | ux-audit |
| description | Protocol for auditing uFawkes.dev pages — what to check, severity ranking, output format, and persona models. Used by UX and Planning agents to produce ranked, actionable findings. |
| license | MIT |
| compatibility | opencode |
Fetch each in order using webfetch:
| Page | URL | Priority |
|---|---|---|
| Homepage | https://ufawkes.dev/ | P0 — highest traffic |
| Obs stack | https://ufawkes.dev/obs/ | P1 |
| Pipe stack | https://ufawkes.dev/pipe/ | P1 |
| DORA stack | https://ufawkes.dev/dora/ | P1 |
| Sec stack | https://ufawkes.dev/sec/ | P1 |
| DevX stack | https://ufawkes.dev/devx/ | P1 |
| Learn hub | https://ufawkes.dev/learn/ | P2 |
| DORA Primer | https://ufawkes.dev/learn/dora-primer.html | P2 |
| AI Capabilities | https://ufawkes.dev/learn/ai-capabilities.html | P2 |
| Observability Primer | https://ufawkes.dev/learn/observability-primer.html | P2 |
| Blog | https://ufawkes.dev/blog/ | P3 |
Keep these in mind when evaluating every page:
Builder — Senior engineer evaluating whether to adopt the stack for their team. Asks: "Does this actually work? How long to get running? Who else uses it?" High trust threshold. Notices stub content immediately.
Operator — Platform engineer or SRE who already uses one stack and wants to add another. Asks: "What does this add? How does it compose?" Skips hero copy, reads quick start commands directly.
Contributor — Developer interested in the open source project. Asks: "Is this active? Where do I start? Is the maintainer responsive?" Checks star count, commit recency, blog post dates.
{{ page.title }})/obs/.html: /learn/dora-primer.html.html pages (will 404)| Level | Label | Meaning | Action |
|---|---|---|---|
| P0 | Broken | Actively damages visitor trust | Fix before anything else |
| P1 | Conversion | Blocks primary visitor action | Fix this sprint |
| P2 | Quality | Weakens credibility or comprehension | Fix next sprint |
| P3 | Polish | Minor improvement | Deferred |
For each page audited, produce:
## Audit: [Page name] — [URL]
Audited: [date]
### P0 Broken
- [finding] → suggested fix → file: [filename]
### P1 Conversion
- [finding] → suggested fix → file: [filename]
### P2 Quality
- [finding] → suggested fix → file: [filename]
### P3 Polish
- [finding] → suggested fix → file: [filename]
### Summary
P0: N | P1: N | P2: N | P3: N
Recommended next: [issue description for Planning agent]
After audit, produce rows in this format for AGENTS.md Section 8:
| # | [Page]: [issue description — specific and actionable] | ⬜ Not started | [filename] — [location note] |