tour-authoring

Create and validate repo-native diagram tours and fixtures with stable IDs.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/h-4vok/diagram-tours --skill tour-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tour-authoring
Source: https://github.com/h-4vok/diagram-tours/tree/main/.agents/skills/tour-authoring
Command: npx skills add https://github.com/h-4vok/diagram-tours --skill tour-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the challenge of creating and validating repo-native diagram tours and fixtures that conform to project conventions.

Core Features & Use Cases

  • Author tours that match the repo's real contract, not generic YAML styles.
  • Validate common pitfalls like missing root fields, empty steps, invalid focus IDs, and broken references.
  • Work alongside docs and fixtures to maintain consistent tour content next to diagrams.

Quick Start

Run the tour-authoring workflow in the repository to create or review *.tour.yaml files and fixtures.

Frequently Asked Questions about tour-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and validate repo-native diagram tours in YAML?

To create diagram tours, author *.tour.yaml files and validate them against project conventions to ensure stable IDs, proper focus references, and correct root fields. This prevents common pitfalls like empty steps and broken references.

What is a diagram tour and how does it work with Mermaid examples?

A diagram tour is a structured walkthrough of Mermaid examples stored as *.tour.yaml files next to their diagrams. It works by guiding content structure and validating focus references to maintain consistent documentation alongside visual fixtures.

How do I validate broken focus references and missing root fields in tour YAML files?

You validate broken focus references and missing root fields in tour YAML files by running validation commands that check for common pitfalls. This ensures stable IDs and proper focus references conform to documented project conventions.

Can I use tour-authoring to manage test fixtures located next to Mermaid diagrams?

Yes, you can manage test fixtures located next to Mermaid diagrams. The workflow guides content structure for *.tour.yaml files and fixtures, ensuring they conform to the repository's real contract and documented conventions.

What is the best way to author YAML tour files that match project conventions instead of generic styles?

The best way to author YAML tour files matching project conventions is to use a validation workflow that checks for empty steps and invalid focus IDs. This ensures tours match the repo's real contract rather than generic YAML styles.

Why does my tour YAML validation fail on empty steps and invalid focus IDs?

Tour YAML validation fails on empty steps and invalid focus IDs when files do not conform to documented project conventions. Running preview and validation commands identifies these common pitfalls and verifies proper focus references.