You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: "Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization."
Copy file name to clipboardExpand all lines: .claude/agents/vc-execute-agent.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
name: execute-agent
3
3
description: EXECUTE MODE - Implementing EXACTLY what was planned. Full tool access. Can only be invoked after explicit user confirmation. Use after plan is approved.
Copy file name to clipboardExpand all lines: .claude/agents/vc-fast-mode-agent.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
name: fast-mode-agent
3
3
description: FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + INNOVATE + PLAN) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
Copy file name to clipboardExpand all lines: .claude/agents/vc-ui-ux-designer.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,15 @@
2
2
name: ui-ux-designer
3
3
description: 'Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n<example>\nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern landing page for our SaaS product with a hero section, features, and pricing"\nassistant: "I''ll use the ui-ux-designer agent to translate that approved direction into a polished implementation plan and UI output."\n<commentary>The user is requesting UI/UX execution work, so delegate to the ui-ux-designer agent to handle the design-aware implementation and polish.</commentary>\n</example>\n\n<example>\nContext: User has implemented a new feature and wants design review\nuser: "I''ve added a new dashboard widget, can you review the design?"\nassistant: "Let me first capture the current UI and then use the ui-ux-designer agent to analyze and provide design recommendations."\n<commentary>Use screenshot tools to capture current state, then delegate to ui-ux-designer for expert design analysis and suggestions.</commentary>\n</example>\n\n<example>\nContext: User mentions design inconsistencies\nuser: "The buttons across different pages look inconsistent"\nassistant: "I''ll use the ui-ux-designer agent to audit the design system and propose a more consistent implementation."\n<commentary>Design-system work requires the ui-ux-designer agent to analyze, document, and improve consistent design patterns.</commentary>\n</example>\n\n<example>\nContext: Proactive design optimization opportunity\nuser: "Here''s the new signup form I just built"\nassistant: "Let me use the ui-ux-designer agent to review the form design for accessibility, user experience, and mobile responsiveness."\n<commentary>Even without an explicit design brief, ui-ux-designer can help ensure design quality and best practices during execute-phase polish.</commentary>\n</example>'
This agent is callable from RIPER-5 EXECUTE phase for UI/UX implementation, design review, and accessibility polish tasks.
11
12
12
-
**Read `process/context/all-context.md` first for context routing, then read `process/context/uxui/uiux.md` and any relevant grouped UI context docs for project-specific UI patterns, component library, and design conventions.** When validation, browser testing, or runtime verification is part of the task, also read `process/context/tests/all-tests.md` before deeper test docs.
13
+
**Read `process/context/all-context.md` first for context routing, then read the project's UI/UX context doc (if present) and any relevant grouped UI context docs for project-specific UI patterns, component library, and design conventions.** When validation, browser testing, or runtime verification is part of the task, also read `process/context/tests/all-tests.md` before deeper test docs.
13
14
14
15
When the orchestrator passes `Work context`, `Feature`, `Reports`, `Plans`, or one exact selected plan file path, treat those as authoritative scope hints. If `Feature:` is present, use the matching `process/features/{feature}/reports/` and `references/` surfaces instead of assuming general locations. Treat direct `*_PLAN_*.md`, legacy `PLAN.md`, legacy `plan.md`, and active `phase-*` files as valid compatibility shapes when following a selected UI task plan.
- Container/Docker/service changes → the relevant container/runtime context doc
110
110
- Test patterns/commands/frameworks → `process/context/tests/all-tests.md` or deeper `process/context/tests/*.md`
111
111
- Architecture/API/conventions/env vars → `all-context.md`
112
112
- UI/UX patterns/components → `uiux.md`
113
-
- Skill runtime/app changes → `skill-apps.md` or `flowser-skills.md`
113
+
- Skill runtime/app changes → the relevant skill-app or skill-system context doc
114
114
- Workflow package changes → `cf-workflows.md`
115
115
- Known bugs/tech debt → `process/general-plans/backlog/backlog.md` or `process/features/{feature}/backlog/`
116
116
- New context file needed → create it in the owning group when one exists, otherwise root; update `process/context/all-context.md` and the owning `all-{group}.md`
@@ -265,13 +265,13 @@ For each approved improvement:
0 commit comments