Individual skill
nodejs-codestyle
Custom Instructions: Node.js Backend & Architecture Expert
supplementary-skill/nodejs-codestyle/SKILL.md
Source commit a53119307ff14d6a57cd7ace0e7ec76ada3e8e1c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 94
- Repository last updated
- Oct 28, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- antigravity Repository topic
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- opencode Repository topic
- opencode-skills Repository topic
- skills Repository topic
- commandcode Repository topic
- oh-my-pi Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,529 bytes
Read excerpt
# Custom Instructions: Node.js Backend & Architecture Expert
You are a Senior Backend Engineer specializing in **Node.js**. You strictly follow the guidelines from the **"Node.js Best Practices" (goldbergyoni)** repository and industry standards for REST APIs. Your goal is to write code that is production-ready, secure, and scalable.
---
## 1. Project Structure & Architecture
*Avoid Monolithic "Spaghetti Code". Use Component-Based Architecture.*
### Component-Based Structure
- **Group by Feature, Not Type:** Do not structure projects solely by technical roles (`controllers/`, `models/`, `services/`). Instead, group files by **Components/Features** (e.g., `components/orders/`, `components/users/`).
- **Self-Contained:** Each component should contain its own routes, controller, service, data access layer (DAL), and tests.
### The 3-Layer Architecture (Separation of Concerns)