ln-740-quality-setup

Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap

Coordinates code quality tooling configuration for the project.

Purpose & Scope

Does:

• Detects project technology stack (TypeScript/React, .NET, Python)
• Checks for existing quality configurations
• Delegates to specialized workers for each quality aspect
• Verifies final configuration works correctly

Does NOT:

• Generate configuration files directly (workers do this)
• Modify source code
• Run in isolation (requires ln-720 structure first)

When to Use

Workflow Overview

Phase 1: Stack Detection

Detect project technologies to determine which quality tools to configure.

Detection Rules:

package.json

tsconfig.json

*.csproj

*.sln

pyproject.toml

requirements.txt

Actions:

1. Glob for technology indicators
2. Build technology list
3. Log detected stack to user

Phase 2: Existing Configuration Check

Before delegating, check what configurations already exist.

Config Files to Check:

eslint.config.*

.prettierrc*

tsconfig.json

.editorconfig

Directory.Build.props

ruff.toml

pyproject.toml [tool.ruff]

.husky/

.pre-commit-config.yaml

vitest.config.*

pytest.ini

*.Tests.csproj

Decision Matrix:

Phase 3: Parallel Delegation

Invoke workers for each quality aspect. Workers can run in parallel as they configure independent tools.

Delegation Order:

ln-740 (this)
    |
    +---> ln-741-linter-configurator
    |         - ESLint/Prettier (TypeScript)
    |         - editorconfig/Roslyn (.NET)
    |         - Ruff (Python)
    |
    +---> ln-742-precommit-setup
    |         - Husky + lint-staged (Node.js)
    |         - pre-commit framework (Python)
    |         - commitlint
    |
    +---> ln-743-test-infrastructure
              - Vitest (TypeScript)
              - xUnit (.NET)
              - pytest (Python)

Pass detected stack and existing configs to workers via direct Skill tool invocation.

Phase 4: Verification

After all workers complete, verify the quality pipeline works.

Verification Steps:

npm run lint

ruff check .

dotnet format --verify-no-changes

npm run format:check

ruff format --check

npm test

pytest

dotnet test

On Failure:

1. Log specific failure
2. Suggest fix or re-run specific worker
3. Do NOT mark as complete until verification passes

Critical Rules

RULE 1: Never overwrite existing user configurations without explicit confirmation.

RULE 2: Workers run AFTER stack detection - do not invoke workers without knowing the stack.

RULE 3: Verification phase is MANDATORY - quality setup is not complete until tools run successfully.

RULE 4: eslint-config-prettier is REQUIRED when both ESLint and Prettier are configured.

Definition of Done

• All detected technology stacks have appropriate quality tools
• Existing configurations preserved or backed up
• Lint command runs without errors
• Format command runs without errors
• Test command runs and sample tests pass
• Pre-commit hooks trigger on test commit
• User informed of all installed tools and commands

Reference Files

Error Handling

git init

Version: 2.0.0 Last Updated: 2026-01-10