harness-skills

Keep environment variables and deploy-time settings inside a typed config boundary

Enforce six-layer forward-only imports: types -> config -> repositories -> services -> runtime -> ui

Write ADRs for harness boundaries, provider choices, dependency exceptions, and enforcement changes

Introduce the six-layer harness into an existing TypeScript project gradually

Fix six-layer harness violations reported by dependency-cruiser, ESLint, or review

Review a PR for six-layer harness, provider, ADR, and enforcement consistency

Keep auth, telemetry, flags, and external connectors behind provider interfaces

Keep database and ORM access inside repository implementations

Keep business use cases in services and keep runtime/UI concerns outside them

Keep HTTP, queue, and cron handlers focused on protocol translation

Start new domain entities from the type layer before repository, service, runtime, or UI code

Keep UI focused on rendering and input while preserving typed boundaries