review-design
Frontend Design Quality Review
Announce: "I'm using enggenie:review-design to review the frontend implementation."
Overview
Review frontend code for design quality - not just "does it work" but "does it look and feel professional." Catches the gap between functional code and production-quality UI.
Jira Ticket Entry
When the user references a Jira ticket for design review (e.g., "Check design for PROJ-1234", "Review UI on PROJ-1234"):
- Read the Jira ticket using MCP tools
- Find the spec link — extract Figma references, design tokens, layout requirements, and responsive breakpoints documented by PM
- Find the "Dev Handoff" comment — extract the PR link and what was built
- Use the spec's design requirements as the review baseline — compare implementation against what was specified, not against generic best practices alone
If Jira MCP is not available, ask: "I can't read PROJ-1234 directly. Can you share the design specs or Figma link?"
More from badrusiddique/enggenie-skill
dev-implement
Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment
10dev-tdd
Use when writing any code - enforces test-driven development discipline with RED-GREEN-REFACTOR cycle, fires during any coding task
9architect-plan
Use when creating implementation plans from specs or requirements - phased task breakdown with deployment readiness gates before any coding begins
9review-code
Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation
9memory-recall
Use when asking about previous sessions - cross-session context search via claude-mem with token-efficient 3-layer retrieval
9architect-design
Use when brainstorming new features, making architectural decisions, evaluating technical tradeoffs, or documenting decisions as ADRs - before any implementation planning or coding begins
9