Loading...
Loading...
Found 36 Skills
This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.
[Utilities] ⚡⚡⚡⚡⚡ Bootstrap a new project step by step
Before executing a task, analyze the available tool set (web search, code execution, file read/write, API calls, database queries, memory tools), select the optimal tools, plan execution order, and prevent unnecessary tool calls. Triggers on multi-step tasks, "which tool should I use", "plan the tools", or whenever multiple tools could apply.
Превращает идею в конкретную задачу, которую агент может выполнить. Проводит через 5 шагов: идея → результат → реальность → задача → план.
Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict in_place; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.
Create comprehensive, self-contained task prompts for implementing features or fixing bugs.
[Git & Release] Stage, commit and push all code in the current branch
[Fix & Debug] ⚡ Analyze logs and fix issues
[Dev] Extracts and organizes best practices for a given topic into a minimal tree structure (max depth 3, max 5 children per node). Use during task planning when writing subtasks in Docs/{name}_Task.md - output is added under each subtask as a concise reference guide. Pure reasoning task with strict formatting rules: keywords/noun phrases only, no prose. (project)
Internal conversation-entry router for Claude Code. Performs a lightweight intake pass at the start of substantive work: decide whether a more specific skill should be invoked first, whether specialized agent delegation is warranted, how much context is actually needed, and whether the task needs planning or can proceed directly. Not a user-facing slash command.
Plan mode: write markdown plan to .hermes/plans/, no exec.