القائمة
Process for evolving the Fawkes Design System (FDS) — token definition, pattern library maintenance, compliance checking, and documentation. Currently in bootstrap phase.
التثبيت باستخدام 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 | design-system-workflow |
| description | Process for evolving the Fawkes Design System (FDS) — token definition, pattern library maintenance, compliance checking, and documentation. Currently in bootstrap phase. |
| license | MIT |
| compatibility | opencode |
No formal token system or component library exists yet. The FDS is being assembled from patterns already in assets/css/main.css and AGENTS.md. Design-System work is PR 3 deferred — do not activate without Planning agent instruction.
#16a34a) in a speccolor-brand)_includes/ file and CSSBefore approving any CSS change, verify:
.block__element--modifierWhen the token system is mature enough for CSS variables, the migration path is:
:root {}main.css in a single PR — do not do incrementallyDo not introduce CSS variables before this migration is planned and approved.