Here are 3 proposals formatted in a markdown table:
| Proposal | Unified Tech | Plain Name | MDS | Purpose/Use-Domain | Key Use Cases | Lexical Scores |
|:---|:---|:---|:---|:---|:---|:---|
| **1** (default) | `fpf-skillbox` | FPF skill box | A versioned carrier containing standalone "skill" descriptions extracted from FPF, treated as an unordered collection (no explicit edges). | Store and retrieve FPF-extracted skills as a flat set (relationships exist but remain unencoded). | • Add new extracted skill without deciding taxonomy
• Grab 1–3 relevant skills fast during design/review
• Reference a skill from another repo/doc without importing whole framework
• Teach by "opening the box" and selecting handful of skills | SemanticFidelity=Exact
CognitiveErgonomics=Acceptable
OperationalAffordance=Role-hinting
AliasRisk=Context-dependent |
| **2** | `fpf-skill-extracts` | FPF skill extracts | A versioned carrier of skill descriptions extracted from FPF patterns, maintained as reusable standalone fragments. | Emphasize provenance ("these come from FPF") more than structure ("box"). | • Show repo as derivative artifact, not "the framework"
• Diff what you extracted vs what you plan to extract
• Reference extracted skills in downstream projects with clear provenance
• Curate extracted skills over time without implying full coverage | SemanticFidelity=Exact
CognitiveErgonomics=Acceptable
OperationalAffordance=Action-aligned
AliasRisk=Safe |
| **3** | `fpf-skill-cards` | FPF skill cards | A versioned carrier containing one-per-file "skill cards" extracted from FPF, each readable standalone and linkable by reference. | Optimize for didactic/UX: each skill lives as a "card" you can read standalone. | • Onboard someone by sending 5 card links
• Add new card without touching global structure
• Review a card in a PR like any other doc artifact
• Use cards as prompts/checklists during work session
• Export cards into other surfaces later (wiki, site) | SemanticFidelity=Precise
CognitiveErgonomics=Natural
OperationalAffordance=Role-hinting
AliasRisk=Safe |
**Quick Decision Guide:**
- Choose **Proposal 1** (`fpf-skillbox`) for maximum flexibility and structure-neutrality
- Choose **Proposal 2** (`fpf-skill-extracts`) when provenance and traceability matter most
- Choose **Proposal 3** (`fpf-skill-cards`) when optimizing for teaching/onboarding and you're committed to card-per-file format
