coding-rules

Enforce coding standards like 0-2 parameters and explicit error handling.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/darsoohoo/intake-bot --skill coding-rules-darsoohoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-rules
Source: https://github.com/darsoohoo/intake-bot/tree/main/.agents/skills/coding-rules
Command: npx skills add https://github.com/darsoohoo/intake-bot --skill coding-rules-darsoohoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Language-agnostic coding standards that promote maintainability, readability, and quality across codebases by enforcing disciplined design practices and consistent conventions.

Core Features & Use Cases

  • Enforces 0-2 parameters per function to promote simple, testable interfaces.
  • Requires explicit error handling, meaningful naming, and clear separation of concerns.
  • Guides code reviews and refactoring to reduce technical debt and improve consistency.

Quick Start

Apply Coding Rules across your codebase to enforce 0-2 parameter functions, explicit error handling, and focused, well-documented design.

Frequently Asked Questions about coding-rules

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

FAQPage Schema
How do I enforce maintainable coding standards during code refactoring?

Enforce maintainable coding standards during refactoring by applying constraints like 0-2 parameters per function, explicit error handling, and single-responsibility functions to reduce technical debt. This ensures interfaces remain simple, testable, and readable across the codebase.

What is the best way to limit function parameters for better code quality?

The best way to limit function parameters for code quality is enforcing a strict 0-2 parameter constraint per function. This promotes simple, testable interfaces and meaningful naming while requiring explicit dependency injection for complex data.

Can I use these coding rules for both frontend and backend TypeScript projects?

Yes, you can use these coding rules for both frontend and backend TypeScript projects. The standards are language-agnostic and applicable across frontend, backend, and library codebases during feature development and audits.

How do I handle errors explicitly to improve codebase maintainability?

Handle errors explicitly to improve maintainability by requiring clear error handling protocols within your functions. This disciplined design practice ensures robust execution, consistent conventions, and reduces hidden technical debt across projects.

Why does single-responsibility design help with code reviews?

Single-responsibility design helps with code reviews by ensuring functions have a clear separation of concerns and meaningful naming. This focused structure guides reviewers, improves consistency, and makes technical debt easier to identify.