Agent skill

Backend Dev Guidelines

Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.

Custom licenceAuto-check passedBackend & APIs

Install Backend Dev Guidelines

skills CLI

$ npx skills add litefuse/litefuse --skill backend-dev-guidelines -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install litefuse/litefuse backend-dev-guidelines --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/litefuse/litefuse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/backend-dev-guidelines .claude/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "backend-dev-guidelines" agent skill from https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines into .claude/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add litefuse/litefuse --skill backend-dev-guidelines -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install litefuse/litefuse backend-dev-guidelines --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/litefuse/litefuse.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/backend-dev-guidelines .agents/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "backend-dev-guidelines" agent skill from https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines into .agents/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add litefuse/litefuse --skill backend-dev-guidelines -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install litefuse/litefuse backend-dev-guidelines --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/litefuse/litefuse.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/backend-dev-guidelines .cursor/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "backend-dev-guidelines" agent skill from https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines into .cursor/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/litefuse/litefuse.git --path .claude/skills/backend-dev-guidelines

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add litefuse/litefuse --skill backend-dev-guidelines -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install litefuse/litefuse backend-dev-guidelines --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/litefuse/litefuse.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/backend-dev-guidelines .gemini/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "backend-dev-guidelines" agent skill from https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines into .gemini/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install litefuse/litefuse backend-dev-guidelines

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add litefuse/litefuse --skill backend-dev-guidelines -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/litefuse/litefuse.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/backend-dev-guidelines .github/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "backend-dev-guidelines" agent skill from https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines into .github/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add litefuse/litefuse --skill backend-dev-guidelines -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install litefuse/litefuse backend-dev-guidelines --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/litefuse/litefuse.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/backend-dev-guidelines .opencode/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "backend-dev-guidelines" agent skill from https://github.com/litefuse/litefuse/tree/main/.claude/skills/backend-dev-guidelines into .opencode/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: backend-dev-guidelines
GitHub stars: 100
Used in: 1 other repo
Token cost: ~5.8k tokens
SKILL.md length: 1,066 words
Files: 8
Skills in repo: 2
Repo updated: Sep 23, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.

Works in 8 steps: tRPC Procedures Delegate to Services → Access Config via env.mjs, NEVER… → Validate ALL Input with Zod v4 → …
Creating tRPC routers
SKILL.md covers Purpose, When to Use This Skill, Quick Start and Architecture Overview, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Backend Dev Guidelines is an agent skill from litefuse/litefuse. Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services)…

Its SKILL.md is about 5.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `resources/architecture-overview.md`, `resources/configuration.md` and `resources/database-patterns.md`).

It sits in Backend & APIs, covering Observability, gRPC and Protobuf and Multi-tenancy. It works with tRPC, ClickHouse, Next.js and Zod. The repository describes itself as: Litefuse - Agent Observability and Evaluation Platform.

When your agent uses it

Creating tRPC routers
Public API endpoints
BullMQ queue processors
Working with tRPC procedures

Example prompts

“/backend-dev-guidelines”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

tRPC Procedures Delegate to Services
Access Config via env.mjs, NEVER process.env
Validate ALL Input with Zod v4
Services Use Prisma Directly for Simple CRUD or Repositories for Complex Queries
Observability: OpenTelemetry + DataDog (Not Sentry for Backend)
Comprehensive Testing Required
Always Filter by projectId for Tenant Isolation
Keep Fern API Definitions in Sync with TypeScript Types

What it can do on your machine

Read from SKILL.md and the folder at commit 70a2001. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Backend Dev Guidelines loads about 5.8k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 1,066 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~187
When it runs · the whole SKILL.md, loaded when a task matches: ~5.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,066 words (~5,764 tokens).

“Establish consistency and best practices across Litefuse's backend packages (web, worker, packages/shared) using Next.js 14, tRPC, BullMQ, and TypeScript patterns.”

— opening of SKILL.md by litefuse, Custom licence

name: backend-dev-guidelines

Outline of SKILL.md

Backend Development Guidelines
Purpose
When to Use This Skill
Quick Start
UI: New tRPC Feature Checklist (Web)
SDKs: New Public API Endpoint Checklist (Web)
New Queue Processor Checklist (Worker)
Architecture Overview
Layered Architecture
Directory Structure
Web Package (/web/)
Worker Package (/worker/)
Shared Package (/packages/shared/)
Core Principles
1. tRPC Procedures Delegate to Services
2. Access Config via env.mjs, NEVER process.env
3. Validate ALL Input with Zod v4
4. Services Use Prisma Directly for Simple CRUD or Repositories for Complex Queries
6. Observability: OpenTelemetry + DataDog (Not Sentry for Backend)
7. Comprehensive Testing Required
8. Always Filter by projectId for Tenant Isolation
9. Keep Fern API Definitions in Sync with TypeScript Types
Common Imports
Quick Reference
HTTP Status Codes
Example Features to Reference
Anti-Patterns to Avoid
Navigation Guide
Resource Files
architecture-overview.md

Read the full SKILL.md on GitHub

Files

SKILL.md and 7 other files in .claude/skills/backend-dev-guidelines of litefuse/litefuse.

