correctness-and-error-handling

Correctness & Error Handling Fix

Find and fix correctness issues and missing error handling in $ARGUMENTS (or the whole app if no argument is given). Work through every step below. Each step searches for problems and then fixes them in place. Only report issues that cannot be auto-fixed.

Step 1 — Map data flows and fix known defects

Read these files before checking anything:

• src/main.tsx / src/App.tsx — top-level error boundaries and auth flow
• All files matching **/hooks/*.ts, **/contexts/*.tsx — shared async state
• All files matching **/api/*.ts, **/services/*.ts — CDF SDK call sites

For each async data source, note:

• What happens when the request fails (network error, CDF 403, timeout)?
• What does the UI show while loading?
• What does the UI show if the result is empty?

Find and fix known defects in critical paths

# Find TODO/FIXME/HACK in critical code paths (not test files)
grep -rn --include="*.ts" --include="*.tsx" -E "(TODO|FIXME|HACK|XXX):" src/ | grep -v

For each match in a critical path (data fetching, rendering, auth, navigation):

1. Read the surrounding code to understand the incomplete/broken behavior.
2. Fix the underlying issue — implement the missing logic, correct the broken behavior, or add proper error handling.
3. If the fix requires significant architectural changes beyond this skill's scope, replace the TODO with a safe failure mode: graceful error handling, a sensible fallback value, or an explicit user-facing message explaining degraded functionality.
4. Remove the TODO/FIXME/HACK comment after fixing. The code should speak for itself.

Do not leave TODOs in critical paths. Every one must be resolved or converted to a safe fallback.

Step 2 — Add top-level error boundary

Every Flows app must have at least one React Error Boundary wrapping the main content so that an unexpected render-time exception shows a user-friendly message instead of a blank screen.

If no error boundary exists, create the ErrorFallback component and add the ErrorBoundary wrapper to App.tsx. Install react-error-boundary if not present:

Then add to App.tsx:

Write the updated App.tsx with the ErrorBoundary in place. Do not just suggest it — make the edit.

Step 3 — Wrap unhandled async functions in try/catch

Search for every async function and Promise chain that does not have error handling:

Fix each one:

• For bare async functions that lack try/catch: wrap the function body in try/catch. Log the error with context and re-throw so callers/query layers can handle it:

• For .then() without .catch(): add .catch() to the chain:

• For TanStack Query consumers (useQuery/useMutation) missing isError handling: add the error check and error UI to the component:

Read each file, make the edit, and write it back.

Step 4 — Add missing loading, error, and empty states to components

For each component that fetches data, it must have three distinct UI states:

Search for components that render data without checking loading state:

For each hit, read the component and add the missing states directly:

• Missing loading state — add before the data render:

• Missing error state — add after the loading check:

• Missing empty state — add after the error check, before the .map():

Insert these checks in the correct order (loading, then error, then empty) above the existing data render. Write each fixed file.

Step 5 — Add type narrowing for external data

External data (CDF responses, URL params, localStorage, JSON.parse) must be validated before use. TypeScript types alone are not runtime guarantees.

Fix each one:

• JSON.parse(x) as T — replace with Zod safeParse:

• searchParams.get("id") without null check — add nullish fallback:

• localStorage.getItem(key) used directly — add type guard and fallback:

Do not cast external data with as MyType — that bypasses runtime safety. Read, fix, and write each file.

Step 6 — Fix null, undefined, and unsafe array access

Read every component that accesses properties of data returned from CDF or passed via props.

Fix each unsafe pattern found:

• Unsafe nested property access — add optional chaining and nullish coalescing:

• Unguarded .map() on possibly-undefined array — add nullish fallback:

• Unsafe array index access — use .at() with optional chaining:

Read each file with a match, apply the fix, and write it back.

Step 7 — Add useEffect cleanup functions

Every useEffect that sets up a subscription, timer, event listener, or async operation that can outlive the component must return a cleanup function.

For each useEffect, check whether cleanup is needed and add the cleanup function if missing:

Reference pattern for async effects:

Read each effect, add the missing cleanup, and write the file.

Step 8 — Add edge case guards

For each feature, check and add guards for:

• Empty data: If zero-item lists are not handled, add an empty state check before rendering.
• Single item: If list rendering has off-by-one bugs with a single entry, fix the logic.
• Maximum data / pagination: If CDF returns the full limit and there are more pages, ensure pagination is communicated to the user. Add a "Load more" or pagination indicator if missing.
• Concurrent requests / stale results: If the user can trigger a new request before the previous completes, add stale request cancellation (AbortController or a request ID check).
• Network offline: If the app silently fails when offline, add a meaningful error message.

For Atlas tool execute functions, add argument validation at the top of every execute function:

Search for execute functions, read each one, add the validation, and write the file.

Step 9 — Report remaining findings

Produce a structured report covering:

1. What was fixed in each step — summarize the changes made (files edited, patterns fixed).
2. Remaining issues — only list issues that could not be auto-fixed (e.g., require architectural changes, need product decisions, or are outside the scope of this skill).

If no issues are found in a step, state "No issues found" for that step. Do not skip steps silently.

Done

Summarize what was fixed by severity. Flag any remaining HIGH issues that could cause data loss, crashes in production, or misleading UI states, and list them first for immediate attention.