forward-only-layers

スター0

フォーク0

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

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

インストール

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

Manusで実行

ソース

feel-flow

feel-flow/harness-skills

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

ダウンロード

Manusで実行

Forward-Only Layers

Rules

Layer order is types -> config -> repositories -> services -> runtime -> ui.
Outer layers can import inner layers. Inner layers cannot import outer layers.
UI/runtime must not skip services to import repositories or ORM clients.
Services must not import runtime, UI, route handlers, or framework response types.
Cross-cutting concerns go through providers.
Cycles are forbidden.

Checklist

Import direction follows the layer order
No direct UI/runtime to repository or ORM access
No service to runtime/UI dependency
Cycles are checked with madge or equivalent
dependency-cruiser rule comments point to ADRs where needed

このリポジトリの他の Skills

同じリポジトリ

config-boundary

feel-flow/harness-skills

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

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-layer-fix

feel-flow/harness-skills

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

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	forward-only-layers
description	Enforce six-layer forward-only imports: types -> config -> repositories -> services -> runtime -> ui

Forward-Only Layers

Rules

Layer order is types -> config -> repositories -> services -> runtime -> ui.
Outer layers can import inner layers. Inner layers cannot import outer layers.
UI/runtime must not skip services to import repositories or ORM clients.
Services must not import runtime, UI, route handlers, or framework response types.
Cross-cutting concerns go through providers.
Cycles are forbidden.

Checklist

Import direction follows the layer order
No direct UI/runtime to repository or ORM access
No service to runtime/UI dependency
Cycles are checked with madge or equivalent
dependency-cruiser rule comments point to ADRs where needed