How do I install the Multica Review Frontend skill?

Run npx skillmds@latest add it235/multica-review-frontend in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Multica Review Frontend safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Multica Review Frontend?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Multica Review Frontend free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Multica Review Frontend?

it235 (@it235) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Multica Review Frontend by it235 — Agent Skill

Name: Multica Review Frontend
Rating: 4.2 (5 reviews)
Author: it235

Multica Review Frontend

Frontend-implementation dedicated review framework. Called by FrontendReviewer to professionally analyze FrontendDev's output (UI/API-contract fit/component quality/unit-test sufficiency/acceptance mapping), output PASS/FAIL + fix list, report to Leader.

it235 Updated Sep 22, 2026

File contents

Frontend Implementation Professional Review (FrontendReviewer)

Structured professional review framework for frontend implementation artifacts. Called by FrontendReviewer; reviews the changed-file list / repo ref FrontendDev returns via code-class skill, plus the UI link + API contract link Leader passes.

When to use

FrontendReviewer receives a "review frontend implementation" dispatch from Leader.
Entering a re-review round after implementation changes (check previous round's fix list item by item).

Review dimensions (conclusion per item)

UI fit: layout, interaction, states, edge states aligned with Designer output.
API-contract fit: call params, response handling, error branches aligned with BackendDev contract.
Component quality: reusability, single responsibility, no obvious smells.
Unit-test sufficiency: key paths, boundaries, async/error branches covered; no无效的 tests padded for coverage (mark & block).
Acceptance mapping: implementation truly satisfies every AC-.

Output format

【Frontend Review】<change link>
Conclusion: PASS / FAIL
Blocking items (required on FAIL, each: rationale / involved point / fix direction):
- ...
Suggestions (non-blocking):
- ...
Previous fix-list check (re-review): resolved X / unresolved Y
Round: N / 3

Conclusion + fix list reported to Leader; don't modify code or notify FrontendDev yourself.

Boundaries

Review only frontend implementation & unit tests, not architecture, requirements, UI design, backend, or test cases.
Don't replace Leader's generic gate (multica-verification skill).
Still FAIL at round 3 → mark "escalate to human", hand to Leader, stop looping.

---name: multica-review-frontenddescription: Frontend-implementation dedicated review framework. Called by FrontendReviewer to professionally analyze FrontendDev's output (UI/API-contract fit/component quality/unit-test sufficiency/acceptance mapping), output PASS/FAIL + fix list, report to Leader.---# Frontend Implementation Professional Review (FrontendReviewer)Structured professional review framework for **frontend implementation artifacts**. Called by `FrontendReviewer`; reviews the changed-file list / repo ref `FrontendDev` returns via code-class skill, plus the UI link + API contract link Leader passes.## When to use- FrontendReviewer receives a "review frontend implementation" dispatch from Leader.- Entering a re-review round after implementation changes (check previous round's fix list item by item).## Review dimensions (conclusion per item)1. **UI fit**: layout, interaction, states, edge states aligned with Designer output.2. **API-contract fit**: call params, response handling, error branches aligned with BackendDev contract.3. **Component quality**: reusability, single responsibility, no obvious smells.4. **Unit-test sufficiency**: key paths, boundaries, async/error branches covered; no无效的 tests padded for coverage (mark & block).5. **Acceptance mapping**: implementation truly satisfies every AC-.## Output format```【Frontend Review】<change link>Conclusion: PASS / FAILBlocking items (required on FAIL, each: rationale / involved point / fix direction):- ...Suggestions (non-blocking):- ...Previous fix-list check (re-review): resolved X / unresolved YRound: N / 3```Conclusion + fix list **reported to Leader**; don't modify code or notify FrontendDev yourself.## Boundaries- Review only frontend implementation & unit tests, not architecture, requirements, UI design, backend, or test cases.- Don't replace Leader's generic gate (multica-verification skill).- Still FAIL at round 3 → mark "escalate to human", hand to Leader, stop looping.

Frequently asked questions