メニュー
LFW Architecture. Use when: organizing the FPF/DPF/LPF workspace, deciding where to place a new framework, setting up the skill-carrier structure, or resolving LPF vs Project boundary questions. Depends on fpf-core.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dimonier/skills --skill dpf-lfw-architectureコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
First Principles Framework core patterns. Use when doing engineering, research, management, or mixed human/AI work. ALWAYS use as governing patterns for any DPF or LPF work. Load individual patterns from references/ as needed — never read the full spec unless doing deep audit.
Maintains project state in a markdown vault (key decisions, open questions, risks, contradictions, dependencies) from meeting transcripts, structured notes, PDF documents, or owner chat updates. Governs working tracks as the mandatory container for all productive activity (research, analysis, synthesis). Use for updating project-vault after meetings, dialog briefings, decision records, and next-meeting agendas. Triggers: project state, transcripts, meeting notes, PDF documents, chat updates, risks, dependencies, contradictions, ADR-style decisions, track creation and lifecycle, inbox processing.
Sync the fpf-core skill from the canonical FPF-Spec.md monolith. Use when: (1) the FPF specification has been updated (git pull shows new commits), (2) the fpf-core skill references/ are stale or show wrong counts, (3) running scheduled maintenance on LFW skills. Self-contained — bundles decompose_fpf.py + _common.py directly. No dependencies on external skills. Works only with the local skill at `../fpf-core/` (relative to this skill) — NOT the global user skill.
SOC 職業分類に基づく
SKILL.md を表示中
| name | dpf-lfw-architecture |
| description | LFW Architecture. Use when: organizing the FPF/DPF/LPF workspace, deciding where to place a new framework, setting up the skill-carrier structure, or resolving LPF vs Project boundary questions. Depends on fpf-core. |
Governed value: LayeredFrameworkWorkspace (LFW)
Depends on: fpf-core, dpf-fpf-literacy
Bounded context: FPF ecosystem @ AI-assisted work environment
Source of truth: assets/FPF-Ecosystem-Workspace-dpf.md
| Situation | Load | Governing cues → fpf-core |
|---|---|---|
| Packaging a DPF/LPF as a skill | references/1-skill-as-carrier.md | E.4.DPF, C.33 |
| Placing a monolith inside a skill | references/2-monolith-in-skill.md | C.33, E.17.EFP |
| Building a dependency chain | references/3-dependency-chain.md | E.5.3, E.4 |
| SKILL.md as a dispatcher (routing-only) | references/4-skill-dispatcher.md | C.33, E.4.DA |
| Project-level AGENTS.md (what to put in it) | references/5-project-context.md | FPFLIT.AgentContextLoad |
| Distinguishing LPF from Project | references/6-lpf-vs-project.md | E.4, E.5.3 |
references/. DO NOT read assets/FPF-Ecosystem-Workspace-dpf.md.assets/FPF-Ecosystem-Workspace-dpf.md. After edits — rebuild references/.Ready — 6 problem cards + INDEX + relations.