coding-standards

Define universal coding standards for TypeScript, JavaScript, React, and Node.js projects.

171|10|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fmflurry/settings-opencode --skill coding-standards-fmflurry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/fmflurry/settings-opencode/tree/main/skills/coding-standards
Command: npx skills add https://github.com/fmflurry/settings-opencode --skill coding-standards-fmflurry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent coding practices across teams lead to hard-to-maintain code, onboarding friction, and fragile codebases. This Skill defines universal standards to ensure readability, consistency, and maintainability across TypeScript, JavaScript, React, and Node.js projects.

Core Features & Use Cases

  • Readability-first conventions including descriptive naming and consistent formatting.
  • Immutability and safe state management patterns.
  • Standardized API design and documentation practices across projects.
  • Use Case: onboarding new contributors to coding standards and enforcing quality during code reviews.

Quick Start

Use coding-standards to align your team's conventions for naming, formatting, immutability, and review processes across new and existing projects.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I establish universal coding standards for TypeScript and JavaScript projects?

Establish universal coding standards by applying readability-first conventions for descriptive naming, consistent formatting, and immutability practices across your TypeScript and JavaScript codebases.

What coding patterns should I use for React and Node.js codebase consistency?

For React and Node.js codebase consistency, use standardized API design, immutability practices, and structured function design guidelines to ensure maintainability and reduce onboarding friction for new contributors.

Can I use these coding standards during code reviews and refactors?

Yes, you can use these coding standards during code reviews and refactors to enforce quality, apply structured typing and linting guidelines, and ensure consistent architecture conventions across both new work and existing projects.

How do naming conventions and immutability practices improve codebase maintainability?

Naming conventions and immutability practices improve codebase maintainability by enforcing readable, safe state management patterns and standardized API documentation, which reduces fragile code and onboarding friction for new contributors.

What is the best way to document and enforce linting and typing conventions across teams?

The best way to document and enforce linting and typing conventions is implementing integration-ready patterns with frontmatter-driven documentation and structured examples to align team workflows and quality reviews.