fixmyberlin/tilda-geo · Archived

topic-docs-yaml-authoring

Author and review `topic-docs` YAML files with valid field combinations, refs, and value reuse patterns. Use when creating or editing `topic-docs/*.yaml`, `topic-docs/groups.yml`, or chapter references.

First seen Jun 18, 2026

Installation

$ npx skills add fixmyberlin/tilda-geo --skill topic-docs-yaml-authoring

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from fixmyberlin/tilda-geo.

npx skills add fixmyberlin/tilda-geo

Browse all from fixmyberlin/tilda-geo

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 24
License LICENSE.md
Default branch develop
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,519 B
  • docs SUMMARY.md 235 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Topic-Docs YAML Authoring

Use this skill when adding or editing topic-docs YAML.

Primary reference

  • Read topic-docs/README.md first.

Source of truth for edge cases

If anything is unclear or conflicting, follow code validation/build behavior in:

  • app/src/data/topicDocs/schema.ts
  • app/scripts/topic-docs-build/attributeResolution.ts

Authoring workflow

  1. Identify the target table file in topic-docs/<topic>/<tableName>.yaml.
  2. Apply the field and combination rules from topic-docs/README.md.
  3. For ref and valuesRef, ensure pointers use <tableName>.<attributeKey> and targets exist.
  4. Keep docs human-readable (label/description) unless format: ignore is intentional.
  5. Verify changes from app/:

- bun run topic-docs-build - Optional: bun run topic-docs-coverage-check -- --table <tableName>

Required checks

  • No invalid combinations (ref with values, valuesRef with values, etc.).
  • valuesAdd only used with ref or valuesRef.
  • format: ignore does not define values.
  • Chapter references point to real chapter IDs.

Output expectations

  • Keep YAML minimal and explicit.
  • Prefer reuse (ref/valuesRef) over copy-pasting large repeated enums.