coding-standards

Standardize TypeScript/JavaScript coding conventions and architectural patterns across frontend and backend development.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill coding-standards-thejanajayalath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/ThejanaJayalath/Niolla-PM-system/tree/main/.cursor/.agents/skills/coding-standards
Command: npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill coding-standards-thejanajayalath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the inconsistency and technical debt that arise when multiple developers contribute to a codebase without a unified set of rules for naming, structure, and quality.

Core Features & Use Cases

  • Standardized Conventions: Provides clear guidelines for TypeScript/JavaScript naming, immutability, and error handling.
  • Quality Assurance: Offers a framework for code reviews, focusing on readability, KISS, DRY, and YAGNI principles.
  • Use Case: When onboarding a new developer or starting a new module, use this Skill to ensure the implementation aligns with the project's established architecture and React/API patterns.

Quick Start

Use the coding-standards skill to review the current module for adherence to naming conventions and error handling 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 clean code and coding standards during a React and TypeScript code review?

Enforce coding standards during code reviews by applying guidelines for TypeScript naming, immutability, and error handling. Review React and API patterns against KISS, DRY, and YAGNI principles to ensure readability, type safety, and maintainability across the codebase.

What's the best way to standardize API response structures and naming conventions across frontend and backend modules?

Standardize API response structures and naming conventions by applying unified architectural patterns across frontend and backend development. Enforce consistent TypeScript conventions, type safety, and immutability rules to achieve a maintainable and scalable codebase.

When do I need to apply coding standards for refactoring tasks and new feature implementation?

Apply coding standards during refactoring tasks and new feature implementation to prevent technical debt. Use them when onboarding new developers or starting modules to ensure implementations align with established React/API patterns and maintain readability.

Can I use these coding conventions to improve type safety and immutability in an existing JavaScript codebase?

Yes, you can use these coding conventions to improve type safety and immutability in an existing JavaScript codebase. The standards provide clear guidelines for migrating toward TypeScript, enforcing error handling, and applying clean code principles during refactoring.

Does this approach to clean code support both frontend React patterns and backend API development?

Yes, this approach supports both frontend React patterns and backend API development. It standardizes architectural patterns across the entire stack, applying consistent rules for naming, type safety, and API response structures to ensure scalable code.