
Agy Ui Director V2
Turn vague UI goals into polished screens by driving the agy CLI through brief, run, harsh review, and refine loops.
Install
npx skills add https://github.com/shahid0/mobile-development-ai-skills --skill agy-ui-director-v2What is this skill?
- Inspects agy CLI (--print, --prompt-interactive, --add-dir, --model) before running in a new environment
- Transforms rough intent into a decisive brief, then runs agy and reviews visible UI harshly
- Supports iterative refine-until-strong loops with model selection (Gemini 3.5 Flash tiers, Claude Sonnet/Opus thinking,
- Documents sandbox vs normal runs so permission prompts do not interrupt UI implementation flow
- Quality-first operator pattern: discover commands → brief → execute → critique → refine
Adoption & trust: 1 installs on skills.sh; 2 GitHub stars; trending (+100% hot-view momentum).
Recommended Skills
Frontend Designanthropics/skills
Vercel React Best Practicesvercel-labs/agent-skills
Remotion Best Practicesremotion-dev/skills
Vercel Composition Patternsvercel-labs/agent-skills
Develop Userscriptsxixu-me/skills
Next Best Practicesvercel-labs/next-skills
Journey fit
Primary fit
Canonical shelf is Build because the skill’s core output is implemented UI in the codebase, even though planning and critique happen first. Frontend is the primary facet: visible UI quality, layout, and component-level refinement dominate the workflow.
SKILL.md
READMESKILL.md - Agy Ui Director V2
interface: display_name: "Agy UI Director V2" short_description: "Operate agy from rough intent to strong UI" default_prompt: "Use $agy-ui-director-v2 as a quality-first agy operator: inspect the app, gather useful context, transform my rough intent into a decisive brief, run agy, review the visible UI harshly, and refine until the result is genuinely strong." # agy CLI Usage ## Discover Before Running Before invoking `agy` in a new environment, inspect the available command shape: ```bash command -v agy agy --help agy models ``` The verified local command shape supports: - `--print`, `-p`, or `--prompt` for one non-interactive prompt. - `--prompt-interactive` or `-i` for an initial prompt followed by an interactive session. - `--print-timeout` for print-mode timeout, default `5m0s`. - `--add-dir` as a repeatable workspace directory flag. - `--model` for model selection. - `--continue` or `-c` to continue the most recent conversation. - `--conversation` to resume a conversation by ID. - `--sandbox` to run with terminal restrictions. Normal UI implementation runs omit it because repeated permission prompts can interrupt `agy`'s flow. - `--dangerously-skip-permissions`, reserved for exact user-approved cases. Available models seen during skill creation: - `Gemini 3.5 Flash (Medium)` - `Gemini 3.5 Flash (High)` - `Gemini 3.5 Flash (Low)` - `Gemini 3.1 Pro (Low)` - `Gemini 3.1 Pro (High)` - `Claude Sonnet 4.6 (Thinking)` - `Claude Opus 4.6 (Thinking)` - `GPT-OSS 120B (Medium)` Re-run `agy models` in the active environment before hardcoding a model name. Default model for UI work: ```text Gemini 3.5 Flash (High) ``` Use this model for normal `agy` UI runs unless the user explicitly requests another model or the model is unavailable. ## Invocation Principles - Run from the project root unless the CLI documentation requires another working directory. - Scope each run to one screen. - The verified prompt form is a positional prompt string after `--print`, `-p`, or `--prompt`. - For multi-paragraph prompts, keep the prompt in a local file and pass its content as the prompt string. Keep the prompt concise unless the task genuinely needs more detail. - Omit `--print-timeout` for normal UI implementation runs. Use it only when the user explicitly asks for a timeout. - Omit `--sandbox` for normal UI implementation runs. Use it only when the user explicitly asks for sandboxing. - Capture the raw `agy` output and the changed-file list before editing further. - Keep secrets, API keys, private credentials, and unrelated files out of the prompt. - Run destructive commands only with exact user approval. - If `agy` is unavailable, return the final implementation brief and explain that the CLI was not present. ## Exact Command Patterns Use these patterns from the project root. ### Non-interactive one-screen implementation ```bash PROMPT_FILE="/absolute/path/to/agy-screen-brief.md" PROJECT_ROOT="/absolute/path/to/project" agy --model "Gemini 3.5 Flash (High)" --add-dir "$PROJECT_ROOT" --print "$(cat "$PROMPT_FILE")" ``` ### Non-interactive one-screen implementation with a selected model ```bash PROMPT_FILE="/absolute/path/to/agy-screen-brief.md" PROJECT_ROOT="/absolute/path/to/project" agy --model "<model-name>" --add-dir "$PROJECT_ROOT" --print "$(cat "$PROMPT_FILE")" ``` ### Interactive one-screen session Use this only when the user wants to manually guide the `agy` session: ```bash PROMPT_FILE="/absolute/path/to/agy-screen-brief.md" PROJECT_ROOT="/absolute/path/to/project" agy --model "Gemini 3.5 Flash (High)" --add-dir "$PROJECT_ROOT" --prompt-interactive "$(cat "$PROMPT_FILE")" ``` ### Continue the latest session ```bash agy --continue ``` ### Resume a known conversation ```bash agy --conversation "<conversation-id>" ``` Use continuation only to refine the same one-screen task unless the user explicitly starts a new task. ## What to Give agy Give `agy` a concise creative-aperture implementation brief: - Pr