القائمة
UX design critique with staff-level evaluation. Use when reviewing UI/UX, critiquing designs, or before shipping a UI feature.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.
QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.
Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.
Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.
Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.
Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.
| name | ux-critique |
| description | UX design critique with staff-level evaluation. Use when reviewing UI/UX, critiquing designs, or before shipping a UI feature. |
| user-invocable | true |
| extends | git+git@github.com:ugudlado/prompt-packs.git@302b87dcc7c8b6a83d249194f3e47e98d3214794#ux-reviewer |
Intent: Run UX critique on UI changes and iterate until the target score is met.
None named. (Reads modified files in the phase.)
critique_scorecritique_skippedcritique_retriesQuality thresholds are step-owned (vendor this pack to change them):
Check if any files modified in this phase touch UI: Match: _.html, _.css, _.scss, _.tsx, _.jsx, _.svelte, _.vue, _.astro, or files in components/, pages/, views/, layouts/, templates/.
If NO UI files modified → skip. Log: "[critique] No UI changes — skipping"
Perform UX critique directly on:
Read SCORE and STATUS from your critique output.
If score >= target_score: PASS. Record critique_score in state.yaml.
If score < target_score: a. Parse PRIORITY_ISSUES from agent output into fix tasks. b. Apply fixes scoped to critique findings only. c. Run the repo's verify commands (as discovered from CLAUDE.md / AGENTS.md / README / manifest conventions) to confirm nothing broke. d. Increment retry counter in state.yaml. e. Re-run critique on updated files. f. If retries >= max_retries: STOP and escalate to user.
Commit UX improvements:
style(<change-id>): UX critique improvements (score: N/10)
After verify passes (or on skip), return:
COMPLETION:
status: completed
outputs:
critique_score: <N or null if skipped>
critique_skipped: <true if no UI files, false otherwise>
critique_retries: <N>