Skills backend-dev-guidelines

📦

backend-dev-guidelines

Name: backend-dev-guidelines
Author: sickn33

Content revision r2 High Risk 🔑 Env variables📁 Filesystem access🌐 Network access⚙️ External commands

Build Reliable Node.js Backends

Backend changes often become inconsistent across routing, business logic, data access, validation, and monitoring. This skill supplies structured Node.js patterns for reliable implementation and review.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "backend-dev-guidelines" from https://skillstore.io/skills/sickn33-backend-dev-guidelines.md and its manifest at https://skillstore.io/api/skills/sickn33-backend-dev-guidelines/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-backend-dev-guidelines.md Signed manifest GET /api/skills/sickn33-backend-dev-guidelines/manifest Signed lockfile GET /api/skills/sickn33-backend-dev-guidelines/lockfile

Test it

Using "backend-dev-guidelines". Plan a user creation endpoint with email validation.

Expected outcome:

Route delegates the request to UserController.
Controller validates input and calls UserService.
Service enforces uniqueness and invokes UserRepository.
Tests cover success, invalid email, duplicate email, and persistence failure.

Using "backend-dev-guidelines". Review a controller that queries Prisma directly.

Expected outcome:

Finding: the controller bypasses service and repository boundaries.
Risk: business rules and persistence become difficult to test independently.
Recommendation: move decisions into a service and queries into a repository.

Using "backend-dev-guidelines". Design monitoring for a payment workflow.

Expected outcome:

Capture unexpected failures with operation and transaction identifiers.
Redact payment details and credentials before telemetry export.
Measure latency and failure rates without recording sensitive request bodies.

Security Audit

High Risk

v5 • 8/14/2026 Open versioned report

All 219 static alerts are false positives caused by Markdown examples, relative imports, placeholders, and TypeScript syntax. Semantic review found overbroad Sentry collection, plaintext development secrets, and direct client exposure of internal error messages.

Files scanned

5,342

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (3)

High

resources/sentry-and-monitoring.md:49-85

Overbroad Sentry Data Collection

The recommended setup captures local variables, request bodies, headers, query strings, IP addresses, and user identifiers. Its scrubber removes only two headers and masks one email field.

The enabled integrations and included fields are explicit. Passwords, tokens, and personal data outside the narrow scrubber could reach Sentry.

Medium

resources/configuration.md:160-234

Plaintext Secret Configuration Guidance

The guide places database, JWT, internal API, and client secrets in config.ini and gives that file highest precedence. Gitignore guidance reduces accidental commits but not plaintext exposure.

The configuration examples and precedence rules are explicit. Production uses environment variables, but the recommended development file still stores secrets unencrypted.

Medium

resources/sentry-and-monitoring.md:120-134

Internal Error Messages Returned to Clients

The BaseController example returns error.message directly in HTTP responses. Unexpected exceptions can reveal database details, identifiers, or internal implementation information.

The response assignment is direct and lacks an allowlist of public error types. The exposure depends on which exceptions reach this handler.

Risk Factors

🔑 Env variables (50)

📁 Filesystem access (42)

🌐 Network access (4)

resources/configuration.md:182 resources/configuration.md:186 resources/testing-guide.md:191 resources/testing-guide.md:194

