code-quality

When starting or scaffolding any project, set up formatting, linting, import sorting, type checking, and pre-commit hooks before writing application code. This prevents the painful scenario of adding these tools later and facing thousands of lines of formatting changes in a single commit.

Determine the project type from existing files or the scaffolding context:

| pyproject.toml, setup.py, requirements.txt, .py files | Python | | package.json, tsconfig.json, .ts/.js/.tsx files | JavaScript/TypeScript | | Both present | Monorepo — configure each ecosystem separately |

Set up formatting, linting, import sorting, type checking, and pre-commit hooks when scaffolding or starting a new project. Use this skill whenever creating a new project, initializing a repo, scaffolding an app, or when the user asks to add linting/formatting to an existing project. Triggers on: "new project", "scaffold", "init", "set up linting", "add formatter", "add pre-commit hooks", "configure biome", "configure ruff". The goal is to establish code quality tooling from day one so issues are caught incrementally, not in a painful bulk-fix later. Source: rarestg/rarestg-skills.