Standardizes code formatting and linting for TypeScript projects.
Install
mkdir -p .claude/skills/formatting-standards && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14740" && unzip -o skill.zip -d .claude/skills/formatting-standards && rm skill.zipInstalls to .claude/skills/formatting-standards
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Formatting and linting standards using GTS, ESLint, and Prettier. Use when writing or formatting TypeScript code in this project.Key capabilities
- →Enforce code quality using ESLint.
- →Apply formatting using Prettier.
- →Adhere to Google TypeScript Style (GTS).
- →Configure indentation to 4 spaces.
- →Set line width to 160 characters.
- →Ensure single quotes and required semicolons.
How it works
This skill configures and runs ESLint, Prettier, and GTS to enforce specific formatting and linting standards for TypeScript code, including rules for indentation, line width, import spacing, and quote styles. It also integrates with VS Code for automatic formatting.
Inputs & outputs
When to use formatting-standards
- →Format codebase
- →Fix linting errors
- →Ensure style consistency
About this skill
Formatting Standards
Tools
This repository uses:
- ESLint for code quality (extends GTS)
- Prettier for formatting (extends GTS)
- GTS (Google TypeScript Style) for TypeScript style
Configuration Files
.eslintrc.json- ESLint configuration (extends GTS).prettierrc.js- Prettier configuration (extends GTS).eslintignore- Files to ignore for linting.prettierignore- Files to ignore for formatting
Formatting Rules
Based on GTS and project configuration:
- Indentation: 4 spaces (not tabs)
- Line Width: 160 characters
- Import Spacing: Spaces around braces:
{ Item }not{Item} - Function Signatures: Multi-line when they exceed print width
- Arrow Functions: Parentheses around single parameters:
(x) =>notx => - Quotes: Single quotes (from GTS)
- Semicolons: Required (from GTS)
- Trailing Commas: ES5 style (from GTS)
Running Formatting
# Format all files
npm run format
# Check formatting without writing
npm run format:check
# Format and fix linting issues
npm run format:fix
VS Code Integration
Format on save is configured in .vscode/settings.json:
- Prettier is the default formatter
- ESLint auto-fix on save
- Format on save enabled for TypeScript, JavaScript, JSON
Before Committing
Always run:
npm run format:fix
This ensures:
- Code is formatted according to GTS/Prettier rules
- Linting issues are automatically fixed
- Consistent code style across the repository
When not to use it
- →When not writing or formatting TypeScript code.
- →When the project does not use GTS, ESLint, or Prettier.
- →When different formatting rules are required.
Limitations
- →The skill is specific to TypeScript code.
- →It relies on `.eslintrc.json`, `.prettierrc.js`, `.eslintignore`, and `.prettierignore` for configuration.
- →VS Code integration is configured via `.vscode/settings.json`.
How it compares
This skill provides a standardized and automated way to enforce a specific set of TypeScript formatting and linting rules (GTS-based), ensuring consistent code style across a project unlike manual formatting.
Compared to similar skills
formatting-standards side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| formatting-standards (this skill) | 0 | 7mo | Review | Beginner |
| schema-markup | 10 | 6mo | No flags | Intermediate |
| coding-standards | 7 | 2mo | Review | Intermediate |
| antfu | 6 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
coding-standards
affaan-m
适用于TypeScript、JavaScript、React和Node.js开发的通用编码标准、最佳实践和模式。
antfu
antfu
Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
method-shorthand-jsdoc
EpicenterHQ
Move helper functions into return objects using method shorthand for proper JSDoc preservation. Use when factory functions have internal helpers that should expose documentation to consumers, or when hovering over returned methods shows no JSDoc.
explain-code
AgnosticUI
Explain what code does in plain English
jsdoc
shift-editor
Add or revise source-level JSDoc for Shift APIs. Use this skill before writing or editing documentation comments for exported classes, methods, constructors, domain data structures, render frames, reactive state, or any API where caller intent, side effects, lifetime, ownership, or nullability are e