Loading...
Loading...
Found 8,412 Skills
Fan out N parallel workers on slices of a job or on a race, collect every result, and return one evidence-backed report. Use for wide coverage, audits, races between approaches or exploration, or for /ds-swarm, 'swarm this', 'split this across workers'.
Rebuilds the current implementation from scratch as the simplest design that satisfies what was learned, after the user approves the design. Use when the user explicitly asks to redo the work, start over, scrap the approach, or rewrite it more simply. Never infer from a failing or complex implementation. Not for fitting a new requirement into an existing design; use redesigning-from-first-principles.
Write Basic Memory notes that render as charts, tables, boards, and live views with `::bm-*` Comark components. Use when a note reads better as a figure or board, or already has `::bm-*` directives.
Assess findings and feature opportunities, preserve related evidence and decisions, and recommend scoped next actions. Use for Just, Yak or Explore handoffs and decisions about a fix, improvement or PR.
Experience a source-accessible library or developer tool through outcome-oriented slices before reading its implementation, and report honest coverage and observable findings without repairing or publishing them.
Room/SQLite, DataStore and repository traps: migrations, NOT IN with NULLs, LIKE escaping, delete order, local-time bucketing, imports, caching, paging. Use before writing a query or migration, or when data comes back wrong.
Use when the developer wants the agent to work without approving every write - "tu dong hoan toan", "cu lam het di", "dung hoi tung buoc", "work autonomously", "approve everything for this task", a long build session - or when an apply preview says autopilot is active, paused, expired or not covering a statement. Requests one developer-approved lease, works strictly inside it, stops where it stops, and reports every write it made.
Use when producing the final output a person will read — a chat reply, summary, status update, handoff, or a PR, issue, or commit message — not your private reasoning. Triggers on wrapping up a task or reporting back to the user.
Create a current-state research query plan from a task.
Use when checking or testing a Void app with Hono CLI — pages, page actions, and API routes. TRIGGER when package.json depends on 'void', the project has void.config.ts, or the user mentions Void. Void is a framework built on Hono.
Before starting a nontrivial task, compute how much understanding the work demands and split it into "already understood" vs "learn first". Use when the user invokes /depth-check, asks "what do I need to understand before touching this?", "이거 시작하기 전에 뭘 알아야 해?", "어디까지 파악하고 들어가야 해?", or is about to start work in territory they may not know well. Maps the task's blast radius, grades the depth each area requires, and emits the short list of questions to answer before coding.
Writes technical blog posts about features being built. Triggers when user asks to write about development progress, implementations, or project updates.