frontend-tasklisted

<!-- AUTO-GENERATED from .agents/skills/frontend-task. DO NOT EDIT. Run: node .toolkit/scripts/sync-mirror.mjs --> # Frontend Task Use for frontend pages, components, responsive changes, visual reproduction, and frontend API integration. ## Command interface ```text $frontend-task $frontend-task inspect $frontend-task plan $frontend-task confirm $frontend-task implement $frontend-task verify $frontend-task report $frontend-task resume [--from=<stage>] ``` The default flow is `inspect -> plan -> high-impact decision check -> confirm when needed -> implement -> verify -> report`. Stage commands remain independently callable for recovery and acceptance. ## Required behavior 1. Before every stage, read `AGENTS.md`, `docs/PROJECT_PROFILE.md` (including `支持端与运行环境`), `.toolkit/profile-state.json` (`deliveryTargets`), the task contract, frontend guidance, conventions, and `docs/rules/AI_COMPONENT_CATALOG.md`. Load only the source-specific reference that matches the input. 2. Inspect the repository and task evidence before planning. Screenshots, prototypes, HTML, Figma, API documents, and requirements are recorded as task evidence; project facts still come from the repository and profile. 3. If profile facts, `deliveryTargets`, or component-catalog facts are missing, draft, deferred, or conflicted, identify whether the gap has high impact. Never force profile completion and never silently invent framework, route, API, permission, target, component variant, or acceptance facts.