Ask Gabriel

The map of this pack. Recommend the next skill, or point to the journey that shows the whole path. Stay thin: load another skill's body only after the path is chosen.

Read when

• Nothing up front. Keep the rules in code-quality.md and code-structure.md out of this router: they already apply, and the next skill loads them.
• About to reply? Open the Plain language and Unslop sections of writing-style.md. Skip them and the recommendation reads like pack jargon.
• Unsure what the whole path looks like? Open the matching journey below. Skip it and you take the first step right and the third one wrong.

Journeys

Each journey follows one piece of work through the skills and rules, step by step, with the rule opened at each moment and the next move. They share one example domain (billing) and chain into each other. Their path and shapes beat the app's existing code, which is usually messy. An app sibling is copied only when it matches an example (cite a sibling).