From tp-fpf
Search FPF knowledge base, display hypothesis details with assurance information, and report knowledge base state (hypothesis counts, evidence freshness, decision records).
How this skill is triggered — by the user, by Claude, or both
Slash command
/tp-fpf:fpf-readWhen to use
Use when the user says 'FPF status', 'search FPF', 'query FPF', 'knowledge base', 'what hypotheses do we have', 'show FPF state', 'check evidence freshness', or 'status'. IMMEDIATELY when the user asks to 'look up a hypothesis', 'find decisions', 'show evidence', or 'inspect the FPF knowledge base'. BEFORE making a decision that depends on prior FPF reasoning — verify the hypothesis is still valid.
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
IF searching for existing hypotheses (SAFE READ, no side effects) -> Search across all knowledge layers and display results with evidence
IF searching for existing hypotheses (SAFE READ, no side effects) -> Search across all knowledge layers and display results with evidence IF checking FPF state (SAFE READ, no side effects) -> Count hypotheses per layer, check evidence freshness, list decisions IF no results found -> Suggest starting a fresh hypothesis cycle IF knowledge base empty -> Show "not initialized" with option to start a fresh hypothesis cycle
Decisions without evidence are guesses. You can't manage what you don't measure. The FPF knowledge base is the audit trail for every significant choice -- regular inspection prevents epistemic debt.
.fpf/knowledge/L0/, .fpf/knowledge/L1/, .fpf/knowledge/L2/, .fpf/knowledge/invalid/, and .fpf/decisions/ for matching the query| Location | Contents |
|---|---|
.fpf/knowledge/L0/ | Proposed hypotheses |
.fpf/knowledge/L1/ | Verified hypotheses |
.fpf/knowledge/L2/ | Validated hypotheses |
.fpf/knowledge/invalid/ | Rejected hypotheses |
.fpf/decisions/ | Design Rationale Records |
.fpf/evidence/ | Evidence and audit files |
.fpf/ exists with required subdirectories.fpf/evidence/ for expired evidence.fpf/decisions/## Results for: {query}
| ID | Title | Layer | Kind | R_eff | Scope |
|----|-------|-------|------|-------|-------|
| ... | ... | L2 | functional | 0.89 | api-design |
## FPF Status
### Directory Structure
- [x] .fpf/ exists
- [x] knowledge/L0/ exists ({n} hypotheses)
- [x] knowledge/L1/ exists ({n} verified)
- [x] knowledge/L2/ exists ({n} validated)
- [x] knowledge/invalid/ exists ({n} rejected)
- [x] evidence/ exists ({n} evidence files)
- [x] decisions/ exists ({n} decision records)
### Evidence Freshness
- Fresh: {n}
- Stale: {n}
- Expired: {n}
- Waived: {n}
npx claudepluginhub git-fg/taches-principled --plugin tp-fpfProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.