What problem does it solve?
Markdown files used by agents, indexers, and ontology pipelines need consistent YAML front matter, but dialects differ widely (Agent Skills, Obsidian, Jekyll, Hugo), causing tag extraction errors and metadata drift.
Core Features & Use Cases
- Three-field default convention: Standardizes markdown metadata on
tags, description, and memo (an ISO 8601 timestamped revision log), with extensions like issue: for design stories and repo:/number: for GitHub issue bodies.
- Helper commands:
x yfm ls lists YFM blocks, x yfm init writes default blocks into markdown files, and x yfm lint validates blocks against their claimed dialect.
- Dialect reference guides: Per-dialect extraction rules for Agent Skills, Obsidian, Jekyll, and Hugo, covering separator differences, reserved keys, and tag hierarchy semantics.
- Use Case: When writing a GitHub issue body or a design story under
.x-cmd/story/, generate a conforming front matter block and lint it so the ontology collector can index tags and relations correctly.
Quick Start
Ask the agent to add a standard YAML front matter block with tags, description, and memo to every markdown file in the current project and lint them for dialect conformance.