القائمة
Maintain TheOneKit repos as a kit maintainer. Use for releasing kits, scaffolding new kits, cross-kit validation, schema migration, and E2E test runs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Asset Hunter Pro — unused asset detection, dependency graph, duplicate finder, project cleanup automation for Unity
Practical tools and validation methods for game balance — DPS calculators, EHP formulas, spreadsheet layouts, stat audits, difficulty spike detection
GDD structure, templates, and living documentation patterns for game projects — wiki pages, design docs, section layout, sync triggers
Game feel and juice — screen shake, hit stop, particles, animation curves, input responsiveness, feedback timing. Makes actions feel satisfying.
Mobile game design patterns — session design, retention mechanics, notification strategy, portrait/landscape, battery/thermal constraints, FTUE
Create or update TheOneKit agent .md files with canonical structure. Use when adding a new agent, updating maxTurns/model, or fixing frontmatter fields.
| 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. |
| version | 1.0.0 |
| argument-hint | <subcommand> [options] |
| effort | medium |
| origin | theonekit-core |
| repository | The1Studio/theonekit-core |
| module | null |
| protected | true |
Unified kit maintenance skill. All subcommands are for kit maintainers only, not end-users.
| 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 |
/t1k:kit validate # Validate current kit repo
/t1k:kit validate --cross-kit # Validate across all installed kits
/t1k:kit release # Guided release workflow
/t1k:kit sync --pull # Pull and check all kits
/t1k:kit scaffold theonekit-x # Scaffold new kit
/t1k:kit audit --all # Audit all kit repos
/t1k:kit migrate --dry-run # Preview schema migration
/t1k:kit test --all # E2E test all kits
/t1k:kit test --kit unity # E2E test specific kit
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 planorigin, repository, module, protected fields are CI/CD-injected by release action, not authored in source. See /t1k:doctor gotchas.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"]version or buildDate in source metadata.json — CI generates these from package.json. Source should only contain manually-maintained fields (name, repository, deletions).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