April 2026 | 3 days | Multiple teams
A shared project template for AI project teams using Claude Code. Clone it, run the setup wizard, and get a consistent foundation for coordinating work across your team.
# 1. Clone into your team's repo
git clone https://github.com/percona-lab/ai-project-template my-project
cd my-project
rm -rf .git && git init
# 2. Run the interactive setup wizard
claude /setup
# 3. Commit and push
git remote add origin git@github.com:percona-lab/your-team-repo.git
git push -u origin main
# 4. Start building
claudeThe /setup command walks you through filling in all the template files interactively.
| File | Purpose |
|---|---|
VECTOR.md |
Start here. Project direction: what you're building, why, scope, demo story. |
CLAUDE.md |
Project config for Claude Code. Tech stack, conventions, constraints. |
ARCHITECTURE.md |
Technical architecture. Components, integration points, decisions. |
.claude/agents/reviewer.md |
Critical reviewer agent. Gut-checks decisions, flags over-engineering. |
.claude/commands/setup.md |
Interactive setup wizard. Run with /setup. |
.claude/commands/status.md |
Daily status check. Run with /status. |
.claude/commands/demo-prep.md |
Day 3 demo prep. Run with /demo-prep. |
Every Claude Code session loads these automatically:
VECTOR.md -- Why are we building this? What's the demo?
|
CLAUDE.md -- How do we work? Stack, conventions, constraints.
|
ARCHITECTURE.md -- How is it structured? Components, data flow, decisions.
| Command | When to Use |
|---|---|
/setup |
Day 0: Fill in all template files interactively |
/status |
Daily: Generate a status update for your workstream |
/demo-prep |
Day 3: Generate demo script and pre-flight checklist |
claude --agent reviewer |
Anytime: Get a critical second opinion on a decision |
When you want someone to push back on your approach:
claude --agent reviewer "Should we use internal triggers or binlog replay for change tracking?"
claude --agent reviewer "Review ARCHITECTURE.md for over-engineering"It will challenge assumptions, propose simpler alternatives, and keep you focused on what ships by Day 3.
- Fill in VECTOR.md first. Everything else follows from the project direction.
- Keep CLAUDE.md under 80 lines. Claude Code has an attention budget. Be concise.
- Update ARCHITECTURE.md as you go. Log decisions so the next session stays aligned.
- Use
/statusat the start of each day. Catch blockers early. - Run
/demo-prepon Day 3 morning. Don't wing the demo.
| Project | Focus | Tech |
|---|---|---|
| Native pt-online-schema-change | Build pt-osc directly into Percona Server | C/C++, InnoDB internals |
| MTR History with UI | Track MTR test history with regression/flaky detection | Python (FastAPI), React, SQLite |
| Automated Jira Ticket Fixes | AI-assisted end-to-end Jira ticket fix pipeline | Python, Claude Code, Jira/GitHub APIs |
Template structure adapted from open-source project scaffolding patterns. Reviewer agent inspired by extractum-skills.
MIT