#api-design
3 skillsWindsurf Rules for Full-Stack TypeScript AppsKeeps a TypeScript monorepo honest: one source of truth for types, API contracts that cannot drift, and forms validated by the same schema the server uses.Windsurf · CodingWindsurf.windsurfrulesWindsurf Rules for Full-Stack TypeScript AppsKeeps a TypeScript monorepo honest: one source of truth for types, API contracts that cannot drift, and forms validated by the same schema the server uses.Use in a full-stack TypeScript repo (Next.js, TanStack Start, or Express + React) where the client and server share a package and you want Windsurf to stop duplicating types and hand-rolling fetch calls.@libraryCodingGraphQL Schema Design RulesSchema-first GraphQL rules with a strict nullability policy, Relay-style connections, typed error unions, and naming conventions.Cursor · CodingCursor.cursorrulesGraphQL Schema Design RulesSchema-first GraphQL rules with a strict nullability policy, Relay-style connections, typed error unions, and naming conventions.Use when designing or extending a GraphQL schema to keep nullability, pagination, mutations, and error handling consistent across the graph.@libraryCodingAPI Design FirstWrite and review the endpoint contract — resources, errors, pagination, versioning — before any handler code exists.Claude Code · CodingClaude CodeSKILL.mdAPI Design FirstWrite and review the endpoint contract — resources, errors, pagination, versioning — before any handler code exists.Use when adding or changing API endpoints, so the contract is designed and reviewed before implementation locks in accidental decisions.@libraryCoding