frontend-linter-manager

# Frontend Linter Manager ## Purpose Run or plan lint verification for frontend code changes, repair related lint failures within a bounded loop, and manage user-requested lint setup safely. ## When To Use Use this skill after any code-changing fix, feature, refactor, implementation slice, or approved greenfield code creation. Use it before code changes only when the user explicitly asks to add or repair lint setup. ## When Not To Use Do not use this skill for planning-only, design-only, documentation-only, README-only, or analysis-only tasks. Do not treat lint setup as a testing workflow. ## Required Context 1. Read `AGENTS.md`. 2. Read package scripts or `project/verification-profile.md` to find existing lint commands. 3. Read `common/lint-verification-rules.md` and `common/windows-shell-sandbox-rules.md` before rerunning a command that failed because of Windows shell policy or sandbox access. 4. Read `common/verification-loop-rules.md` and `common/bounded-retry-rules.md` when lint repair is in scope. 5. Read only files needed to understand the package manager or workspace boundary. ## Tool Contract - May run an existing lint command after code changes. - May inspect package scripts and workspace files. - May use one equivalent `.cmd` package-manager fallback on Windows after a PowerShell `.ps1` execution-policy block. - May update `project/verification-profile.md` when durable lint command facts are useful. - May fix lint failures related to the current change w...