Shared AI development template for all uniiverse organization repositories
This repository provides a standardized template system that bootstraps AI-assisted development capabilities across all uniiverse repositories. It ensures Claude behaves consistently, provides reusable skills, and maintains organization-wide coding standards.
From any uniiverse repository:
curl -sSL https://raw.githubusercontent.com/uniiverse/master-claude/main/scripts/bootstrap-repo.sh | bashThis will:
- Create
.claude/directory with skills, agents, and commands - Add
CLAUDE.mdwith uniiverse coding standards - Create
CLAUDE.local.mdfor repository-specific customization - Initialize version tracking
# Update your repository with latest template changes
.claude/commands/sync.shA comprehensive CLAUDE.md that defines:
- Code quality guidelines
- Security requirements
- Performance expectations
- Documentation standards
- Testing practices
Pre-built capabilities like:
- code-review: Comprehensive code reviews
- security-scan: Vulnerability assessment
- test-generator: Generate test cases
- architecture-review: System design review
- performance-profile: Performance analysis
Invoke with: claude /skill-name or by description
Purpose-built agents for:
- security-auditor: Security-focused analysis
- tech-lead: Architecture guidance
- code-archaeologist: Legacy code exploration
- performance-expert: Optimization recommendations
Uniiverse-specific commands:
/bootstrap: Initialize template in repo/sync-master: Update from master-claude/validate-template: Check template integrity/uniiverse-review: Full standards compliance review
your-repo/
├── CLAUDE.md # Core AI instructions (synced from master)
├── CLAUDE.local.md # Your customizations
└── .claude/
├── skills/ # Shared skills (symlinked)
├── agents/ # Shared agents (symlinked)
├── commands/ # CLI commands (symlinked)
├── config/
│ ├── hooks.yaml
│ └── settings.yaml
└── master/ # Git submodule to master-claude
Edit CLAUDE.local.md to add repository-specific preferences:
# My Repository Customizations
## Tech Stack
- Python 3.11+ with FastAPI
- PostgreSQL 15
- Redis for caching
## Preferences
- Use async/await for all I/O operations
- Prefer Pydantic models over dataclasses
- All API endpoints must have OpenAPI documentation
## Team Conventions
- Sprint planning on Mondays
- Code freeze on Thursdays
- Deploy to staging happens automatically on merge to `develop`Create repository-specific skills in .claude/skills/custom/:
mkdir -p .claude/skills/custom/my-skill
cat > .claude/skills/custom/my-skill/skill.yaml <<EOF
name: my-custom-skill
version: 1.0.0
description: Does something specific to this repo
trigger_patterns:
- "do the thing"
EOFTrack your template version:
# Check current version
cat .claude/template-version.yaml
# Update to latest
.claude/commands/sync.sh
# Pin to specific version
echo "1.2.3" > .claude/.template-version-pinInstructions are applied in this order (highest priority first):
- ~/.claude/CLAUDE.local.md - Your personal preferences
- CLAUDE.local.md - Repository-specific instructions
- CLAUDE.md - Core uniiverse standards (synced from master)
- Master Template - The source template
The template uses git submodules to share content:
# Your repo references master-claude
.claude/master/ -> git submodule
# Core files are symlinked
CLAUDE.md -> .claude/master/templates/CLAUDE.md
.claude/skills -> .claude/master/templates/.claude/skills
.claude/agents -> .claude/master/templates/.claude/agentsUpdates propagate automatically when you sync.
- Fork master-claude
- Create feature branch
- Add/modify templates
- Test in pilot repository
- Submit PR with examples
- Documentation: Full Specification
- Issues: GitHub Issues
- Chat: #ai-tooling on Slack
- Owner: Engineering Enablement Team
- Core specification
- Bootstrap script
- Essential skills (code-review, security-scan)
- Specialized agents
- GitHub Actions for auto-sync
- Pilot with 5 repositories
- Organization-wide rollout
Internal use only - Uniiverse Organization
Version: 1.0.0 Last Updated: 2026-02-12 Maintainer: Engineering Enablement Team