anthonykgross/akg

A Claude Code plugin that sets up Claude Code on a project from an optional **team config**, by asking a few questions about the project, then keeps it in sync with the team.
- **Scans first**: manifests, README, CI, tests and recent commits — stack, test/lint/build commands, monorepo sub-projects.
- **Shows what it understood**: purpose, key folders, architecture, integrations — and lets you add what matters ("edge functions are in supabase/functions", "we do DDD"). It lands in a Project context section of CLAUDE.md you own.
- **Asks every question, pre-filled**: project type, Definition of Done, TDD, review level, Claude autonomy (several picks), dependencies, where commands run (host or container), local tools and shortcuts, architecture, secrets, ticket tracker by default; deployment, branching, tests, migrations, docs… on demand; plus your team's. Asked as an interview, in plain text: answer 1 is akg's guess with its evidence (team, project or scan), the other options are numbered after it. Type "ok", a number, or your own words; a recap of every answer comes before anything is written.
- **Generates**: CLAUDE.md (one per sub-project in a monorepo), .claude/settings.json (permissions from your answers, with ask on install commands and on destructive commands of detected tools such as terraform apply), and the plugins to enable.
- **Speaks your language**: questions are asked in the language of the conversation; generated files stay in English unless you choose otherwise.
- **Never imposes**: every file is shown before it is written; every value, setting and plugin is a proposal. Local choices always win over the team's.
Install
Usage
| Command | When |
|---|---|
| /akg:setup | Once per project: link the team config (or none), confirm what was detected and understood, answer the pre-filled questions, review the generated files. |
| /akg:source-init | Once per team, in an empty folder: creates the team source (a dedicated repo, no code) — team conventions, then a plugin marketplace from your installed plugins, official Anthropic plugins fitting the team's stacks, and skills copied from existing projects. |
| /akg:team | Anytime: shows the team's instructions (team.md: onboarding, tools to install, rules). Display only. |
| /akg:pull | When the team config changes: applies team updates, shows conflicts with your local overrides ("team says X, project says Y"), proposes new questions and plugins. |
Tip: turn on **Prompt suggestions** in /config (or "promptSuggestionEnabled": true in your settings) to often get the answer ("1", "ok") as a grey suggestion: Tab to accept, Enter to send. Claude Code generates it, so akg can't guarantee its content.
When the project extends a team config, a new session shows one line when the team has a new version:
It is shown once per team version, stays silent when offline, and never slows the session down (~2 s budget).
Files
akg reads and writes the same files in the project and in the team repo:
Three layers, the closest to the project wins: **akg defaults → team → project**.
Project config.yaml
Only what differs from the team:
extends accepts github:owner/repo, a git URL, an HTTPS URL to a single config.yaml, or a local path. Add # (or a tag or commit) to a repo or local git directory to follow something other than the default branch: github:acme/claude-team#develop. Private repos use your git credentials; private single files are not supported.