Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

code-quality

Estrellas1

Forks0

Actualizado27 de marzo de 2026 a las 03:55

SOLID principles, naming, and "No Comments" policy for GitData-BackEnd.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

agussantinelli

agussantinelli/GitData

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	code-quality
description	SOLID principles, naming, and "No Comments" policy for GitData-BackEnd.

💎 GitData BackEnd Code Quality

Standardized rules for maintaining a robust NestJS engine.

📏 General Rules

No Comments: Code must be self-explanatory.
SOLID: Follow SOLID principles strictly.
Single Responsibility: Each service/method should do one thing well.
Type Safety: Use TypeScript and Zod to ensure data integrity across all layers. is doing. If the code is complex, refactor it or use descriptive variable/function names.
- Exception: Only use comments for complex algorithmic "why" or to document public APIs (JSDoc).
Descriptive Names: Use intention-revealing names for variables, functions, and classes.
Small Functions: Functions should do one thing and be small.
DRY: Don't Repeat Yourself. Abstract common logic.
Clean Diff: Keep your changes focused and remove any commented-out code before committing.

Más de este repositorio

mismo repositorio

node

agussantinelli/GitData

Node.js best practices and runtime configuration for GitData-BackEnd.

2026-07-081

frontend-test-enforcement

agussantinelli/GitData

Mandatory rule requiring a corresponding Vitest/React Testing Library test file for every React component (.tsx) in GitData frontend.

2026-07-071

global-skills

agussantinelli/GitData

Catalog of all specialized skills used across the GitData Monorepo project.

2026-07-061

widget-inference

agussantinelli/GitData

Guidelines for mathematically deducing advanced widget data on the backend.

2026-07-061

github-api-hybrid

agussantinelli/GitData

Rules for using both GraphQL and REST APIs simultaneously for GitHub data fetching.

2026-07-061

widget-i18n-architecture

agussantinelli/GitData

Architecture rules for building UI widgets, supporting i18n locales, and multi-theme logic.

2026-07-061

name	code-quality
description	SOLID principles, naming, and "No Comments" policy for GitData-BackEnd.

💎 GitData BackEnd Code Quality

Standardized rules for maintaining a robust NestJS engine.

📏 General Rules

No Comments: Code must be self-explanatory.
SOLID: Follow SOLID principles strictly.
Single Responsibility: Each service/method should do one thing well.
Type Safety: Use TypeScript and Zod to ensure data integrity across all layers. is doing. If the code is complex, refactor it or use descriptive variable/function names.
- Exception: Only use comments for complex algorithmic "why" or to document public APIs (JSDoc).
Descriptive Names: Use intention-revealing names for variables, functions, and classes.
Small Functions: Functions should do one thing and be small.
DRY: Don't Repeat Yourself. Abstract common logic.
Clean Diff: Keep your changes focused and remove any commented-out code before committing.