Dimonier Skills

Convert PDF files to Markdown — extracts text with pdfplumber and describes images/diagrams via a local vision-language model. Use when the user asks to extract PDF content, convert presentation slides to text, transcribe conference talks from PDFs, or OCR diagrams and charts from documents.

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.

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.

Maintains project state in a markdown vault (decisions, open questions, risks, contradictions) from transcripts, notes, PDFs, or owner chat. Governs working tracks as the mandatory container for productive work. Use after meetings, briefings, decisions; inbox/outbox; vault init.

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.

Lossless compaction of epistemes: prose ↔ compact typed-slot notation (F4-F5, ~65% token savings) with a source-claims vs [bracketed] split and reconstruction back to source. Use for AI-agent or FPF-literate-human output needing token economy and auditability. NOT narrativization. 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.

Business Analysis & Requirements Engineering. Use when: identifying stakeholders, eliciting or specifying requirements, prioritizing, validating, tracing, or managing requirements changes. Depends on fpf-core.

Author and improve a Domain Principle Framework (DPF) or Local Practices Framework (LPF) directly in Agent-skill form (SKILL.md + references/). Use when creating, revising, or maintaining a DPF/LPF as a skill, or when the user mentions "pattern language as agent skill".