Organize API layers using a 5-file TypeScript pattern with role-based access.
npx skills add https://github.com/BOM-98/FinTracker --skill api-organization
Please help me install this Agent Skill. Skill: api-organization Source: https://github.com/BOM-98/FinTracker/tree/main/.claude/skills/api-organization Command: npx skills add https://github.com/BOM-98/FinTracker --skill api-organization
Inconsistent API integration leads to fragmented code, type errors, and security vulnerabilities. This skill provides a rigid, 5-file standardized pattern for organizing all API interactions, ensuring type safety, role-based access control, and maintainability across the codebase.
endpoint-types.ts), URLs (endpoints.ts), generic clients (api-client.ts), admin clients (admin-api-client.ts), and protected wrappers (protected-endpoints.ts).Define new API types for a 'products' resource, including list, get, create, update, and delete operations, following the 5-file API organization pattern.
High-intent search queries and answers about installing and using this skill.
Standardize API organization using a 5-file system: endpoint-types.ts for type definitions, endpoints.ts for URL constants, api-client.ts for generic client logic, admin-api-client.ts for privileged access, and protected-endpoints.ts for role-based wrappers. This enforces end-to-end TypeScript typing and centralizes authentication.
Yes. Use the 5-file API organization pattern with Supabase Auth integration to automatically authenticate requests and enforce admin-only access through protected endpoint wrappers, separating regular user and admin client logic.
Apply the standardized 5-file API pattern: centralize all URLs in endpoints.ts, define shared types in endpoint-types.ts, and build reusable generic clients in api-client.ts. This creates a single source of truth and eliminates code duplication across the codebase.
Follow the rigid 5-file system structure for every new endpoint: define types, add URL constants, extend the generic client, update admin variants if needed, and wrap with role-based protection. This maintains consistency and prevents fragmented integration patterns.
For maintainability at scale, yes. A centralized 5-file architecture reduces runtime errors, enforces role-based access, ensures DRY code, and provides a single integration point for all API interactions—critical when managing multiple endpoints and user roles.
Rigid 5-file structures impose upfront overhead and may feel verbose for simple one-off endpoints. However, this trades short-term speed for long-term security, type safety, and maintainability—best for projects prioritizing consistency over quick iteration.
alunadevDesign REST and GraphQL APIs with production best practices for naming, errors, versioning, and documentation.
xiaoniuge36Generate type-safe API clients from OpenAPI specifications.
alijilani-devDevelop FastAPI web APIs with routing, Pydantic models, and testing.
ananddtyagiValidate API contracts against backend implementations and generate TypeScript clients.