Cycles
Design · c30

Tour Guide

archivedcreated 2026-03-19· last activity 2026-09-11

Per-project tour guide command for orienting newcomers interactively

Why

Each Qpoint project has a CLAUDE.md optimized for AI instructions — it documents the what and how but skips the why. New users (human or AI in a fresh conversation) have no guided entry point that explains a project's purpose, founding principles, ecosystem context, or common workflows in a conversational way.

Objective

Create a canonical /tour command and the design project's TOUR.md, establishing the pattern for rollout to sister projects.

Scope

  • design/.claude/commands/tour.md — canonical command template
  • design/TOUR.md — narrative content for the design project tour
  • cycles/c30.tour-guide/CYCLE.md — this file
  • cycles/CYCLES.md — active cycle entry

Key Changes

  • Created canonical tour command at .claude/commands/tour.md (command, not agent — tour is always user-initiated via /tour)
  • Created TOUR.md with 6 sections: Purpose & Founding Principles, Ecosystem Context, Key Concepts, Common Tasks, History & Evolution
  • Command reads both TOUR.md (narrative why) and CLAUDE.md (technical what/how), synthesizes into conversational walkthrough
  • Supports full tour (/tour) and targeted stops (/tour <topic>)
  • Originally scaffolded as an agent — pivoted to command because the tour guide is always user-initiated, unlike cycle-manager which Claude spawns internally

Outcome

Canonical /tour command and design project TOUR.md established. Command lives in .claude/commands/ (not agents) since it's user-invoked. Ready for rollout to sister projects in future cycles.

Artifacts

  • initial-prompt.md
  • initial-prompt.md

Qpoint Brand Style Guide