67 件（Rune-kit のリポジトリ） ・ 人気順
概要と使いどころ
Creates structured handoff briefings between agents. Use when delegating complex work to subagents that would otherwise lose context. Packages task context, constraints, and progress into a compact packet that subagents can consume without re-reading the full conversation. Prevents the 'lost context' problem in multi-agent delegation.
日本語の概要は準備中です。原文の説明を表示しています。
Feature implementation orchestrator. ALWAYS use this skill for ANY code change — implement, build, add feature, create, fix bug, or any task that modifies source code. This is the default route for 70% of all requests. Runs full TDD cycle: understand → plan → test → implement → quality → verify → commit.
日本語の概要は準備中です。原文の説明を表示しています。
Spec↔code convergence scan. Use after implementation to verify the ACTUAL codebase matches the spec/plan — detects missing backends, dead buttons, partial wiring, scope creep. Classifies gaps (missing/partial/contradicts/unrequested), appends remediation tasks, loops until converged. The direct answer to 'the UI renders but nothing works' syndrome.
日本語の概要は準備中です。原文の説明を表示しています。
Gathers N independent, decorrelated perspectives across model families (external CLIs when present, subagents when not) and arbitrates inline. Use when a decision needs genuine debate — not same-model echo — for critique, review, or judge calls. Honest about degradation: never claims 'consensus' from a single model family.
日本語の概要は準備中です。原文の説明を表示しています。
Database workflow specialist. Generates migration files with rollback scripts, detects breaking schema changes, and validates query parameterization.
日本語の概要は準備中です。原文の説明を表示しています。
Root cause analysis for bugs and unexpected behavior. Traces errors through code, uses structured reasoning, and hands off to fix when cause is found. Core of the debug↔fix mesh. When the diagnosed cause is a memory leak in a long-running process, escalates to perf for cost-impact framing (leaks drive OOM-restart → cold-start → autoscaler spend, often 20-40% bill inflation).
日本語の概要は準備中です。原文の説明を表示しています。
Dependency health management. Detects package manager, checks outdated packages and vulnerabilities, and produces a prioritized update plan.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy application to target platform. Use when user explicitly says 'deploy', 'push to production', 'ship it'. Handles Vercel, Netlify, AWS, GCP, DigitalOcean, and VPS with pre-deploy verification and health checks. Enforces cost allocation tags + Managed-vs-Self-Host crossover decisions so deploy choices map to actual unit economics, not hand-waved 'we'll optimize later'.
日本語の概要は準備中です。原文の説明を表示しています。
Design system reasoning. Maps product domain to style, palette, typography, and platform-specific patterns. Generates .rune/design-system.md as the shared design contract for all UI-generating skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a reader needs an editorial architecture, flowchart, sequence, state, ER, swimlane, loop, layer-stack, data-flow, or process diagram as self-contained HTML/SVG. Symptoms: 'draw the system', 'architecture diagram', 'sequence of calls', 'state machine visual'. Not for logos, OG images, or Marp decks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and parse office documents — PDF, DOCX, XLSX, PPTX, CSV. Use when creating reports, exporting tabular data, or processing uploaded office files. NOT for project documentation (use docs).
日本語の概要は準備中です。原文の説明を表示しています。
Find documentation for APIs, libraries, and error messages. Looks up official docs, changelog entries, and migration guides.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generate and maintain project documentation. Creates README, API docs, architecture docs, changelogs, and keeps them in sync with code changes. The "docs are never outdated" skill.
日本語の概要は準備中です。原文の説明を表示しています。
Apply code changes and fixes. Writes implementation code, applies bug fixes, and verifies changes with tests. Core action hub in the development mesh.
日本語の概要は準備中です。原文の説明を表示しています。
Specialized git operations — semantic commits, PR descriptions, branch management, conflict resolution guidance. Replaces ad-hoc git commands with a dedicated, convention-aware utility.
日本語の概要は準備中です。原文の説明を表示しています。
Clone, port, or convert features from any GitHub repo into your project. Use when stealing patterns from external repos or porting proven code. Understand before copy, challenge before implement. 4 modes: port (rewrite), compare (analysis), copy (transplant), improve (copy + optimize).
日本語の概要は準備中です。原文の説明を表示しています。
Verify AI-generated imports, API calls, and packages actually exist. Use when finishing AI-generated code that introduces new imports or external API calls — auto-fires after fix/cook to catch phantom functions, non-existent packages, and slopsquatting attacks.
日本語の概要は準備中です。原文の説明を表示しています。
Find architectural friction in a codebase and propose deepening opportunities. Use when user wants to improve architecture, find refactor candidates, consolidate shallow modules, or make a codebase more testable. Outputs scored proposals (depth/leverage/locality) that surgeon and review can consume.
日本語の概要は準備中です。原文の説明を表示しています。
Structured incident response. Use when user reports an outage, production error, or says 'incident', 'something is down', 'users are affected'. Triage severity, contain blast radius, root-cause, document timeline, generate postmortem.
日本語の概要は準備中です。原文の説明を表示しています。