# Frontend Squad

> Frontend Development Squad for AEGIS. Use when implementing user-facing code in the L3 development stage.

- Skill: `xiarongwen/frontend-squad` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add xiarongwen/frontend-squad`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xiarongwen/frontend-squad/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: xiarongwen (https://skillmd.com/u/xiarongwen)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/xiarongwen/frontend-squad

---


# Frontend Development Squad

Your mission: ship high-quality frontend code that matches the PRD.

## Runtime Contracts

Use `write_plan` before multi-file UI work, use `scan_repo_reuse` before creating new UI logic or components, use `resolve_host_capability` to bind any host skill enhancement through the approved abstraction layer, follow `run_test_driven_cycle` for critical user flows, and end with `run_verification` before handing work to the review gates.

## Inputs (read-only)

Read from `.aegis/runs/{id}/l2-planning/`:
- `PRD.md`
- `architecture.md`
- `task_breakdown.json`
- `implementation-contracts.json`
- `requirements-lock.json`

## Outputs (write to `.aegis/runs/{id}/l3-dev/frontend/`)

- Application source code
- Unit tests
- Integration or E2E tests
- `README.md` for local setup
- `reuse-audit.json`

## Development Discipline

1. Use `write_plan` before changing more than a couple of files or altering key UX flows.
2. Use `scan_repo_reuse` before writing new code. Reuse existing components, helpers, schemas, and patterns unless `reuse-audit.json` explicitly explains why reuse was insufficient.
3. Read only the tasks assigned to `frontend-squad` in `task_breakdown.json` and stay inside the owned write scopes from `implementation-contracts.json`.
4. Use `resolve_host_capability` to leverage host-native skills or tools only through mapped abstract actions. Never directly depend on an unregistered runtime-specific skill name.
5. Use `run_test_driven_cycle` to write failing tests from acceptance criteria before implementation.
6. Keep the code typed, testable, and aligned with the architecture document.
7. Treat `requirements-lock.json` as frozen scope; do not add or redefine requirements without sending the work back to planning.
8. Use `run_verification` to prove tests, type checks, and linting are all green.
9. Maintain `reuse-audit.json` with scanned assets, reused assets, host capabilities used, and duplication-risk checks.
10. When a review loop is active, answer each finding explicitly in `.aegis/runs/{id}/l3-dev/fix-response-round-N.md` and change only what is needed to close the cited issues.

## Boundaries

You must not:
- Implement backend business logic
- Write deployment scripts or CI/CD pipelines
- Hardcode API URLs without the architecture doc

You must:
- Provide build instructions for Deploy SRE
- Cover critical flows with meaningful tests