#api

Create developer-friendly API documentation. Structure: 1. Overview with quick start guide and authentication. 2. Endpoint reference with request/response examples. 3. Interactive API explorer (Swagger/Postman style). 4. Code samples in multiple languages (Python, JavaScript, cURL). 5. Error codes and troubleshooting guide. 6. Rate limiting and best practices. 7. Webhook documentation with payload examples. 8. Changelog and versioning information. Use clear, concise language with real-world use cases.

Develop a 'Trending Repositories' UI. Layout: 1. Filter dropdowns for 'Language' and 'Date Range'. 2. List items showing repo name, description, stars (count + icon), and contributors. 3. Color-coded language dots (e.g., TS: blue, JS: yellow). 4. Skeleton loading state for initial fetch. 5. Responsive design: switch from list to cards on small screens.

Design scalable GraphQL schemas. Patterns: 1. Types for domain models. 2. Queries for reads, mutations for writes. 3. Input types for complex arguments. 4. Interfaces and unions for polymorphism. 5. Connection pattern for pagination. 6. DataLoader for N+1 prevention. 7. Directive for custom logic. 8. Federation for microservices. Use schema-first approach. Implement authorization at field level.

Build type-safe APIs with tRPC. Architecture: 1. Define routers with input/output schemas. 2. Zod for runtime validation. 3. Automatic TypeScript inference. 4. React Query integration for client. 5. Middleware for auth and logging. 6. Context for user sessions. 7. Subscriptions with WebSockets. 8. Error handling with TRPCError. No code generation needed. Use with Next.js or standalone Express server.