harness-layer-fix

スター0

フォーク0

更新日2026年6月30日 04:58

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

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

feel-flow

feel-flow/harness-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Harness Layer Fix

Steps

Identify the violated rule and source/target files.
Classify each file into types, config, repositories, services, runtime, or ui.
Prefer moving behavior to the correct layer over adding exceptions.
If an exception is truly required, create or update an ADR first.
Re-run the exact failing command.

Checklist

Violation is fixed without introducing a new reverse dependency
No layer skip was added to hide the issue
ADR exists for intentional exceptions
npm run harness:depcruise or equivalent passes

このリポジトリの他の Skills

同じリポジトリ

config-boundary

feel-flow/harness-skills

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

2026-06-300

forward-only-layers

feel-flow/harness-skills

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

2026-06-300

harness-adr-write

feel-flow/harness-skills

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

2026-06-300

harness-bootstrap

feel-flow/harness-skills

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

2026-06-300

harness-pr-review

feel-flow/harness-skills

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

2026-06-300

provider-boundary

feel-flow/harness-skills

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

2026-06-300

name	harness-layer-fix
description	Fix six-layer harness violations reported by dependency-cruiser, ESLint, or review
metadata	{"type":"Playbook","origin":"harness-engineering/ch12-13","helpful":0,"harmful":0,"status":"active"}

Harness Layer Fix

Steps

Identify the violated rule and source/target files.
Classify each file into types, config, repositories, services, runtime, or ui.
Prefer moving behavior to the correct layer over adding exceptions.
If an exception is truly required, create or update an ADR first.
Re-run the exact failing command.

Checklist

Violation is fixed without introducing a new reverse dependency
No layer skip was added to hide the issue
ADR exists for intentional exceptions
npm run harness:depcruise or equivalent passes