Documentation Index
Fetch the complete documentation index at: https://panopticon-cli.com/llms.txt
Use this file to discover all available pages before exploring further.
Meta Repos
A meta repo is a special repository that contains shared skills, architecture documentation, team conventions, and onboarding materials for a project. In progressive polyrepo setups, the meta repo is the single source of truth for agent configuration and team onboarding.What a Meta Repo Contains
Directory Structure
.agent-template/
This directory is copied into every workspace created for the project. It contains:
| Path | Purpose |
|---|---|
.claude/CLAUDE.md | Project-specific AI instructions |
.claude/skills/ | Team-specific skills available to agents |
.claude/commands/ | Team-specific commands |
.claude/agents/ | Custom agent definitions |
panopticon/repo-groups.yaml
Defines named groups of repositories for progressive workspace creation:
docs/
Architecture and reference documentation:
| File | Purpose |
|---|---|
repo-map.md | What each repo does, dependencies, common change patterns |
architecture.md | System architecture overview |
onboarding/checklist.md | Prerequisites checklist for new team members |
onboarding/machine-setup.sh | Automated setup script |
onboarding/README.md | Getting started guide |
Creating a Meta Repo
Via Setup Wizard
The setup wizard (pan setup) creates a meta repo as part of progressive polyrepo project setup:
Via Setup Agent
The Setup Agent generates meta repo contents automatically:- Explores all repositories in the project
- Detects conventions, patterns, and dependencies
- Generates CLAUDE.md with only non-obvious project-specific rules
- Generates repo-map.md documenting each repo’s purpose
- Generates repo-groups.yaml with logical groupings
- Generates onboarding checklist with prerequisites
Manual Creation
Create the directory structure manually:Onboarding Flow
When a new team member joins:-
Clone the meta repo
-
Run the machine setup script
This installs prerequisites, authenticates CLI tools, and clones repositories.
-
Run
pan setupThe wizard detects existing repos and applies your team’s template with pre-configured settings. -
Ready to work
Updating the Meta Repo
When team conventions change:- Update the meta repo (normal git workflow)
- Changes propagate when agents sync skills:
.agent-template/ contents when:
- A new workspace is created
pan syncis run- The Setup Agent runs and regenerates files
Meta Repo Best Practices
What to Include in CLAUDE.md
Focus on non-obvious conventions only. Don’t document:- How to run
npm install,git commit, etc. (LLMs know these) - Standard industry practices
- Deviations from defaults — “PRs target
qanotmain” - Per-repo quirks — “Each Lambda has its own package.json, no root one”
- Breaking behaviors — “Never run
terraform applywithout approval” - Architecture patterns — “API gateway handles auth, microservices don’t”
What to Include in Repo Map
For each repo, document:- Purpose — What the repo does
- Dependencies — What it depends on, what depends on it
- Common change patterns — “Changes here usually need corresponding changes in api-service”
- Key files — Where to start looking
Machine Setup Script
Generated by the Setup Agent based on detected prerequisites:Related Guides
- Progressive Polyrepo — Progressive workspace configuration
- Setup Wizard — Interactive project setup
- Projects — Project registry and configuration