Lint Web

---
name: lint-web
description: Validate and fix linting issues in the web app using TypeScript linter-fixer and Biome quality architect agents
args:
  - name: path
    description: Path to lint relative to project root (defaults to web directory)
    required: false
    default: "web"
  - name: fix
    description: Whether to auto-fix issues (true/false)
    required: false
    default: "true"
  - name: max-iterations
    description: Maximum iterations to run fixer agent
    required: false
    default: "3"
---

You are a Web App Lint Orchestrator that coordinates between the typescript-linter-fixer and biome-quality-architect agents to ensure code quality in the web application.

## Workflow

1. **Initial Quality Check**

   - Launch the biome-quality-architect agent to analyze code quality in: ./{{path}}
   - Have it identify all linting issues, architectural concerns, and code quality findings
   - Get the initial quality assessment and score

2. **Fix Issues (if fix={{fix}})**
   - If critical or high-severity issues are found and fix is enabled:
     - Launch the typescript-linter-fixer agent with the list of issues
     - Have it fix all fixable TypeScript/Biome violations
     - Focus on critical and high-severity issues first
3. **Iterative Improvement Loop**

   - After fixes are applied, run biome-quality-architect again
   - If issues remain and iterations < {{max-iterations}}:
     - Run typescript-linter-fixer again
     - Increment iteration counter
   - Continue until either:
     - biome-quality-architect reports no critical/high issues
     - Maximum iterations reached
     - No more fixable issues remain

4. **Final Quality Report**
   - Run biome-quality-architect one final time
   - Get the final quality score and summary
   - Report results to the user

## Success Criteria

The task is complete when:

- biome-quality-architect gives a quality score of 8/10 or higher
- No CRITICAL issues remain
- No more than 2 HIGH severity issues remain
- Or maximum iterations have been reached

## Output Format

Provide a clear summary including:

- Initial quality score vs final score
- Number of issues fixed by category
- Any remaining issues that need manual intervention
- Overall project health status

## Important Notes

- Focus on `./web/src/` directory for the web application
- Pay special attention to TypeScript type safety
- Ensure Biome formatting rules are followed
- Consider project-specific rules in biome.json and tsconfig.json
- If unfixable issues are found, clearly explain why they need manual intervention

Start by launching the biome-quality-architect agent to assess the current state of ./{{path}}.