Agent Skills: UX Design Sync Skill

Synchronize DESIGN.md, UX DesignOps docs, Stitch mappings, visual debt, and implementation reality after UI changes.

UncategorizedID: LaizyIO/WorkflowSkills/ux-design-sync

Install this agent skill to your local

pnpm dlx add-skill https://github.com/LaizyIO/WorkflowSkills/tree/HEAD/ux-design-sync

Skill Files

Browse the full folder contents for ux-design-sync.

Download Skill

Loading file tree…

ux-design-sync/SKILL.md

Skill Metadata

Name
ux-design-sync
Description
Synchronize DESIGN.md, UX DesignOps docs, mockup references, visual debt, and implementation reality after UI changes.

UX Design Sync Skill

WorkflowSkills Project Context

Before acting, resolve project documentation roots:

  1. Look for a [DOC]-* directory at project root.
  2. If found, set DOC_ROOT to that directory and UX_DOCS_ROOT to [DOC]-*/11-UX-DesignOps.
  3. If [DOC]-* is absent, stop and ask to initialize project documentation first; never write persistent UX documentation to docs/obsidian.
  4. Read current code and approved requirements. Code is evidence of implemented behavior; CDC, DB, meetings, ADR and FEAT retain the project's documented precedence for intended behavior. Record discrepancies rather than rewriting requirements to legitimize a defect.

Goal

Keep UX documentation, DESIGN.md, mockup metadata, and implemented UI aligned.

Process

  1. Read changed UI files, tokens, components, routes, and tests.
  2. Compare code with DESIGN.md and UX docs.
  3. Update screen, component, flow, decision, visual debt, and mockup index docs.
  4. Update frontmatter updated dates.
  5. Update MOC-UX.md and MOC-Principal.md when new docs are created.
  6. Verify that referenced mockup images exist locally and distinguish proposed designs from implemented screens.
  7. Maintain Product_Context, Design_Direction and Platform_Profile when the authorized change affects their decisions. Preserve reasons, evidence and unresolved gaps; do not transfer project-specific visual choices into global rules.

Image references

Update 07-Mockups/Mockup_Index.md with selected image paths, exact prompts, route/component mapping, implementation status and intentional deviations. Keep rendered application screenshots separate from generated mockups.

Rules

  • Documentation content must be in French.
  • Do not invent implementation details absent from code.
  • Archive obsolete UX docs if the related code no longer exists.

Taste and design references

Maintain Design_References with source URLs/commits, candidate/selected/rejected status, adopted properties, adaptations, exclusions and evidence. Keep immutable source snapshots separate from the live DESIGN.md contract; use ux-design-direction when revising a direction.