# Practical references

Use these references to resume a specific task. They keep the main chapters readable while preserving exact recovery and record formats.

| Reference | Use when |
| --- | --- |
| [A. Terminal and OS notes](a-terminal-and-os.md) | A path, shell, executable, or platform difference interrupts work |
| [B. Git recovery](b-git-recovery.md) | You need to preserve work while changing staging, working content, or history |
| [C. Markdown and YAML](c-markdown-yaml.md) | A document, link, code fence, or skill header is malformed |
| [D. Task-brief patterns](d-task-briefs.md) | A request needs a clear boundary and observable result |
| [E. Project records](e-project-records.md) | You need requirements, sources, decisions, tests, or a handoff |
| [F. Instructions and skills](f-instructions-skills.md) | A repeatable procedure needs a focused package and behavior checks |
| [G. Versions and checkpoints](g-versions-and-checkpoints.md) | You need the supported starting state and applicable commands |
| [H. Troubleshooting](h-troubleshooting.md) | You need to classify a failure before choosing a remedy |
| [I. Sources, rights, and errata](i-sources-rights-errata.md) | A claim, asset, or correction needs a traceable record |
| [Glossary](glossary.md) | A term needs a short practical definition |

Examples marked illustrative are original instructional material. Commands require the stated execution context. Record the output of your own run rather than copying an expected result into an evidence field.