Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From PWDEV Feat — Fast Feature Plans & Execution
Create a frontend-focused action plan — components, pages, composables, E2E tests with Playwright.
How this command is triggered — by the user, by Claude, or both
Slash command
/pwdev-feat:frontend [frontend task description]The summary Claude sees in its command listing — used to decide when to auto-load this command
# /pwdev-feat:frontend — Create Frontend Plan
## Method (inline — you run in the MAIN context)
You are PWDEVIA. Follow `${CLAUDE_PLUGIN_ROOT}/references/pwdevia-method.md`
end-to-end: read context, interview the human (max 2 rounds), answer the
7 questions, generate `.planning/feat/features/{slug}/plan.md`, present the
summary. No Task tool, no model resolution.
## Input
$ARGUMENTS: frontend task description (required).
## Plan Type
**Frontend** — components, pages, composables/hooks, styles, E2E tests.
## Flow
### STEP 0 — Language
Follow `${CLAUDE_PLUGIN_ROOT}/references/language.md`...You are PWDEVIA. Follow ${CLAUDE_PLUGIN_ROOT}/references/pwdevia-method.md
end-to-end: read context, interview the human (max 2 rounds), answer the
7 questions, generate .planning/feat/features/{slug}/plan.md, present the
summary. No Task tool, no model resolution.
$ARGUMENTS: frontend task description (required).
Frontend — components, pages, composables/hooks, styles, E2E tests.
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
npx claudepluginhub pwdev-solucoes/pwdev-claude-marketplace --plugin pwdev-feat/frontendAudits a pull request for frontend quality issues including React lifecycle, server/client components, type safety, accessibility, and performance.
/frontendOptimizes frontend architecture and performance for a given requirement (required) and optional focus (e.g., "Optimize bundle size" performance).
/frontendScaffolds customizable React + Vite + TypeScript frontend with routing, state management, Tailwind CSS, auth, API integration, tests, and production configs.
/frontendRuns a multi-lens quality review for GreyCat frontend projects, covering correctness, stack compliance (Lit/Web Awesome/@greycat/web), TypeScript safety, performance, Lighthouse/SEO, and testing. Accepts keyword arguments to limit the scope or 'help' for a table of lenses.
/frontendProduces polished frontend UIs by applying a curated set of design skills: tokens, layout patterns, accessible components, reference matching, and accessibility/design review.