workspace-code-standards

Enforce TypeScript and ESLint standards across workspace codebases.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill workspace-code-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-code-standards
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/workspace-code-standards
Command: npx skills add https://github.com/open-hax/opencode-skills --skill workspace-code-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enforces a unified TypeScript and ESLint standard across the workspace to prevent style drift, improve readability, and catch issues early during development.

Core Features & Use Cases

  • ESM only: Enforces no require or module.exports, encouraging modern module syntax.
  • Functional style: Prefers const, minimizes let, and discourages classes to improve predictability.
  • TypeScript strict: Forbids any, enforces explicit types, and promotes readonly parameters.
  • Import order: Enforces a consistent import sorting rule: builtin -> external -> internal -> sibling -> index.
  • Code quality gates: Limits function length, cognitive complexity, parameter counts, and file size to promote maintainability.
  • Quick adoption: Integrates with existing tooling and CI to progressively enforce standards.

Quick Start

Run the workspace-code-standards guidelines on your TypeScript project to enforce consistent style and typing across the codebase.

Frequently Asked Questions about workspace-code-standards

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

FAQPage Schema
How do I enforce TypeScript strict mode and ban `any` across my entire workspace?

To enforce TypeScript strict mode across a workspace, apply predefined linting rules that forbid `any`, require explicit types, and promote readonly parameters. This ensures a consistent typing discipline and prevents style drift across all project modules.

What's the best way to enforce import order in a TypeScript monorepo?

Enforcing import order in TypeScript requires applying strict sorting rules: builtin -> external -> internal -> sibling -> index. This standardized import structure improves code readability and maintains consistency across all modules in the repository.

How do I enforce ESM usage and prevent `require` in my TypeScript codebase?

To enforce ESM usage in TypeScript, apply static analysis rules that explicitly forbid `require` and `module.exports`. This encourages modern module syntax and ensures consistent functional style across the entire workspace codebase.

Can I use these ESLint standards to limit function length and cognitive complexity?

Yes, you can use these ESLint standards to limit function length, cognitive complexity, parameter counts, and file size. These code quality gates promote maintainability and catch potential architectural issues early during development.

Does this workspace code quality tooling integrate with existing CI pipelines?

Yes, workspace code standards integrate with existing tooling and CI pipelines to progressively enforce standards. This allows teams to adopt strict TypeScript, ESM, and functional style rules without disrupting current development workflows.

Why should I discourage classes and minimize `let` in my TypeScript projects?

Discouraging classes and minimizing `let` in TypeScript projects enforces a functional style that improves predictability. Preferring `const` reduces side effects and ensures a consistent coding standard across the entire workspace.