fix-ui

⚠️ Anti-Hallucination Reminder

Before modifying ANY code: Verify assumptions with actual code evidence. Search for usages, read implementations, trace dependencies. If confidence < 90% on any change, investigate first or ask user. See

.claude/skills/shared/anti-hallucination-protocol.md

for full protocol.

Required Skills (Priority Order)

ui-ux-pro-max
- Design intelligence database (ALWAYS ACTIVATE FIRST)
frontend-design
- Implementation patterns

Use

ui-ux-designer

subagent to read and analyze

./docs/design-guidelines.md

then fix the following issues: <issue>$ARGUMENTS</issue>

Workflow

FIRST: Run

ui-ux-pro-max

searches to understand context and common issues:

bash

python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "accessibility" --domain ux
python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "z-index animation" --domain ux

If the user provides a screenshots or videos, use

ai-multimodal

skill to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.

Use
```
ui-ux-designer
```
subagent to implement the fix step by step.
Use screenshot capture tools along with
```
ai-multimodal
```
skill to take screenshots of the implemented fix (at the exact parent container, don't take screenshot of the whole page) and use the appropriate Gemini analysis skills (
```
ai-multimodal
```
,
```
video-analysis
```
, or
```
document-extraction
```
) to analyze those outputs so the result matches the design guideline and addresses all issues.

If the issues are not addressed, repeat the process until all issues are addressed.

Use
```
test-ui
```
skill to analyze the implemented fix and make sure it matches the design guideline.
Use
```
tester
```
agent to test the fix and compile the code to make sure it works, then report back to main agent.

If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.

Project Management & Documentation: If user approves the changes: Use
```
project-manager
```
and
```
docs-manager
```
subagents in parallel to update the project progress and documentation:
- Use
```
project-manager
```
  subagent to update the project progress and task status in the given plan file.
- Use
```
docs-manager
```
  subagent to update the docs in
```
./docs
```
  directory if needed.
- Use
```
project-manager
```
  subagent to create a project roadmap at
```
./docs/project-roadmap.md
```
  file.
- IMPORTANT: Sacrifice grammar for the sake of concision when writing outputs. If user rejects the changes: Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
Final Report:

Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
Ask the user if they want to commit and push to git repository, if yes, use
```
git-manager
```
subagent to commit and push to git repository.
IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.
IMPORTANT: In reports, list any unresolved questions at the end, if any.

REMEMBER:

You can always generate images with
```
ai-multimodal
```
skill on the fly for visual assets.
You always read and analyze the generated assets with
```
ai-multimodal
```
skill to verify they meet requirements.
For image editing (removing background, adjusting, cropping), use
```
ImageMagick
```
skill or similar tools as needed.
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.

IMPORTANT Task Planning Notes

Always plan and break many small todo tasks
Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

fix-ui

NPX Install

Tags

SKILL.md Content

⚠️ Anti-Hallucination Reminder

Required Skills (Priority Order)

Workflow

IMPORTANT Task Planning Notes