Pattern

Use this skill for reusable project patterns that need evidence and a runnable teaching example. Before product-source changes, check the patterns owned by the project and follow every applicable one.

1. Inspect the relevant pattern children and their documented checks.
2. Apply an active pattern when its situation and boundary fit.
3. Create a candidate only when a real source case, transferable relation, and runnable example exist.
4. Keep code, checks, status, and teaching material in agreement.

Read the detailed guide for qualification, approval boundaries, or work under patterns/. Tests, scripts, configuration, migrations, generated code, and docs examples stay outside the product-source gate.