kuroryuu-public

Use when the user wants to toggle question mode — making Claude ask clarifying questions before making edits. Triggers on 'question_toggle', 'toggle questions', 'ask me before editing', 'stop asking questions', or when the user wants to control whether Claude asks for confirmation before changes.

Use when the user wants multiple polymathic agents to analyze a problem, review code, debate an idea, or provide diverse expert perspectives. Triggers on 'consult polymaths', 'ask the polymaths', 'get polymath opinions', 'polymath review', 'run it by the polymaths', 'what would the polymaths say', or any request for multi-perspective expert analysis. Also trigger when the user says 'consult-polymaths' or wants to 'task the polymaths'. This is different from /consult (which queries external LLM APIs) — this skill spawns internal polymathic thinking agents.

Use when the user wants to run comprehensive end-to-end testing of a web application. Triggers on 'run e2e tests', 'test this app end to end', 'test all user journeys', 'do a full test pass'. Launches parallel research sub-agents then uses agent-browser for testing.

Use when creating a structured implementation plan with parallel task decomposition for team execution. Triggers on 'k-plan', 'create a plan', 'plan this task', 'decompose this work', or when the user needs a detailed plan document with task breakdown, dependencies, and team assignment before implementation.

Use when starting an autonomous task execution loop with structured git commits tied to task IDs. Triggers on 'k-start-worker-loop', 'start worker loop', 'autonomous task loop', 'work through tasks automatically', or when the user wants to iterate through a task list with automatic verification and git commits per task.

Use when the user needs browser automation specifically using playwright-cli — navigating pages, filling forms, managing tabs, taking screenshots, recording traces, or mocking network requests. Triggers on 'use playwright', 'playwright-cli', 'open browser with playwright'.

Creates Excalidraw diagrams programmatically. Use when the user wants flowcharts, architecture diagrams, system designs, or any visual diagram instead of ASCII art. Outputs .excalidraw files that can be opened directly in Excalidraw or VS Code with the Excalidraw extension.

Use when starting ANY non-trivial task to maximize parallelism - spawns multiple subagents, creates task graphs, identifies independent work streams

This skill should be used when saving checkpoints, writing worklogs, linking cross-references, using inbox/messaging, RAG interactive mode, or doing any Kuroryuu persistence workflow. Trigger phrases include "save checkpoint", "write worklog", "cross-reference", "link worklog", "inbox", "send message", "RAG interactive", "search interactively".

Creates Kuroryuu-specific interactive HTML playgrounds pre-populated with real project architecture data. Use when the user asks for a "kuroryuu playground", "architecture explorer", "theme tuner", "agent team planner", or "hook builder". Extends the official playground skill with project-aware templates.

This skill should be used when the user asks about "Kuroryuu bootstrap", "multi-agent coordination", "leader worker pattern", "promise protocol", "k_ tools", "session start", "checkpoint save", "inbox messages", "RAG search", "how does Kuroryuu work", "Kuroryuu architecture", or needs guidance on Kuroryuu multi-agent orchestration patterns and workflows.

Adoption of the 'Opus 4.5 Ultimate Quizzer' persona for rigorous requirements gathering.

Use when starting work on a specific technology (typescript, react, python, vite, nextjs, etc), when user asks "find a skill for X", "search skills.sh", "best practices for X", or when you need procedural knowledge for a task. Searches the open agent skills ecosystem at skills.sh.