jmisilo/coding-styleguide

Overview

This skill is a curated set of balanced coding patterns and practical best practices designed to improve development velocity, maintainability, and scalability. It consolidates reusable design patterns, coding standards, and architecture guidance that apply across languages and frameworks. The patterns emphasize clarity, testability, and predictable production behavior.

How this skill works

The skill inspects common pain points in application design—third-party integrations, component structure, routing, and production operational concerns—and provides concrete pattern choices and implementation notes. It recommends minimal, pragmatic approaches: small composable components, clear interaction boundaries for external services, and operational checks for reliability. Each guideline includes rationale, trade-offs, and examples to help teams adopt patterns consistently.

When to use it

• When starting a new project to set consistent architecture and coding standards
• When refactoring to improve maintainability and reduce technical debt
• When integrating third-party services to minimize coupling and failure blast radius
• When building UI components to enforce predictable composition and reuse
• When preparing systems for production stability and observability

Best practices

• Favor small, single-responsibility modules and explicit interfaces
• Encapsulate third-party interactions behind adapters and retries with backoff
• Design UI components as pure functions with clear props and limited side effects
• Define and document failure modes, monitoring signals, and operational runbooks early
• Prioritize automated tests and simple CI checks that validate behavior across layers

Example use cases

• Implement an adapter layer for payment or API providers to allow easy provider swaps
• Refactor a monolithic frontend into composable React components with consistent props and testing patterns
• Apply retry, timeout, and circuit-breaker patterns for unreliable external services
• Standardize production readiness criteria: health checks, metrics, logs, and deploy rollback strategies
• Create language-agnostic patterns for service boundaries to guide multi-team integration