aosp-internal-book: Skill for Claude Code

Book Writer

Write source-code-referenced technical books in Markdown with Mermaid diagrams, served as a ProperDocs website. Covers chapter structure, content flow, diagram syntax, and keeping the ProperDocs site in sync with content changes.

ProperDocs Site Maintenance

The book is served via ProperDocs (a MkDocs fork) with the Material theme. When chapter content changes, the site configuration must stay in sync. Forgetting this breaks navigation or hides new chapters from readers.

When you add a new chapter

1. Create NN-slug.md with the chapter template below
2. Add a nav entry to properdocs.yml in the correct Part section:

   - "N. Chapter Title": NN-slug.md
   

3. Create a symlink in docs/:

   ln -sf "../NN-slug.md" "docs/NN-slug.md"
   

4. Add a chapter entry to llms.txt in the correct Part section, in chapter order:

   - [Chapter N: Title](https://aospbooks.github.io/aosp-internal-book/NN-slug/): one-line description of what the chapter covers
   

5. If the chapter number changes existing chapters, renumber the affected properdocs.yml entries and llms.txt URLs too
6. Add a row to the chapter table in README.md and update the chapter counts (CLAUDE.md rule 13)

When you remove a chapter

1. Delete the .md file
2. Remove its entry from properdocs.yml nav
3. Remove the symlink from docs/
4. Remove the matching llms.txt entry
5. Renumber subsequent chapters if needed (in filenames, properdocs.yml, llms.txt, and section headings inside the files)
6. Remove the row from the chapter table in README.md and update the chapter counts

When you rename or reorder chapters

1. Rename the .md file
2. Update the properdocs.yml nav entry (both the label and the filename)
3. Update the docs/ symlink
4. Update the llms.txt entry (label, URL slug, and the one-line description if scope changed)
5. Update all ## N.x section headings inside the file to match the new chapter number
6. Update the row in the chapter table in README.md