菜单
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.
用 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.
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.
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-fpf-literacy |
| description | 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. |
Depends on: fpf-core (all governing-pattern cues reference FPF Core)
Bounded context: AI-assisted engineering and management work grounded in FPF
Source of truth: assets/FPF-Literacy-dpf.md
| Situation | Load | Governing cues → fpf-core |
|---|---|---|
| Agent gives a "nice but useless" answer | references/1-vanilla-vs-fpf.md | C.22.2, E.17, A.10 |
| Team confuses FPF/DPF/LPF levels | references/2-ecosystem-placement.md | B.2, C.11, E.4.PFAD |
| Time is wasted on clearly unsuitable options | references/3-move-exclusion.md | E.8, G.2, A.21 |
| Need to draft a DPF in one hour | references/4-first-hour-route.md | E.4.DPF, C.22.2, C.33 |
| Agent doesn't know the domain | references/5-agent-context-load.md | C.11, E.16, E.4 |
| Need to improve an existing DPF | references/6-improvement-cycle.md | E.22, E.21, E.23, E.19 |
| Agent proposes a mainstream/shallow solution | references/7-sota-recognition.md | G.2, C.22.2, A.10 |
| Choosing whether to publish in a file or in chat | references/8-carrier-first-entry.md | C.33, E.17.EFP |
| Need a map of relationships between patterns | references/relations.md | E.4.PFR |
First load references/2-ecosystem-placement.md — it determines which level
(FPF/DPF/LPF) the problem belongs to. Then load the specific pattern.
references/. DO NOT read assets/FPF-Literacy-dpf.md.assets/FPF-Literacy-dpf.md. After edits — rebuild references/.Ready — 8 problem cards + INDEX + relations.