web-server-architecture
Maintains clean architecture for web server layers.
Install
mkdir -p .claude/skills/web-server-architecture && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16542" && unzip -o skill.zip -d .claude/skills/web-server-architecture && rm skill.zipInstalls to .claude/skills/web-server-architecture
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
`web/src/server/**`의 router, service, 공통 계층을 건드릴 때 사용하는 스킬이다. tRPC router와 service 책임 분리, 도메인 구조, Prisma 사용 경계를 맞춘다.Key capabilities
- →Create new tRPC routers
- →Add or split service logic
- →Refactor router business logic
- →Organize Prisma query locations
- →Maintain domain-driven structure
How it works
The skill ensures that changes to the server architecture adhere to established rules for router, service, and common utility responsibilities, preventing their mixing.
Inputs & outputs
When to use web-server-architecture
- →Creating tRPC routers
- →Adding service layer logic
- →Refactoring Prisma query boundaries
About web-server-architecture
Ensures adherence to backend architectural rules, specifically managing separation between tRPC routers, service layers, and Prisma queries.
`web/src/server/**`의 router, service, 공통 계층을 건드릴 때 사용하는 스킬이다. tRPC router와 service 책임 분리, 도메인 구조, Prisma 사용 경계를 맞춘다.
When not to use it
- →When the change is not related to `web/src/server/**`
- →When the change does not involve router, service, or common layers
- →When the change does not impact tRPC router and service responsibility separation
Limitations
- →Limited to `web/src/server/**` directory
- →Focuses on router, service, and common utility layers
- →Requires adherence to tRPC router and service responsibility separation
How it compares
This skill enforces architectural consistency for web server components, preventing common issues like bloated routers or mixed responsibilities that can arise from unguided development.
Compared to similar skills
web-server-architecture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| web-server-architecture (this skill) | 0 | 3mo | No flags | Intermediate |
| prisma-connection-pool-exhaustion | 1 | 7mo | Review | Intermediate |
| hiddenroom-supabase | 0 | 1mo | No flags | Intermediate |
| backend-patterns | 0 | 1mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by develsvai
View all by develsvai →You might also like
prisma-connection-pool-exhaustion
blader
Fix Prisma "Too many connections" and connection pool exhaustion errors in serverless environments (Vercel, AWS Lambda, Netlify). Use when: (1) Error "P2024: Timed out fetching a new connection from the pool", (2) PostgreSQL "too many connections for role", (3) Database works locally but fails in production serverless, (4) Intermittent database timeouts under load.
hiddenroom-supabase
cuvo1903-ctrl
Hidden Room Supabase backend skill for migrations, generated database types, Edge Functions, RLS policies, auth/profile sync, storage buckets, Stripe integration, cloud_jobs, and database documentation. Use when editing supabase/migrations, supabase/functions, database.types.ts, or Supabase-backed f
backend-patterns
chenqin231
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
event-store-design
wshobson
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
springboot-patterns
affaan-m
Spring Boot 架构模式、REST API 设计、分层服务、数据访问、缓存、异步处理和日志记录。适用于 Java Spring Boot 后端工作。
dotnet-architect
sickn33
Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.