coding-standards

Enforce TypeScript, Vue 3, Node-Express, and Mongoose coding conventions.

Updated May 10, 2026
One-click install
npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill coding-standards-mateus2411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/Mateus2411/Hermes-PersonalBot/tree/main/skills/coding-standards
Command: npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill coding-standards-mateus2411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coding standards prevent fragmented styles, inconsistent patterns, and avoidable bugs by aligning every change to a shared set of conventions.

Core Features & Use Cases

  • Project-wide TypeScript & architecture rules: Enforces functional style, explicit types, and consistent export patterns to keep implementations predictable.
  • Framework-specific best practices: Mandates Vue 3 <script setup>, typed props/emits, and composables conventions to reduce integration friction.
  • Backend reliability conventions: Requires async/await, controller-level error handling, and thin routes to improve correctness and maintainability.

Quick Start

Load coding-standards, then implement the requested feature by following the specified TypeScript/Vue/Node/Mongoose and file-naming conventions without introducing new patterns.

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 TypeScript coding conventions across Vue 3 and Node Express projects?

You can enforce consistent TypeScript coding conventions by applying functional style patterns, explicit typing, and standardized export rules across Vue 3 and Node Express projects to prevent style drift and predictable structure.

What are the best practices for Vue 3 script setup and composables naming conventions?

Vue 3 script setup best practices require using typed props and emits alongside standardized composables naming conventions to reduce integration friction and maintain predictable component architecture.

How do I structure Node Express routes and controllers with async await error handling?

Structure Node Express routes and controllers by keeping routes thin, implementing controller-level async await error handling, and applying schema validation to improve backend reliability and maintainability.

Does this coding standards approach work with Mongoose schema validation and safe _id handling?

Yes, this coding standards approach explicitly supports Mongoose schema validation and safe _id handling to ensure backend reliability and prevent avoidable implementation errors during database operations.

Why does my codebase suffer from style drift and inconsistent implementation patterns during refactoring?

Your codebase suffers from style drift and inconsistent implementation patterns during refactoring because coding standards are not enforced, leading to fragmented styles and avoidable bugs across new feature work.