backend dev guidelines

Data Community

Skill notes

Purpose

Establish consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js/Express/TypeScript patterns.

When to Use This Skill

Automatically activates when working on: Creating or modifying routes, endpoints, APIs Building controllers, services, repositories Implementing middleware (auth, validation, error handling) Database operations with Prisma

New Backend Feature Checklist

[ ] Route: Clean definition, delegate to controller [ ] Controller: Extend BaseController [ ] Service: Business logic with DI [ ] Repository: Database access (if complex) [ ] Validation: Zod schema

New Microservice Checklist

[ ] Directory structure (see architecture-overview.md) [ ] instrument.ts for Sentry [ ] unifiedConfig setup [ ] BaseController class [ ] Middleware stack

Layered Architecture

Key Principle: Each layer has ONE responsibility. See architecture-overview.md for complete details.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview backend-dev-guidelines.preview
# [complete-examples.md](complete-examples.md)

Full examples, refactoring guide ---

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.