uFawkes.dev

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.

Process for evolving the Fawkes Design System (FDS) — token definition, pattern library maintenance, compliance checking, and documentation. Currently in bootstrap phase.

Hard constraints for uFawkes.dev — Jekyll stack, GitHub Pages limits, Liquid safety rules, CSS conventions, front matter patterns, and commit format. Load this skill before any implementation task.

Responsive layout patterns for uFawkes.dev — canonical breakpoints, grid patterns, mobile-first rules, and common layout specs in vanilla CSS/BEM.

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.

Visual design rules for uFawkes.dev — hierarchy, spacing rhythm, typography scale, color usage, and interaction patterns. All expressed in vanilla CSS/BEM constraints.