Architectural patterns, API design, and database optimization for Node.js, Express, and Next.js backends.
Works with
Covers repository, service, and middleware layers for clean separation of concerns; includes REST API structure with resource-based URLs and query parameters
Database patterns include N+1 prevention, query optimization, transactions, and caching strategies (Redis, cache-aside)
Error handling with centralized handlers, retry logic with exponential backoff, and structured logging f
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbackend-patternsExecute the skills CLI command in your project's root directory to begin installation:
Fetches backend-patterns from affaan-m/everything-claude-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate backend-patterns. Access via /backend-patterns in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
142.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
142.9K
stars
Backend architecture patterns and best practices for scalable server-side applications.
// PASS: Resource-based URLs
GET /api/markets # List resources
GET /api/markets/:id # Get single resource
POST /api/markets # Create resource
PUT /api/markets/:id # Replace resource
PATCH /api/markets/:id # Update resource
DELETE /api/markets/:id # Delete resource
// PASS: Query parameters for filtering, sorting, pagination
GET /api/markets?status=active&sort=volume&limit=20&offset=0
// Abstract data access logic
interface MarketRepository {
findAll(filters?: MarketFilters): Promise<Market[]>
findById(id: string): Promise<Market | null>
create(data: CreateMarketDto): Promise<Market>
update(id: string, data: UpdateMarketDto): Promise<Market>
delete(id: string): Promise<void>
}
class SupabaseMarketRepository implements MarketRepository {
async findAll(filters?: MarketFilters): Promise<Market[]> {
let query = supabase.from('markets').select('*')
if (filters?.status) {
query = query.eq('status', filters.status)
}
if (filters?.limit) {
query = query.limit(filters.limit)
}
const { data, error } = await query
if (error) throw new Error(error.message)
return data
}
// Other methods...
}
// Business logic separated from data access
class MarketService {
constructor(private marketRepo: MarketRepository) {}
async searchMarkets(query: string, limit: number = 10): Promise<Market[]> {
// Business logic
const embedding = await generateEmbedding(query)
const results = await this.vectorSearch(embedding, limit)
// Fetch full data
const markets = await this.marketRepo.findByIds(results.map(r => r.id))
// Sort by similarity
return markets.sort((a, b) => {
const scoreA = results.find(r => r.id === a.id)?.score || 0
const scoreB = results.find(r => r.id === b.id)?.score || 0
return scoreA - scoreB
})
}
private async vectorSearch(embedding: number[], limit: number) {
// Vector search implementation
}
}
// Request/response processing pipeline
export function withAuth(handler: NextApiHandler): NextApiHandler {
return async (req, res) => {
const token = req.headers.authorization?.replace('Bearer ', '')
if (!token) {
return res.status(401).json({ error: 'Unauthorized' })
}
try {
const user = await verifyToken(token)
req.user = user
return handler(req, res)
} catch (error) {
return res.status(401).json({ error: 'Invalid token' })
}
}
}
// Usage
export default withAuth(async (req, res) => {
// Handler has access to req.user
})
// PASS: GOOD: Select only needed columns
const { data } = await supabase
.from('markets')
.select('id, name, status, volume')
.eq('status', 'active')
.order('volume', { ascending: false })
.limit(10)
// FAIL: BAD: Select everything
const { data } = await supabase
.from('markets')
.select('*')
// FAIL: BAD: N+1 query problem
const markets = Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
java-coding-standards
18affaan-m/everything-claude-code
Backendsame repoprompt-optimizer
23affaan-m/everything-claude-code
Productivitysame repovideo-editing
19affaan-m/everything-claude-code
Videosame repoliquid-glass-design
10affaan-m/everything-claude-code
Frontendsame repobackend-development
22mrgoonie/claudekit-skills
Backendtag: backendbackend-architect
21sickn33/antigravity-awesome-skills
Backendtag: backendReviews
4.6★★★★★38 reviews- KKwame Bansal★★★★★Dec 24, 2024
backend-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.
- YYuki Abebe★★★★★Dec 20, 2024
backend-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.
- PPratham Ware★★★★★Dec 12, 2024
Registry listing for backend-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
- ZZara Park★★★★★Nov 27, 2024
Registry listing for backend-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
- LLayla Bhatia★★★★★Nov 27, 2024
Keeps context tight: backend-patterns is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ZZara Robinson★★★★★Nov 15, 2024
backend-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.
- KKabir Mensah★★★★★Nov 11, 2024
backend-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.
- KKwame Agarwal★★★★★Oct 18, 2024
Keeps context tight: backend-patterns is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNoor Garcia★★★★★Oct 18, 2024
Registry listing for backend-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
- ZZara Choi★★★★★Oct 6, 2024
Useful defaults in backend-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 38
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.