Claude Code vs Windsurf

Add a GraphQL API to this repo in {{language}}. Define the schema first in schema.graphql: a Query type with paginated lists, a Mutation type for create and update, and one connection-style type for {{resource}} with cursor pagination. Wire resolvers to {{database}} with a dataloader per parent-child relation so nested queries do not N+1. Reject queries deeper than 6 levels and add a 30-second timeout per operation. Before writing resolvers, run the schema through the linter or validation step and fix any errors. Then write resolver tests covering pagination cursors, a nested query, and a mutation with invalid input. Run the tests. Finally start the server, POST an introspection query with curl, and paste the type names returned so I can confirm the schema is actually being served.

Build a TypeScript GraphQL API with Apollo Server backed by {{database}}. Schema: a {{resource}} type, a query for one {{resource}} by id, a cursor-paginated list query, and create, update, delete mutations returning a payload with a userErrors field instead of throwing. Put SDL in src/schema.graphql, resolvers under src/resolvers/, and a dataloader per relation to prevent N+1 lookups. Validate input at the resolver boundary and map {{database}} failures to typed errors. Ask before installing packages. Then start the server from the Windsurf terminal and run an introspection query plus one create-then-fetch round trip to prove the wiring. Finish by listing every file you created and the nullability decisions you made so I can review them.

Audit this codebase for missing error handling, then fix it in order of blast radius. First produce the audit: grep for empty catch blocks, unhandled promise rejections, fetch or database calls without a failure path, and absent process-level handlers. Show me the list ranked by user impact before changing code. Then apply fixes: every external call gets a typed error or result wrapper, user-facing failures get a message that states what to retry, internal failures get structured logs with enough context to reproduce, and nothing swallows an error silently. Do not wrap everything in one giant try block. For each fix, add a test that forces the failure, network refused, bad JSON, constraint violation, and asserts the handled behavior. Run the suite and paste the failing-then-passing output for at least the three highest-impact fixes.

Audit this repo for missing error handling and fix it in layers. Start with a Cascade search for bare awaits, empty catch blocks, and promise chains without rejection paths; group findings by file and show me before editing. Then add a shared asyncHandler around route handlers, one error middleware mapping known error types to status codes and hiding stack traces outside development, and a timeout plus typed failure result on every external call: network, filesystem, {{database}}. On the UI side, wrap the route tree in an error boundary with a retry action. Every fix ships with a test that forces the failure: reject the promise, sever the connection, throw inside a child component. Run the suite from the Windsurf terminal and report each forced-failure test you added.