backend-dev-guidelines▌
langfuse/langfuse · updated Apr 13, 2026
Use this skill for backend and API work across web/, worker/, and
- ›packages/shared/.
Backend Development Guidelines
Use this skill for backend and API work across web/, worker/, and
packages/shared/.
When to Apply
- Creating or modifying tRPC routers and procedures
- Creating or modifying public API endpoints
- Creating or modifying queue processors, producers, or queue-backed workflows
- Building or refactoring backend services and repositories
- Working on backend auth, middleware, validation, or observability
- Updating Prisma or ClickHouse access patterns
- Adding or fixing backend tests
How to Read This Skill
- Start with AGENTS.md when the task spans multiple backend areas or you need the end-to-end checklists.
- Read only the specific reference file that matches the work when the scope is narrower.
Reference Map
| Topic | Read this when | File |
|---|---|---|
| Architecture and package boundaries | You need the web/worker/shared split, request flow, or queue lifecycle | references/architecture-overview.md |
| Routing and controllers | You are writing tRPC procedures, public API routes, or queue entrypoints | references/routing-and-controllers.md |
| Middleware and auth | You are changing request auth, permissions, or middleware composition | references/middleware-guide.md |
| Services and repositories | You are placing business logic, repository code, or DI patterns | references/services-and-repositories.md |
| Database access | You are touching Prisma, ClickHouse, tenant filters, or query patterns | references/database-patterns.md |
| Configuration | You are adding env vars, startup config, or runtime toggles | references/configuration.md |
| Testing | You are adding or updating backend tests | references/testing-guide.md |
Full Compiled Guide
Read AGENTS.md for the complete backend guide with checklists, directory conventions, imports, architecture, and cross-cutting practices.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
backend-dev-guidelines is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Sep 9, 2024
Keeps context tight: backend-dev-guidelines is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Registry listing for backend-dev-guidelines matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Jul 7, 2024
backend-dev-guidelines reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend backend-dev-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· May 5, 2024
Useful defaults in backend-dev-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dhruvi Jain· Apr 4, 2024
backend-dev-guidelines has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Mar 3, 2024
Solid pick for teams standardizing on skills: backend-dev-guidelines is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Feb 2, 2024
We added backend-dev-guidelines from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Jan 1, 2024
backend-dev-guidelines fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.