Team Onboarding

This page turns adoption into an execution checklist.

1. Decide the onboarding goal

Before you adopt the project, answer three questions:

1. Are you building a shared prompting baseline or a broader engineering knowledge layer?
2. Do you need a fast pilot or a maintainable long-term system?
3. Do you mainly need rule samples, or do you need a public-facing project shell that demonstrates maturity?

2. Pick the right entry surface

• Pilot evaluation: start with the Project Mission and Composition Patterns
• Team rollout: start with the Academy Path and Best Practices
• Repository maintenance: start with the Maintainer Curriculum and Rule Template Guide

3. Define a minimal baseline

Use a three-part starting set:

• one general rule
• one primary-stack rule
• one governance rule from security, data, or platform

That is enough to create a team baseline without front-loading too much complexity.

4. Revisit the evidence and research layers

After the first adoption cycle, come back to:

• Research References
• Rules Index