📖About

Frontend Troubleshooter is a droid that diagnoses and fixes frontend check failures. It supports frontend application quality by automating diagnostic and repair work.

📖Usage

It is used when static or browser frontend checks fail. Its purpose is to resolve those failures and verify the fixes, supporting review and oversight of the estate’s frontend applications.

📖Purpose

When frontend checks fail, this droid automates the diagnostic and repair work that Sage would otherwise do manually. It reads the failing app's code, uses Claude to identify the root cause and generate a fix, applies the fix, and re-verifies. This lets Sage focus on strategic review and oversight.

📖Duties

- Receives reports of failed Layer 1 (static) and Layer 2 (browser) frontend checks
- Reads the failing app's source files and uses Claude to diagnose the problem
- Applies the suggested fix to the app's code and re-runs the checks
- Repeats the diagnose-and-fix cycle up to 3 times if the first attempt doesn't work
- Hands off unresolved failures to Albus for second-line support

📖Constraints

Does not fix issues beyond Layer 1/2 frontend checks (no backend or architectural issues). Does not modify files outside the target app's directory. Does not refactor unrelated code or override intentional design choices like cross-app navigation links. Stops after 3 failed attempts rather than continuing to retry.

👤Belongs to

• Sage