القائمة
Use when you have a design or requirements and need to create tickets (epics/tasks) for implementation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automated performance optimization loop. Generates large benchmark workloads with vole-stress, profiles with perf, identifies hotspots in our code, fixes them, verifies improvement, repeats.
Automated bug-hunting loop using vole-stress + vole-reduce. Generates random codebases, tests them, reduces failures, fixes bugs, verifies, and repeats.
Use when adding new diagnostic error codes to the compiler
Use when you are asked to implement tickets (tasks/epics) created in `tk`
Incremental Rust code quality loop. Scans the compiler codebase for one refactoring opportunity per round — duplicated logic, poor factoring, mechanical lint fixes — applies it, verifies, and repeats.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
| name | create-tickets |
| description | Use when you have a design or requirements and need to create tickets (epics/tasks) for implementation |
Convert designs into tickets. Verify tk is installed first or STOP.
Multi-task features: Epic + child tasks
tk create "EPIC: Feature Name" -d "Goal and design summary"
tk create "Task 1" --parent <epic-id> -d "What to do, files to touch"
Small features: Standalone tasks
tk create "Task title" -d "Description"
Goal: What this accomplishes Files: exact/paths/here Steps (example):
tk dep tree {epic-id} # Show tasks
Ask the user if they wish to implement the epic or task, if so
use the implement-tickets skill with a reference to the ticket.