[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI may ask user whether to skip.
Prerequisites: MUST READ before executing:
.claude/skills/shared/understand-code-first-protocol.md.claude/skills/shared/evidence-based-reasoning-protocol.md
Quick Summary
Goal: Run linters (.NET analyzers and/or ESLint/Prettier) and report or auto-fix code quality issues.
Workflow:
- Parse — Determine scope from arguments: backend, frontend, or both; fix mode or report-only
- Execute — Run
dotnet buildfor .NET analyzers ornx lint/prettierfor Angular - Report — Group issues by severity (error/warning/info) with file paths and line numbers
Key Rules:
- No argument = run both backend + frontend in report-only mode
fixargument = apply safe auto-fixes, report remaining manual items- Always show file paths and line numbers in output
Run linting: $ARGUMENTS
Instructions
Parse arguments:
backendorbe→ Run .NET analyzersfrontendorfe→ Run ESLint/Prettierfix→ Auto-fix issues where possible- No argument → Run both, report only
For Backend (.NET):
dotnet build EasyPlatform.sln /p:TreatWarningsAsErrors=false- Check for analyzer warnings (CA*, IDE*, etc.)
- Report code style violations
For Frontend (Angular/Nx):
cd src/PlatformExampleAppWeb nx lint playground-text-snippet nx lint platform-coreWith auto-fix:
nx lint playground-text-snippet --fix npx prettier --write "apps/**/*.{ts,html,scss}" "libs/**/*.{ts,html,scss}"Report format:
- Group issues by severity (error, warning, info)
- Show file paths and line numbers
- Suggest fixes for common issues
Auto-fix behavior:
- If
fixargument provided, apply safe auto-fixes - Report what was fixed vs what needs manual attention
- If
IMPORTANT Task Planning Notes (MUST FOLLOW)
- Always plan and break work into many small todo tasks
- Always add a final review todo task to verify work quality and identify fixes/enhancements