ddd:setup-code-formating

Create or update CLAUDE.md with project code formatting rules.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/luicabref97/sushi-jungle-web --skill ddd-setup-code-formating-luicabref97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd:setup-code-formating
Source: https://github.com/luicabref97/sushi-jungle-web/tree/main/.agents/skills/ddd-setup-code-formating
Command: npx skills add https://github.com/luicabref97/sushi-jungle-web --skill ddd-setup-code-formating-luicabref97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates or updates a central style guideline file (CLAUDE.md) to enforce consistent code formatting and style rules across a repository, reducing style drift and code review friction.

Core Features & Use Cases

  • Single-source Style File: Writes a CLAUDE.md containing explicit formatting rules for the project.
  • Enforced Conventions: Captures rules such as no semicolons, single quotes, no unnecessary curly braces, 2-space indentation, and import ordering.
  • Use Cases: Onboard new contributors with a clear style guide, standardize formatting before CI checks, or seed repository-level conventions for monorepos.

Quick Start

Create or update CLAUDE.md with the project's code style rules exactly as specified so linters and contributors follow the same conventions.

Frequently Asked Questions about ddd:setup-code-formating

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

FAQPage Schema
How do I set up consistent code formatting rules across a repository?

To set up consistent code formatting, you can create or update a central CLAUDE.md guideline file to enforce project conventions like no semicolons, single quotes, and 2-space indentation for all contributors.

What is a CLAUDE.md file used for in developer onboarding?

A CLAUDE.md file serves as a single-source style guideline for developer onboarding, explicitly capturing code style rules to reduce style drift and friction during code reviews across the repository.

How do I standardize import ordering and styling before CI checks?

Standardize import ordering before CI checks by defining rules in a CLAUDE.md file, specifying imports from external to internal to types, alongside formatting conventions like no unnecessary curly braces.

Does this code formatting approach work for monorepos?

Yes, this code formatting approach works for monorepos by seeding repository-level conventions in a central CLAUDE.md file to standardize formatting across multiple codebases and developer workflows.

Can I use this to enforce linting rules without adding heavy dependencies?

Yes, you can enforce linting rules by writing a CLAUDE.md style guide file without adding dependencies, capturing explicit formatting rules to guide contributors and linters directly.

What are the limitations of using a style guide file for code formatting?

A limitation of using a style guide file is that it provides documented conventions rather than automated runtime enforcement, requiring contributors to manually follow the CLAUDE.md rules during development.