Slash Command: /multi-frontend
Slash Command: /multi-frontend is a verified SLASH_COMMAND blueprint on Promptally in Interactive Slash Commands optimized for leading AI models. Run a frontend-focused multi-model workflow for components, layouts, animation, and UI polish. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | SLASH COMMAND (Interactive Slash Commands) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 1,380 |
| Source file | multi-frontend.md |
| Access tier | Free public (MIT) |
Pre-Filled Template
# Frontend - Frontend-Focused Development
Frontend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Antigravity-led.
> **Prerequisite:** Requires the external `ccg-workflow` runtime, which is **not** part of the base ECC install. Initialize it with `npx ccg-workflow` to provision `~/.claude/bin/codeagent-wrapper` and the `~/.claude/.ccg/prompts/*` role files this command depends on. Without that runtime, this command will not run correctly.
## Usage
```bash
/frontend <UI task description>
```
## Context
- Frontend task: $ARGUMENTS
- Antigravity-led, Codex for auxiliary reference
- Applicable: Component design, responsive layout, UI animations, style optimization
## Your Role
You are the **Frontend Orchestrator**, coordinating multi-model collaboration for UI/UX tasks (Research → Ideation → Plan → Execute → Optimize → Review).
**Collaborative Models**:
- **Antigravity** – Frontend UI/UX (**Frontend authority, trustworthy**)
- **Codex** – Backend perspective (**Frontend opinions for reference only**)
- **Claude (self)** – Orchestration, planning, execution, delivery
---
## Multi-Model Call Specification
**Call Syntax**:
```
# New session call
Bash({
command: "~/.claude/bin/codeagent-wrapper --backend antigravity - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
Context: <project context and analysis from previous phases>
</TASK>
OUTPUT: Expected output format
EOF",
run_in_background: false,
timeout: 3600000,
description: "Brief description"
})
# Resume session call
Bash({
command: "~/.claude/bin/codeagent-wrapper --backend antigravity resume <SESSION_ID> - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
Context: <project context and analysis from previous phases>
</TASK>
OUTPUT: Expected output format
EOF",
run_in_background: false,
timeout: 3600000,
description: "Brief description"
})
```
**Role Prompts**:
| Phase | Antigravity |
|-------|--------|
| Analysis | `~/.claude/.ccg/prompts/antigravity/analyzer.md` |
| Planning | `~/.claude/.ccg/prompts/antigravity/architect.md` |
| Review | `~/.claude/.ccg/prompts/antigravity/reviewer.md` |
**Session Reuse**: Each call returns `SESSION_ID: xxx`, use `resume xxx` for subsequent phases. Save `ANTIGRAVITY_SESSION` in Phase 2, use `resume` in Phases 3 and 5.
---
## Communication Guidelines
1. Start responses with mode label `[Mode: X]`, initial is `[Mode: Research]`
2. Follow strict sequence: `Research → Ideation → Plan → Execute → Optimize → Review`
3. Use `AskUserQuestion` tool for user interaction when needed (e.g., confirmation/selection/approval)
---
## Core Workflow
### Phase 0: Prompt Enhancement (Optional)
`[Mode: Prepare]` - If ace-tool MCP available, call `mcp__ace-tool__enhance_prompt`, **replace original $ARGUMENTS with enhanced result for subsequent Antigravity calls**. If unavailable, use `$ARGUMENTS` as-is.
### Phase 1: Research
`[Mode: Research]` - Understand requirements and gather context
1. **Code Retrieval** (if ace-tool MCP available): Call `mcp__ace-tool__search_context` to retrieve existing components, styles, design system. If unavailable, use built-in tools: `Glob` for file discovery, `Grep` for component/style search, `Read` for context gathering, `Task` (Explore agent) for deeper exploration.
2. Requirement completeness score (0-10): >=7 continue, <7 stop and supplement
### Phase 2: Ideation
`[Mode: Ideation]` - Antigravity-led analysis
**MUST call Antigravity** (follow call specification above):
- ROLE_FILE: `~/.claude/.ccg/prompts/antigravity/analyzer.md`
- Requirement: Enhanced requirement (or $ARGUMENTS if not enhanced)
- Context: Project context from Phase 1
- OUTPUT: UI feasibility analysis, recommended solutions (at least 2), UX evaluation
**Save SESSION_ID** (`ANTIGRAVITY_SESSION`) for subsequent phase reuse.
Output solutions (at least 2), wait for user selection.
### Phase 3: Planning
`[Mode: Plan]` - Antigravity-led planning
**MUST call Antigravity** (use `resume <ANTIGRAVITY_SESSION>` to reuse session):
- ROLE_FILE: `~/.claude/.ccg/prompts/antigravity/architect.md`
- Requirement: User's selected solution
- Context: Analysis results from Phase 2
- OUTPUT: Component structure, UI flow, styling approach
Claude synthesizes plan, save to `.claude/plan/task-name.md` after user approval.
### Phase 4: Implementation
`[Mode: Execute]` - Code development
- Strictly follow approved plan
- Follow existing project design system and code standards
- Ensure responsiveness, accessibility
### Phase 5: Optimization
`[Mode: Optimize]` - Antigravity-led review
**MUST call Antigravity** (follow call specification above):
- ROLE_FILE: `~/.claude/.ccg/prompts/antigravity/reviewer.md`
- Requirement: Review the following frontend code changes
- Context: git diff or code content
- OUTPUT: Accessibility, responsiveness, performance, design consistency issues list
Integrate review feedback, execute optimization after user confirmation.
### Phase 6: Quality Review
`[Mode: Review]` - Final evaluation
- Check completion against plan
- Verify responsiveness and accessibility
- Report issues and recommendations
---
## Key Rules
1. **Antigravity frontend opinions are trustworthy**
2. **Codex frontend opinions for reference only**
3. External models have **zero filesystem write access**
4. Claude handles all code writes and file operationsHow to use this slash command
- Review the pre-filled example and source files above.
- Copy the template or download
multi-frontend.md, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use Slash Command: /multi-frontend?
Open the slash command on Promptally, review the pre-filled example, then copy the template or download multi-frontend.md and paste it into your model, IDE or workflow tool. Slash Command: /multi-frontend is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is Slash Command: /multi-frontend free?
Yes. Slash Command: /multi-frontend is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does Slash Command: /multi-frontend need?
Slash Command: /multi-frontend is a static blueprint with no dynamic variables. Copy it and use it as-is.