菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate compact, unambiguous FPF-structured output at F4-F5 formality level. Use when writing for AI agent consumers or FPF-literate humans where token economy and auditability matter: diagnostics, architecture decisions, code reviews, status reports, trust assessments, system compositions. Replaces verbose prose (F0) with typed-slot notation (~65% token savings, lossless). Do NOT use for: casual chat, teaching, non-technical audiences, creative tasks.
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.
Spec-Decomposer: splits monolithic framework specifications (FPF/DPF/LPF) into atomic skill reference files. Use when: decomposing a framework monolith into skill references, updating references/ after monolith changes, or setting up a new DPF/LPF skill from a monolith. Depends on fpf-core, dpf-fpf-literacy, dpf-lfw-architecture.
Business Analysis & Requirements Engineering. Use when: identifying stakeholders, eliciting or specifying requirements, prioritizing, validating, tracing, or managing requirements changes. Depends on fpf-core.
FPF Literacy & DPF Authoring. Use when: helping an agent understand the FPF/DPF/LPF stack, creating a new DPF, loading domain knowledge into an agent, distinguishing FPF-grounded answers from generic AI responses, or choosing a carrier for publication. Depends on fpf-core.
Guide for deciding when to create agent skills, how to design them well, and what anti-patterns to avoid. Use when: (1) creating a new skill, (2) deciding between skills vs AGENTS.md vs MCP vs Memory, (3) reviewing an existing skill for quality, (4) unsure if a skill is needed at all.
| 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.