| name | development-frontend |
| description | Define baseline frontend engineering standards and legacy project audits. Use when users need project setup/configuration for Node.js + vite-plus workflows, commit/release governance, or compliance gap analysis against the frontend baseline. |
Frontend Development
Purpose
Use this skill to standardize frontend engineering workflows for both new and existing projects:
- Bootstrap and normalize project tooling.
- Enforce code quality and git hook checks.
- Govern commit and release processes.
- Audit legacy repositories against required standards and output remediation actions.
Scope And Boundaries
- Required baseline:
- Node.js environment must be installed and available.
vite-plus (vp) is the required foundational CLI workflow.- Commit messages must follow Conventional Commits.
- Release automation must use
bumpp and changelogen.
- Recommended baseline:
- Use
pnpm as the package manager.
- Do not assume project-specific business logic, branching policy, or deployment platform details. Ask for clarification when missing.
- Keep this file as routing only; operational details belong in
references/.
Core Principles
- Executable standards: every rule maps to a concrete command or config.
- Minimal migration cost: prioritize low-risk, high-impact improvements first.
- Audit with evidence: compliance decisions require reproducible checks.
- No ambiguous requirements: unclear project constraints must be clarified.
Module Routing
Read the following modules based on user intent:
- Environment and bootstrap
- Code quality and hooks
- Commit and release workflow
- Legacy project audit and remediation
Minimal Output Contract
For any frontend lifecycle task, always provide:
- Selected module and why it applies.
- Completed checks/configuration items with evidence commands.
- Compliance gaps and impact level (blocker/high/medium/low).
- Actionable remediation plan with expected outcome.
- Final status (
compliant / partially-compliant / non-compliant) and next actions.
