# Multica Frontend Impl

> Frontend implementation skill—page/component/state/style coding conventions and acceptance checklist; the preferred mount for @FrontendDev.

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

---


# Frontend Implementation (frontend-impl)

## Responsibility
As @FrontendDev, implement pages/components/state/style per the designer's `multica-design-ui-impl` output, then push the deliverable set to `frontend-artifact` via `multica-artifact-frontend`.

## Conventions
- Component/state management follows the project's agreed stack.
- UI must match the design's states (normal/empty/error/loading).
- Reusable components go through the design system.

## Acceptance checklist
- [ ] Pages implement all design states
- [ ] Responsive/layout matches design
- [ ] No hardcoded credentials/URLs
- [ ] run-url reachable after build

## Flow
1. Read upstream design links from `multica-design-ui-impl`.
2. Implement pages/components.
3. Self-check against the checklist.
4. Push to `frontend-artifact` (`multica-artifact-frontend`), then hand off to @Reviewer (G1) and @Tester (T1/T2/T3).