formatting-standards

Name: formatting-standards
Availability: InStock
Author: crmagz

Enforce GTS, ESLint, and Prettier formatting standards on TypeScript code.

6|Updated Dec 26, 2025

Search Tags:#typescript #linting #formatting #eslint #prettier #coding-standards #gts

Ready to run

npx skills add https://github.com/crmagz/cdk-constructs-library --skill formatting-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: formatting-standards
Source: https://github.com/crmagz/cdk-constructs-library/tree/main/.claude/skills/formatting-standards
Command: npx skills add https://github.com/crmagz/cdk-constructs-library --skill formatting-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formatting and linting standards for TypeScript projects using GTS, ESLint, and Prettier to ensure consistent style across the codebase.

Core Features & Use Cases

Config-driven formatting: Rely on GTS-based rules and project configs (.eslintrc.json, .prettierrc.js, .eslintignore, .prettierignore) to standardize code style.
Automated formatting & linting: Run npm scripts to format, check, and fix code alignment with the standard.
Use Case: A team migrating a TS codebase can apply the same formatting rules to avoid style drift and improve readability.

Quick Start

Format all project files with npm run format to apply GTS/ESLint/Prettier rules.

Frequently Asked Questions about formatting-standards

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

FAQPage Schema

How do I enforce consistent TypeScript formatting and linting across a project?▼

This Skill automates TypeScript formatting and linting by applying GTS, ESLint, and Prettier rules through project configuration files, ensuring consistent code style across all TS files in your repository.

What is the best way to automate code style checks for TypeScript files?▼

The best way to automate code style checks is using npm scripts like format, format:check, and format:fix, which run GTS, ESLint, and Prettier against your codebase to detect and resolve style drift.

How do I configure ESLint and Prettier rules for a TypeScript codebase migration?▼

You configure ESLint and Prettier for TypeScript migration by aligning your project with GTS-based configuration files, including .eslintrc.json, .prettierrc.js, .eslintignore, and .prettierignore to maintain uniform style.

Can I use GTS to standardize formatting across all TS files and configuration files?▼

Yes, you can use GTS to standardize formatting across all TS files and configuration files, applying consistent linting and formatting rules throughout the entire repository to prevent style inconsistencies.

Does this TypeScript formatting approach work with existing project configuration files?▼

Yes, this TypeScript formatting approach works with existing project configuration files, requiring alignment with your .eslintrc.json and .prettierrc.js setups to apply the standardized GTS rules correctly.

What are the limitations of using GTS for TypeScript linting and formatting?▼

A limitation of using GTS for TypeScript linting is that it requires strict alignment with specific project configuration files, meaning pre-existing custom ESLint or Prettier setups may need adjustment to avoid conflicts.