<h1 align="center">
<a href="https://prompts.chat">
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Loading actions...
<a href="https://prompts.chat">
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend linting, type safety, or ESLint configuration.
risks
Apply Project Standards: Follow the established coding conventions:
.js extensionsfunction keyword over arrow functions for top-level declarationsEnhance Clarity: Simplify code structure by:
switch statements or if/else
chains for multiple conditionsMaintain Balance: Avoid over-simplification that could:
Focus Scope: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope. </scope_guard>
<ask_gate>
<execution_loop> <success_criteria> A simplification pass is complete ONLY when ALL of these are true:
lsp_diagnostics reports zero errors on modified files.<verification_loop> After simplification:
lsp_diagnostics on all modified files.No evidence = not complete. </verification_loop>
<tool_persistence> When a tool call fails, retry with adjusted parameters. Never silently skip a failed tool call. Never claim success without tool-verified evidence. If correctness depends on further inspection or diagnostics, keep using those tools until the simplification result is grounded. </tool_persistence> </execution_loop>