Loading...
Loading...
Found 186 Skills
Expert full-stack development covering frontend frameworks, backend services, databases, APIs, and deployment for modern web applications.
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints. Covers contract-first design, resource modeling, error handling, pagination, and security.
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
REST API design with HTTP methods and status codes. Use for web APIs.
Expert software architecture covering system design, distributed systems, microservices, scalability patterns, and technical decision-making.
The functional options pattern for Go constructors and public APIs. Use when designing APIs with optional configuration, especially with 3+ parameters.
Agent skill for dev-backend-api - invoke with $agent-dev-backend-api
Define and manage backend coding standards in docs/rules/code/back/. Use when creating API design rules, database patterns, service architecture, authentication standards, or any backend-specific code rules.
Create or update system design documents. Supports initial design and incremental design modes. Use when users need technical architecture, API design, data models, design changes, or impact analysis. Triggers on keywords like "system design", "architecture", "technical design", "API design", "design change", "impact analysis", "design change", "impact analysis".
Insomnia API client for REST and GraphQL. Use for API testing.
Ability to develop both front-end and back-end systems, integrating user interfaces with server logic and databases.
Consult this skill when designing client-server systems or API architectures. Use when traditional web/mobile applications with centralized services, clear separation between client and server responsibilities needed. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.