| name | t1k:kit |
| description | Maintain TheOneKit repos as a kit maintainer. Use for releasing kits, scaffolding new kits, cross-kit validation, schema migration, and E2E test runs. |
| keywords | ["maintainer","release","scaffold","validate","audit","migrate","kit"] |
| version | 1.0.0 |
| argument-hint | <subcommand> [options] |
| effort | medium |
| origin | theonekit-core |
| repository | The1Studio/theonekit-core |
| module | null |
| protected | true |
TheOneKit Kit — Maintainer Toolkit
Unified kit maintenance skill. All subcommands are for kit maintainers only, not end-users.
Subcommands
| Subcommand | Usage | Purpose |
|---|
validate | /t1k:kit validate [--cross-kit] | Schema, activation paths, keyword conflicts, preset refs, naming |
release | /t1k:kit release [--skip-validate] | Guided release: validate → CI gate → GitHub release → Discord |
sync | /t1k:kit sync [--pull] [--status-only] | Pull all kits, check version compat, release-action alignment |
scaffold | /t1k:kit scaffold <name> [--org] | Create new kit repo from template with full boilerplate |
audit | /t1k:kit audit [--all] | Health audit: file counts, modules, keywords, CI, freshness |
migrate | /t1k:kit migrate [--dry-run] | Schema migration (e.g., registryVersion 1→2) |
test | /t1k:kit test [--all] [--kit <name>] | Comprehensive 15-phase E2E testing: install, modules, CLI, release infra |
Quick Reference
/t1k:kit validate
/t1k:kit validate --cross-kit
/t1k:kit release
/t1k:kit sync --pull
/t1k:kit scaffold theonekit-x
/t1k:kit audit --all
/t1k:kit migrate --dry-run
/t1k:kit test --all
/t1k:kit test --kit unity
Subcommand Details
Read the reference file for full details on each subcommand:
references/validate.md — per-kit and cross-kit validation checksreferences/release.md — release workflow steps and gatesreferences/sync.md — cross-kit synchronization protocolreferences/scaffold.md — new kit scaffolding templatereferences/audit.md — health audit checks and scoringreferences/migrate.md — schema migration stepsreferences/test.md — 12-phase E2E test plan
Gotchas
- Do not add origin metadata to source —
origin, repository, module, protected fields are CI/CD-injected by release action, not authored in source. See /t1k:doctor gotchas.
- Modular kits use
release-modules.cjs (custom release script), NOT semantic-release directly. Flat kits (e.g., theonekit-rn) still use semantic-release. release-modules.cjs produces per-module ZIPs + manifest.json index.
t1k-modules.json is GENERATED for the modules section — do not hand-author it. Source of truth is each module.json. Only presets in t1k-modules.json are hand-authored..releaserc.json MUST include package.json and .claude/metadata.json in @semantic-release/git assets — without this, package.json stays at 0.0.0 forever. Every kit repo needs: "assets": ["package.json", "CHANGELOG.md", ".claude/metadata.json"]- Do not hardcode
version or buildDate in source metadata.json — CI generates these from package.json. Source should only contain manually-maintained fields (name, repository, deletions).
Future: Self-Improving AI Pipeline
T1K vision: the kit should self-teach and improve using aggregated consumer data. Planned pipeline:
- User errors collected via telemetry → D1 (already exists)
- Scheduled AI agent (cron) queries D1 for error clusters (same fingerprint, 3+ occurrences, multiple users)
- AI aggregates patterns → synthesizes root cause, workaround, prevention
- Auto-generates gotcha entries for relevant skill SKILL.md files
- Opens PR to kit repo automatically
- Maintainer reviews and merges → next release distributes to ALL users
Status: Not yet implemented. See CLAUDE.md "Self-Improving AI Vision" for context.
Auto-Activation Keywords
Triggers on: kit validate, kit release, kit sync, kit scaffold, kit audit, kit migrate, kit test, kit health, kit status, cross-kit, maintainer, test kit, test install, test modules, e2e kit, validate installation, self-improving, auto-gotcha, gotcha generation, ai aggregation, learn from users
