- Skills
- 20
- 仓库
- 1
- 职业覆盖
- 2
- 场景覆盖
- 3
- Stars
- ★ 0
JAuto-Corp 的 Skills 20
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
workflow/skill
Patterns for adding or editing a skill — frontmatter contract, router + sub-file split, line budgets.
workflow
Meta-skill for editing the framework itself — skills, hooks, commands, rules, CLAUDE.md. Use before changing anything under .claude/ or the routing docs, so the change keeps the system's shape (lazy-load, forge markers, hook auto-discovery, harness).
work
Work lifecycle orchestration: start, continue, pause, handoff, done, plus epic/sprint planning. Context gathering + goal-focused state-chain transitions.
verify
Verification and auditing. Validate acceptance scenarios, run multi-perspective audits, check type-check/build evidence, and gate phase/sprint completion.
team-lead
Coordinate an Agent Team for parallelizable work — implementation, audit, research, or testing. Teaches the mechanical constraints (WAIT pattern, file ownership, model tiers) and lets you design the team. For orchestration_tier=cluster / multi-agent runs.
scope
Plan and design work before building. Invoke when starting an epic, scoping a sprint, or planning any Standard+ change: orient on what exists, equip the planning procedure + domain skills, then produce the SPEC/SCENARIOS/PROGRESS structure and converge it through an audit loop. Feeds /work:epic-plan and the ATDD entry gate.
patterns
Shared workflow patterns referenced across orchestrator skills — multi-explorer deployment, the discovery/friction signal vocabulary, the outcome interview, and state-chain file formats. Load on-demand when a skill points to a section.
e2e
End-to-end / acceptance testing orchestration. Run the project's configured e2e suite against a phase's acceptance scenarios, pick an execution mode (suite / conductor / direct / data-layer), and capture the per-scenario passing evidence the ATDD gate and stop check 03 require.
check
Orchestrate verification ACROSS a chain of work — the multi-round, multi-tier audit loop that drives findings to zero. Distinct from /verify:complete (one phase's exit gate): /check escalates verify:* tiers and relays remediation to /work until a sprint/epic/change converges clean. Invoke to converge-verify a body of work, not to gate a single phase.
chain
Convergence-state model for multi-round orchestration loops. Defines context/CHAIN.json — the baton /scope (plan-converge) and /check (verify-converge) pass between rounds: progress metric, tier-ladder climb, stall detection, exit + escalation rules. A reference, not an executor.
capture
Turn signals surfaced during work into tracked issues. Park discoveries and keep moving; convert audit/session findings to issues; block, triage, and roll up into epics — the human side of the self-improvement loop.
caveman
Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
caveman
Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".
copier-conflict-fixture
framework version two
copier-conflict-fixture
framework version two
copier-conflict-fixture
framework version one