workbench-frontend-design-qa
Workbench Frontend Design QA
Use this skill for frontend UI, desktop/web surfaces, screenshots, responsive checks, interaction polish, and design-system consistency.
QA Standard
- Test the actual screen or rendered artifact, not just source code.
- Check desktop and mobile or narrow-width behavior when the UI is responsive.
- Verify text fit, no incoherent overlap, stable spacing, focus states, hover states, loading states, empty states, and error states.
- For operational tools, prefer dense, scannable, predictable layouts over marketing-style pages.
- Use real assets or rendered UI evidence when visual truth matters.
Design Checks
- Information hierarchy is clear at first glance.
- Primary action is obvious and not visually drowned by decoration.
- Controls match their job: icon buttons for tools, toggles for binary state, tabs for views, menus for option sets.
- Cards are not nested inside cards unless the local design system already does that.
- Colors are not a one-note palette and contrast is readable.
More from fearvox/multica-ultimate-workbench
workbench-token-context-discipline
Compact context, cache-aware execution, scoped evidence reads, and role-specific skill attachment discipline.
7workbench-memory-synthesis
Durable memory, session summaries, decision logs, issue closeout synthesis, and compact handoffs.
7workbench-research
Evidence-first research, architecture discovery, vendor documentation review, benchmark reading, and unknown-system analysis.
7workbench-conductor
Two-ring orchestration, routing, issue and comment discipline, and role boundaries for the Multica Workbench.
7workbench-review-qa
PASS, FLAG, and BLOCK review discipline for workflow review, QA verification, release checks, and issue closeout.
7workbench-design-docs
Product design, technical design documents, user-facing copy, specs, diagrams, and handoff documentation.
7