⚙️ External commands (42)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-backend-dev-guidelines/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-backend-dev-guidelines/security.svg)](https://skillstore.io/skills/sickn33-backend-dev-guidelines?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-backend-dev-guidelines?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-backend-dev-guidelines/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-backend-dev-guidelines.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). backend-dev-guidelines security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-backend-dev-guidelines/audits/5

BibTeX citation

@techreport{sickn33-sickn33-backend-dev-guidelines-2026,
  author = {sickn33},
  title = {backend-dev-guidelines security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-backend-dev-guidelines/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "backend-dev-guidelines security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-08-14"
url: "https://skillstore.io/skills/sickn33-backend-dev-guidelines/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-backend-dev-guidelines:audit:5"
    description: "Skillstore immutable audit report identifier"

Compare variants

5 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

DojoCodingLabs Recommended

dojocodinglabs-backend-dev-guidelines

Skillstore Score 70

Evidence Confidence High

Skillstore usage 9

Updated

2026-08-21

Dimon94

dimon94-backend-dev-guidelines

Skillstore Score 70

Evidence Confidence High

Skillstore usage 6

Updated

2026-08-21

diet103

diet103-backend-dev-guidelines

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 10

Updated

2026-08-21

sickn33 Current

sickn33-backend-dev-guidelines

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 7

Updated

2026-08-21

BrianDai22

briandai22-backend-dev-guidelines

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 7

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Design a New API Feature

Plan routes, validation, service logic, repository access, error handling, and tests before implementation.

Review Backend Architecture

Identify layer violations, missing validation, direct database access, weak error boundaries, and testing gaps.

Standardize a Service Team

Establish shared conventions for configuration, dependency injection, monitoring, naming, repositories, and pull request review.

Try These Prompts

Plan a Backend Endpoint

Plan a [method] [path] endpoint for [goal]. Include layers, validation, errors, persistence, and tests.

Review a Backend Change

Review [files or diff] against these backend guidelines. List behavioral risks, architecture violations, security concerns, and missing tests.

Design a Transactional Workflow

Design [workflow] using Express, Prisma, and Zod. Define transaction boundaries, idempotency, error mapping, observability, and integration tests.

Refactor a Legacy Feature

Refactor [feature] into routes, controllers, services, and repositories. Preserve behavior, add Zod validation, transaction boundaries, Sentry context, and focused tests.

Best Practices

Describe the existing architecture, dependencies, and acceptance criteria.
Provide relevant routes, schemas, models, errors, and test conventions.
Validate generated changes with project tests, security review, and runtime checks.

Avoid

Do not request a complete rewrite without behavioral constraints.
Do not place business logic, validation, and database calls directly in routes.
Do not adopt telemetry or configuration examples without reviewing secret and privacy handling.

Frequently Asked Questions

Which backend stack does this skill target?

It targets Node.js services using Express, TypeScript, Prisma, Zod, and Sentry.

Can it generate complete backend features?

It can guide implementation across layers, but project models, dependencies, and requirements must be provided.

Does it replace security review?

No. Authorization, secret handling, privacy, dependency risk, and deployment controls still require project-specific review.

Can it review existing code?

Yes. Provide files or a diff and request findings on architecture, behavior, validation, errors, observability, and tests.

Does it support databases beyond Prisma?

The architecture can transfer, but database examples and transaction guidance are written for Prisma.

What context produces the best results?

Provide the feature goal, current layers, data model, API contract, error conventions, and test commands.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/backend-dev-guidelines

Ref

5a26d1d61d694db29af9b138c661c1981076d9df

Maintenance freshness

8/15/2026

Usage

6 downloads · 135 views

File structure

📁 resources/

📄 architecture-overview.md

📄 async-and-errors.md

📄 complete-examples.md

📄 configuration.md

📄 database-patterns.md

📄 middleware-guide.md

📄 routing-and-controllers.md

📄 sentry-and-monitoring.md

📄 services-and-repositories.md

📄 testing-guide.md

📄 validation-patterns.md

📄 SKILL.md

More from sickn33

View all

📦

content-creator

Create Brand-Consistent Marketing Content

Marketing teams need content that stays consistent across channels. This skill helps plan, write, analyze, and optimize content for brand voice and SEO.

Writing & Content View

📦

prompt-engineering-patterns

Improve LLM Prompts With Proven Patterns

Inconsistent prompts waste time and make AI outputs hard to trust. This skill guides prompt design with reusable patterns, examples, evaluation steps, and optimization workflows.

Productivity View

📦

senior-fullstack

Build Fullstack Apps with Senior Patterns

Teams need consistent setup, architecture, and review guidance for modern web applications. This skill provides scaffolders, workflow references, and quality prompts for React, Next.js, Node.js, GraphQL, and PostgreSQL projects.

Coding & Development View

📦

senior-architect

Design Scalable Software Architectures

Architecture decisions are hard to compare across web, mobile, backend, and cloud systems. This skill provides structured guides and local scaffold scripts for reports, dependency review, and trade-off documentation.

Coding & Development View

📦

prompt-engineer

Optimize AI Prompts With Prompt Engineer

Writing clear prompts is hard when goals are vague or complex. This skill turns rough requests into structured prompts using proven prompt frameworks.

Productivity View

📦

product-manager-toolkit

Prioritize Product Work With Research Insights

Product teams need faster ways to rank features, synthesize interviews, and document decisions. This skill provides RICE scoring, interview analysis, and PRD templates for structured planning.

Productivity View

View all

📦

clean-code

Improve TypeScript Clean Code

by DoubleslashSE

Teams lose time when TypeScript code grows duplicated, complex, and hard to test. This skill guides Claude, Codex, and Claude Code toward simpler functions, clearer names, and safer structure.

Coding & Development View

📦

tdd-workflow

Build TypeScript Features with TDD

by DoubleslashSE

Teams often struggle to keep tests focused during fast TypeScript changes. This skill guides RED-GREEN-REFACTOR work with practical Node.js patterns.

Coding & Development View

📦

playwright-testing

Build Reliable Playwright Tests

by C0ntr0lledCha0s

Playwright test suites can become flaky, slow, and difficult to maintain. This skill provides practical patterns for locators, fixtures, page objects, debugging, mocking, and configuration.

Coding & Development View

📦

starknet-js

Build Starknet Apps with starknet.js

by internet-court

Starknet integrations require precise provider, account, transaction, and fee handling across several APIs. This skill provides focused starknet.js v9.x patterns for reliable TypeScript applications.

Coding & Development View

📦

vue-best-practices

Improve Vue 3 Code Quality

by vuejs-ai

Vue projects often collect reactivity, component, and performance mistakes over time. This skill gives targeted Vue 3 guidance for safer patterns and clearer code.

Coding & Development View

📦

react-dev

Build Type-Safe React Components

by softaworks

React TypeScript work often needs precise event, hook, and route types. This skill provides focused patterns for typed components, React 19 APIs, and routing.

Coding & Development View

backend-dev-guidelines

Install with my Agent

Agent-readable resources

Test it

Security Audit

Confirmed security concerns (3)

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Compare variants

Skillstore Score

What You Can Build

Design a New API Feature

Review Backend Architecture

Standardize a Service Team

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details

More from sickn33

content-creator

prompt-engineering-patterns

senior-fullstack

senior-architect

prompt-engineer

product-manager-toolkit

Related Skills

clean-code

tdd-workflow

playwright-testing

starknet-js

vue-best-practices

react-dev