vawe-docs

Routes documentation questions to the single doc that answers them in the Vawe repository.

3|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Vandit1604/vawe --skill vawe-docs-vandit1604
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vawe-docs
Source: https://github.com/Vandit1604/vawe/tree/main/skills/vawe-docs
Command: npx skills add https://github.com/Vandit1604/vawe --skill vawe-docs-vandit1604

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The Vawe repository contains over a hundred doctrine, craft, and rules documents, and finding the right one means either reading many files or guessing. This Skill provides a generated index that maps every document to the question it answers, so you open exactly one doc instead of scanning the corpus. ## Core Features & Use Cases - Question-to-document routing: Each entry states when to reach for a doc and what it answers, covering film structure, story beats, transitions, typography, colour, layout, imagery, sound, subagent cost, approval stops, recreation, QA gates, and engine architecture. - Drift-free index: Generated from the frontmatter on every doc via make doc-index, so the map cannot diverge from what is on disk. - Use Case: Before authoring a scene JSON you need to know which easing belongs on an exit. Instead of browsing engine-doctrine, you consult the index, find RULES/ease-direction.md, and read only that file. ## Quick Start Ask which document in this repo settles your question about authoring, judging, or changing a Vawe video, then open only the doc the index points to.

Frequently Asked Questions about vawe-docs

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

FAQPage Schema
How do I find the right documentation file in a large repo?

Use the generated index in this Skill: every document is listed with when to reach for it and what it answers. Read the one-line entry, then open only that doc instead of scanning the whole corpus.

What topics does the Vawe engine-doctrine documentation cover?

It covers film structure, story beats, transitions, typography, colour, layout, imagery, density, sound, subagent cost, approval stops, recreation, QA gates, engine architecture, and a mistake log, organized as craft, rules, research, and reference docs.

How is the vawe-docs index kept in sync with the docs?

The index is generated by running make doc-index, which builds the map from the frontmatter on every document. Because it is generated rather than hand-written, it cannot drift from what is on disk, and it should never be edited manually.

When should I use this Skill instead of reading CLAUDE.md?

Start at CLAUDE.md for the standing rules and the render loop. Use this Skill when CLAUDE.md cannot answer your question directly and you need to know which specific doctrine, craft, or rules document settles it.

Does this Skill contain the actual documentation content?

No. It contains only a routing index of one-line entries pointing to documents elsewhere in the repo. You open the referenced file yourself, so no document body is loaded into context unless you ask for it.