coding-patterns

Codify TypeScript coding patterns and conventions for monorepo consistency.

9|2|Updated Apr 13, 2024
One-click install
npx skills add https://github.com/JacobLey/leyman --skill coding-patterns-jacobley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-patterns
Source: https://github.com/JacobLey/leyman/tree/main/.claude/skills/coding-patterns
Command: npx skills add https://github.com/JacobLey/leyman --skill coding-patterns-jacobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In large TypeScript monorepos, coding patterns and conventions can diverge, creating cognitive overhead, inconsistent APIs, and onboarding friction. This skill codifies best practices around package design, type safety, dependency injection, and documentation to foster coherence and maintainability.

Core Features & Use Cases

  • Standardized package boundaries and design guidance to keep modules focused and composable.
  • Enforced TypeScript practices: immutability, precise typing, no unknown/any, and explicit exports.
  • Guidance for documentation and learnings to accelerate onboarding and collaboration.

Quick Start

Adopt these patterns in your TypeScript projects to improve readability, consistency, and maintainability.

Frequently Asked Questions about coding-patterns

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

FAQPage Schema
How do I enforce consistent coding patterns in a TypeScript monorepo?

Standardizing TypeScript coding patterns involves enforcing immutability, precise typing without unknown or any, explicit named exports, and internal import aliases. This ensures code quality and consistency across a monorepo.

What's the best way to standardize dependency injection patterns in TypeScript?

The best way to standardize dependency injection patterns in TypeScript is to codify explicit conventions for package boundaries and module design. This keeps modules focused, composable, and maintainable across large projects.

How do I prevent API divergence and onboarding friction in large TypeScript projects?

Prevent API divergence and onboarding friction in large TypeScript projects by applying standardized package boundaries and documentation guidance. Consistent conventions accelerate collaboration and improve system maintainability.

Does this TypeScript coding convention require specific linting dependencies?

No specific linting dependencies are required. The guidance codifies architectural patterns for package design, precise typing, immutability, and dependency injection directly into your TypeScript workflow without external component dependencies.

When should I standardize package design and explicit typing in TypeScript?

Standardize package design and explicit typing in TypeScript when your monorepo experiences diverging coding patterns, cognitive overhead, or inconsistent APIs. Applying these conventions fosters coherence and maintainable software systems.