coding-standards

Enforces cross-project coding conventions for naming, immutability, readability, and code review.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill coding-standards-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/diazMelgarejo/orama-system/tree/main/.cursor/.agents/skills/coding-standards
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill coding-standards-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to keep code consistent across projects and contributors, leading to unreadable code, mutation bugs, and inconsistent review standards. This Skill provides a shared baseline of coding conventions that applies to any TypeScript, JavaScript, or React project. ## Core Features & Use Cases - Naming and Readability Rules: Enforces descriptive variable and function names, verb-noun function patterns, and self-documenting code over comments. - Immutability and Error Handling: Mandates spread-operator updates instead of direct mutation, plus structured try/catch patterns and typed API responses. - Code Smell Detection: Flags long functions, deep nesting, and magic numbers with concrete before-and-after examples. - Use Case: When reviewing a pull request in a Next.js project, activate this Skill to check naming, immutability, async patterns, and validation against a consistent baseline before approving. ## Quick Start Ask the AI to review your current file or module against the coding-standards conventions and list any violations with fixes.

Frequently Asked Questions about coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent coding standards across a team?

Apply a shared baseline of conventions covering naming, immutability, error handling, and file organization, then reference it during code reviews. This Skill provides that baseline with concrete pass/fail examples for TypeScript, JavaScript, and React code.

What are the best practices for immutability in JavaScript?

Always use the spread operator to create updated copies of objects and arrays instead of mutating them directly. For example, use {...user, name: 'New Name'} rather than user.name = 'New Name', and [...items, newItem] rather than items.push(newItem).

When should I use this skill instead of framework-specific guidelines?

Use it for cross-project concerns like naming, readability, immutability, and code smell review. For React hooks, rendering patterns, backend architecture, or API design, defer to the dedicated frontend-patterns, backend-patterns, or api-design skills.

How do I validate API request bodies in Next.js?

Define a Zod schema describing the expected shape, then call schema.parse(body) inside your route handler. Catch ZodError to return a 400 response with validation details, keeping invalid data out of your business logic.

What code smells should I look for during code review?

Watch for functions longer than about 50 lines, nesting deeper than a few levels, and unexplained magic numbers. Fix them by splitting functions, using early returns to flatten logic, and replacing literals with named constants.