SKILL.md
resources/architecture-overview.md
resources/configuration.md
resources/database-patterns.md
resources/middleware-guide.md
resources/routing-and-controllers.md
resources/services-and-repositories.md
resources/testing-guide.md

Open the folder on GitHubat commit 70a2001

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in litefuse/litefuse, which our catalogue first saw on October 7, 2026.

Microck/ordinary-claude-skillsskills_all/backend-dev-guidelines skills_categorized/backend/backend-dev-guidelines+1 more

Compare with similar skills

Backend Dev Guidelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Backend Dev Guidelines compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Backend Dev Guidelines this skilllitefuse/litefuse	100	1 repos	~5.8k	Automated safety check: Pass	Custom licence	14 days ago
Backend Dev Guidelineslangfuse/langfuse	35k	—	~1.9k	Automated safety check: Pass	Custom licence	today
Trpcpproenca/dot-skills	214	—	~2.8k	Automated safety check: Pass	MIT	1 mo ago
Profiling Slow API EndpointsPostHog/posthog-foss	721	—	~1k	Automated safety check: Pass	MIT	today
Nestjs Trpctrycompai/crm	11k	—	~2.8k	Automated safety check: Pass	MIT	26 days ago
Nestjs Drizzle Crud Generatorgiuseppe-trisciuoglio/developer-kit	355	—	~1.3k	Automated safety check: Notes	MIT	27 days ago

Similar skills

Backend Dev Guidelines
langfuse/langfuse
Build or review Langfuse backend code. An agent skill from langfuse/langfuse.
35k GitHub stars~1.9k tokensUpdated today
Backend & APIsAuto-check passed
Trpc
pproenca/dot-skills
Corrects the wrong defaults a model has for tRPC v11 (verified against 11.18.0).
214 GitHub stars~2.8k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Profiling Slow API Endpoints
PostHog/posthog-foss
Official
Profiles slow PostHog API endpoints when the main cost is in Postgres or Python.
721 GitHub stars~1k tokensUpdated today
DatabasesAuto-check passed
Nestjs Trpc
trycompai/crm
Build end-to-end type-safe tRPC APIs inside NestJS using the nestjs-trpc adapter — @Router/@Query/@Mutation/@Subscription decorators, TRPCModule.forRoot, injectable middlewares and context, Zod…
11k GitHub stars~2.8k tokensUpdated 26 days ago
Backend & APIsAuto-check passed
Nestjs Drizzle Crud Generator
giuseppe-trisciuoglio/developer-kit
Generates complete CRUD modules for NestJS applications with Drizzle ORM.
355 GitHub stars~1.3k tokensUpdated 27 days ago
DatabasesAuto-check: notes
Multi Cluster API Data Mismatch
divinevideo/divine-mobile
Debug "API returns data that doesn't exist in database" when multiple Kubernetes clusters exist (production, staging, POC).
265 GitHub stars~1.3k tokensUpdated today
DevOps & CloudAuto-check passed

Questions about Backend Dev Guidelines

What does Backend Dev Guidelines do?

Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo. Backend Dev Guidelines is an agent skill from litefuse/litefuse.js 14/tRPC/Express/TypeScript monorepo.

When should I use Backend Dev Guidelines?

Backend Dev Guidelines fits situations like: creating tRPC routers; public API endpoints; bullMQ queue processors; working with tRPC procedures.

How do I install Backend Dev Guidelines in Claude Code?

Run `npx skills add litefuse/litefuse --skill backend-dev-guidelines -a claude-code`. Or copy the skill folder (.claude/skills/backend-dev-guidelines in litefuse/litefuse) into .claude/skills/backend-dev-guidelines in your project. Claude Code loads it when a task matches its description.

How do I install Backend Dev Guidelines in Codex?

Run `npx skills add litefuse/litefuse --skill backend-dev-guidelines -a codex`. Or copy the skill folder (.claude/skills/backend-dev-guidelines in litefuse/litefuse) into .agents/skills/backend-dev-guidelines in your project. Codex loads it when a task matches its description.

Can I use Backend Dev Guidelines in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add litefuse/litefuse --skill backend-dev-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backend-dev-guidelines, .gemini/skills/backend-dev-guidelines, .github/skills/backend-dev-guidelines and .opencode/skills/backend-dev-guidelines in your project.

What does Backend Dev Guidelines need to run?

SKILL.md names no scripts, command-line tools or credentials: Backend Dev Guidelines is instructions for the agent only.

Does Backend Dev Guidelines access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Backend Dev Guidelines safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Backend Dev Guidelines use?

Backend Dev Guidelines has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Backend Dev Guidelines use?

About 5.8k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Backend Dev Guidelines?

Skills that share tags, products or a category with Backend Dev Guidelines: Backend Dev Guidelines (langfuse/langfuse, 35k stars), Trpc (pproenca/dot-skills, 214 stars), Profiling Slow API Endpoints (PostHog/posthog-foss, 721 stars) and Nestjs Trpc (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Backend Dev Guidelines?

litefuse (a GitHub user) maintains it in litefuse/litefuse, which has 100 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 23, 2026.

Source: litefuse/litefuse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Backend Dev Guidelines

Install Backend Dev Guidelines

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Used in 1 other repository

Compare with similar skills

Similar skills