From b00t
Defines .tomllm/.tomllmd conventions: valid TOML with enriched comment annotations (# @tribal:, # @example:, # b00t:map) for LLM consumption. Use when authoring b00t datums.
How this skill is triggered — by the user, by Claude, or both
Slash command
/b00t:tomllm-formatThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The TOML+LLM format defines conventions for enriching valid TOML with comment annotations optimized for LLM consumption. `.tomllm` (machine-oriented) and `.tomllmd` (documentation-heavy) files extend plain `.toml` with three comment conventions: `# @tribal:` / `# 🤓` for non-obvious knowledge, design rationale, and gotchas; `# @example:` for usage examples inline with the datum; and `# b00t:map...
The TOML+LLM format defines conventions for enriching valid TOML with comment annotations optimized for LLM consumption. .tomllm (machine-oriented) and .tomllmd (documentation-heavy) files extend plain .toml with three comment conventions: # @tribal: / # 🤓 for non-obvious knowledge, design rationale, and gotchas; # @example: for usage examples inline with the datum; and # b00t:map v1 as a structured tail-map footer (last ≤10 lines of the file).
The tail-map contains: summary (one-line description, ≤120 chars), tags (comma-separated keywords), tier (sm0l/ch0nky/frontier), cmds (comma-separated relevant commands), and complexity (1-10 integer). The critical rule: the tail-map MUST be the last ≤10 lines of the file — nothing follows it.
Use .tomllmd for documentation-heavy datums like PRDs and schemas. Use .tomllm for machine-oriented configuration datums. Use plain .toml as the fallback. Load this skill when authoring any new b00t datum.
# 🤓 / # @tribal: comments for non-obvious design rationale.# @example: comments for usage examples.# b00t:map v1 as the footer with summary, tags, tier, cmds, complexity.npx claudepluginhub elasticdotventures/_b00t_ --plugin skill-document-understandingReads, writes, and edits TOML files like pyproject.toml in Python using tomlkit to preserve comments/formatting, or tomllib. Covers config management and atomic updates.
Provides syntax rules, quoting conventions, examples, and validation for writing, parsing, and generating TOON files including org-patterns.toon and JSON conversions.
Provides Markdown templates and guidelines for READMEs, API docs, JSDoc/TSDoc comments, changelogs, ADRs, and AI-friendly formats like llms.txt. Use for structuring project documentation.