New Capability: Repo Review Command + UX Quality Enforcement
Date: April 3, 2026 Origin: Chris shared https://github.com/Cornjebus/neo-user-journey for evaluation. The review surfaced a recurring need: structured evaluation of external repos for cherry-picking, plus a gap in UX quality enforcement for the interactive applications we build. Impact: The team can now evaluate any GitHub repo in under 5 minutes with multi-leader assessment, and Mirror/Showcase have concrete UX anti-pattern and accessibility testing infrastructure.
What Was Built
Three artifacts from one repo review:
1. /repo-review slash command — A structured evaluation process for external GitHub repositories. When Chris shares a repo URL, the full leadership team (V, Sage, Pax, Aegis) evaluates it against our Dewey-classified platform. Output: cherry-pick recommendations with exact source/destination paths, leader assessments, and discard rationale. Saved to docs/reviews/ for future reference. Default expectation is cherry-pick, never merge.
2. skills/enforcement/ux-anti-patterns.md — UX quality enforcement reference adapted from neo-user-journey's ANTI-PATTERNS.md. Covers 4 categories (Visual, Copy, Interaction, Architecture) with 20 specific anti-patterns, each reframed for our platform. References our brand colors, portal sections, Command Center, Core Beliefs, and language guide. Owned by Mirror and Showcase.
3. apps/website/tests/accessibility-audit.spec.ts — WCAG 2.1 AA compliance test suite adapted from neo-user-journey's Playwright accessibility tests. 6 test suites: axe-core full scan, keyboard navigation, touch targets (44px minimum), form labels, color contrast, and cross-page summary. Configured for 10 high-traffic pages. Uses @axe-core/playwright (newly installed as devDependency).
Infrastructure Changes
| Change | Before | After |
|---|---|---|
/repo-review command |
Did not exist | .claude/commands/repo-review.md |
| UX enforcement | No UX-specific enforcement skill | skills/enforcement/ux-anti-patterns.md |
| Accessibility testing | No WCAG testing capability | apps/website/tests/accessibility-audit.spec.ts |
@axe-core/playwright |
Not installed | Added to website devDependencies |
| Codebase index (410) | 7 enforcement skills listed | 8 enforcement skills (added ux-anti-patterns.md) |
Implementation
| File | Purpose |
|---|---|
.claude/commands/repo-review.md |
Slash command: multi-leader external repo evaluation |
skills/enforcement/ux-anti-patterns.md |
UX quality enforcement reference (Dewey 410) |
apps/website/tests/accessibility-audit.spec.ts |
WCAG 2.1 AA Playwright test suite |
apps/website/package.json |
Added @axe-core/playwright devDependency |
Usage
/repo-review
/repo-review https://github.com/owner/repo
/repo-review https://github.com/owner/repo "area of interest"
Produces: docs/reviews/{date}-{repo-name}.md
Accessibility Audit
cd apps/website && npx playwright test accessibility-audit.spec.ts
Tests 10 pages against WCAG 2.1 AA. Critical rule failures (color-contrast, image-alt, label, link-name, button-name) cause test failure. Other violations are reported as warnings.
UX Anti-Patterns
Referenced by Mirror during visual QA and Showcase during portal builds. Not a runnable script — it's enforcement reference material loaded when evaluating UI quality.
Leader Applications
V (Operations)
Primary beneficiary. /repo-review standardizes a recurring workflow — Chris shares repos regularly, and before today the evaluation was ad-hoc. The accessibility audit adds a new dimension to our Playwright test infrastructure (joining episode audits, profile audits, and episode quality scoring). The UX anti-patterns skill gives Mirror and Showcase concrete criteria instead of subjective "looks good."
Sage (Customer)
The UX anti-patterns directly affect client portal quality. Portal sections (Dashboard, Documents, Roadmap, SubwayMapV3) are interactive applications that real people use. Patterns like "Everything-on-Dashboard," "Modal Hell," and "Hover-Dependent UI" are risks in our portal. Accessibility compliance also matters — client team members may have accessibility needs we don't know about.
Pax (Finance)
No direct financial application. Indirectly, accessibility compliance reduces legal risk, and higher UX quality supports client retention.
Dependencies
| Dependency | Status | Notes |
|---|---|---|
| Playwright + Chromium | Confirmed | Already installed for website tests |
@axe-core/playwright |
Confirmed | Installed via pnpm, v4.11.1 |
| Production website | Confirmed | Tests run against valuefirstteam.com |
| WebFetch (for /repo-review) | Confirmed | Available via Claude Code |
| GitHub MCP tools | Confirmed | Available for repo file access |
Verification
# Verify accessibility audit runs
cd apps/website && npx playwright test accessibility-audit.spec.ts --reporter=list
# Verify enforcement skill exists
cat skills/enforcement/ux-anti-patterns.md | head -5
# Verify command exists
cat .claude/commands/repo-review.md | head -3
Feedback Captured
During the review, V undersold the platform as "mostly configuring HubSpot + building Astro pages." Chris corrected this — we build novel interactive interfaces (28-section portal with SubwayMapV3 canvas, Command Center, RPG walkthroughs, interactive assessments). This feedback is now in memory as feedback_novel_interfaces.md and classified as scope-reduction enforcement (same category as "quick wins" and "start simple").