메뉴
Autonomous Claude Code task runner — write task specs as Markdown files, run claskit, and Claude implements them one by one. Use when setting up claskit in a project, writing task specs, scheduling autonomous runs, or understanding the todo/done task lifecycle.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Scaffold, revise and manage custom ACF Gutenberg blocks for WordPress with Tailwind CSS. Use when the user wants to create a new block, revise/audit blocks, or set up a WordPress blocks project.
Scaffold one or more ACF Gutenberg blocks from GitHub issues, a markdown brief, or interactive prompts. Generates block.json, fields.json, render.php, and optional view.js.
Discuss a new block's purpose and requirements with the user, then create a GitHub issue with a structured breakdown ready for /wp-acf-blocks:add-block.
Deep AI audit of all blocks or specific blocks — runs structural checks first, then uses AI to review content quality, descriptions, grammar, admin render justification, wrapper usage, and empty-state messages.
Fast structural audit of all blocks or specific blocks — checks required files, wrapper attributes, fields.json timestamp, previewImage, viewScript. No AI, runs instantly via script.
Set up a new WordPress theme with the wp-acf-blocks block development workflow
| name | claskit |
| description | Autonomous Claude Code task runner — write task specs as Markdown files, run claskit, and Claude implements them one by one. Use when setting up claskit in a project, writing task specs, scheduling autonomous runs, or understanding the todo/done task lifecycle. |
| when_to_use | - User wants to set up claskit in a project - User wants to write a task spec / plan file for claskit - User asks how claskit works or what commands are available - User wants to run tasks now or schedule them - User asks about the .claude/tasks/ folder structure |
| allowed-tools | ["Read","Edit","Write","Bash"] |
Repo: https://github.com/phucbm/claskit
npm: npx claskit or npm i -g claskit
claskit reads Markdown task specs from .claude/tasks/todo/, launches Claude with --dangerously-skip-permissions, and lets Claude implement them autonomously. On success each spec moves to .claude/tasks/done/.
npx claskit --init
Creates:
.claude/tasks/
todo/ ← drop task specs here
done/ ← claskit moves completed specs here
README.md
npx claskit # interactive menu (now / schedule)
npx claskit --now # skip menu, run immediately
Interactive flow — schedule path:
When a user wants to create a claskit spec from a conversation (brainstorm, plan, feature description):
/claskit skill — it reads the current conversation context and writes .claude/tasks/todo/<slug>.md directlyThe /claskit skill handles: slug generation, folder creation, and correct file format. Prefer it over writing specs manually.
# Feature Title
## Task
What to implement — be specific.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Files Affected
- src/foo.ts
## Notes
Dependencies, order hints, constraints.
Save as .claude/tasks/todo/my-feature.md.
| Command | What it does |
|---|---|
npx claskit | Interactive menu |
npx claskit --init | Initialize .claude/tasks/ structure |
npx claskit --now | Run immediately, skip menu |
npx claskit --test | Create 2 sample tasks to try claskit |
npx claskit --clean-test | Remove sample tasks and output |
.md files.md from todo/ → done/ on successclaude) installed and authenticated--dangerously-skip-permissions — only use in trusted, backed-up projectscaffeinate during scheduled countdown to prevent sleeptodo/ are read-only — claskit (not you) moves them to done/