backend-patterns
This skill provides a collection of backend architecture patterns and best practices for Node.js, Express, and Next.js applications. It includes code templates for API design, repository and service layers, database optimization, caching, error handling, authentication, and logging.
Is backend-patterns safe to install?
Safe to install: our audit of backend-patterns's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. This skill provides text-based architectural patterns and code examples. It does not execute commands or perform network requests.
How we audit skills: our security review methodology.
Who is this skill for?
Developers building scalable server-side applications using Node.js, Express, or Next.js.
What can you do with it?
- Designing REST or GraphQL API endpoints
- Implementing repository, service, or controller layers
- Optimizing database queries and preventing N+1 issues
- Adding caching layers with Redis
- Setting up background jobs or asynchronous processing
- Structuring centralized error handling and validation
- Building middleware for authentication and authorization
How good is this skill?
Quality score: 5/10. The skill provides clear, well-commented code patterns for common backend tasks. It is highly focused and follows standard architectural practices.
What does the skill file contain?
# Backend Development Patterns Backend architecture patterns and best practices for scalable server-side applications. ## When to Activate - Designing REST or GraphQL API endpoints - Implementing repository, service, or controller layers - Optimizing database queries (N+1, indexing, connection pooling) - Adding caching (Redis, in-memory, HTTP cache headers) - Setting up background jobs or async processing - Structuring error handling and validation for APIs - Building middleware (auth, logging, rate limiting) ## API Design Patterns ### RESTful API Structure ```typescript // PASS: Resourc...
Frequently asked questions
Does this skill provide a production-ready Redis implementation?
It provides a pattern for a CachedMarketRepository class and a Cache-Aside pattern example, but these are templates that require integration with your specific Redis client.
How does this skill handle database transactions?
It demonstrates using Supabase RPC functions to execute SQL transactions, ensuring atomicity for multiple insert operations.
Can I use the provided error handler for all API routes?
Yes, the provided errorHandler class supports custom ApiError types and Zod validation errors, which can be wrapped around your API route logic.
Related skills
lark-base
314.2KUsers who need to programmatically interact with Lark Bitable data, automate table management, or perform data analysis within the Lark ecosystem
The lark-base skill provides a command-line interface for managing Lark Bitable (Base) resources, including tables, records, fields, views, forms, dashboards, workflows, and role-based permissions.
supabase-postgres-best-practices
264.3KDevelopers and database administrators working with Postgres and Supabase
This skill provides a structured set of Postgres performance optimization rules and best practices maintained by Supabase. It guides developers in writing, reviewing, and optimizing SQL queries, schema designs, and database configurations.
simple
221.4KDevelopers and project managers who need a fast, lightweight decision-making process for feature design or component creation
A structured brainstorming framework for architectural and creative tasks that guides users from discovery to decision-making through a defined process flow.
supabase
153.8KDevelopers building applications with Supabase who require assistance with database schema design, security policy implementation, CLI operations, and integration troubleshooting
The Supabase skill provides guidance for developing with the Supabase platform, including database management, authentication, RLS policies, CLI usage, and MCP server integration. It emphasizes verifying implementation against current documentation, following security checklists, and using specific CLI commands for schema migrations.