brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
error-handlingUse when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Independent GitHub snapshot · Automated classification · Original documentation governs
Unhandled errors crash applications, create poor user experiences, and make debugging impossible without proper context.
Review error handling in this code, ensuring async operations use try-catch and errors are properly logged.
Add try-catch blocks to async operations and implement error boundaries for React components.
Explain JavaScript error handling best practices including try-catch, Promise rejection, and error boundaries.
Review scripts, client components, and browser execution paths related to Implement proper error handling. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/javascript/error-handling