Team Onboarding & Context Injection FAQs

Question 1

How does the onboarding skill determine which cards to show?

Accepted Answer

The skill parses your role argument and matches it against keywords in the 'tags' field of your markdown cards stored in .claude/memory/cards/. It also prioritizes cards marked with high importance or the 'onboarding' type.

Question 2

Can I use this for non-technical roles like PMs or Designers?

Accepted Answer

Yes, the skill includes pre-defined mappings for PMs (process, requirements) and Designers (UI/UX, accessibility) to ensure they receive relevant high-level context.

Question 3

Does it display sensitive or private information?

Accepted Answer

The skill is programmed to automatically skip any cards with 'visibility: private' set in their metadata to ensure only team-appropriate onboarding material is shared.

Question 4

What happens if a new project has no onboarding cards yet?

Accepted Answer

If no cards are found, the skill will suggest creating your first card using the /session-memory:card command or offer to auto-generate starter cards based on your current project structure.

Question 5

Where are the knowledge cards stored?

Accepted Answer

All knowledge cards are stored as standard markdown files within your repository's .claude/memory/cards/ directory, allowing them to be versioned and shared via Git.

Team Onboarding & Context Injection

Key Features

Use Cases

Team Onboarding & Context Injection

Key Features

Use Cases