IDE & Editors
2165 skills in Tools > IDE & Editors
implement-type-annotations
Add comprehensive type hints to Python/TypeScript code to improve IDE support, catch errors early, and enable better AI code understanding
emacs-testing
Test changes in a dedicated Emacs session. Good for validating behavior and UI results.
youtube-transcript
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
coding-guidelines-gen
Generate nested AGENTS.md coding guidelines per module (monorepo-aware), detect languages/tooling, ask architecture preferences, and set up missing formatters/linters (Spotless for JVM). Use when the user wants module-scoped AGENTS.md coding guidelines or to set up missing formatters/linters.
workflow-guide
Provides guidance on Cursor ↔ Claude Code 2-agent workflow. Use when user mentions ワークフローについて, Cursorとの連携, 作業の流れ, 2-agent workflow, collaboration. Do NOT load for: 実装作業, ワークフロー設定, ハンドオフ実行.
agenticfleet-frontend-component-workflow
End-to-end guide for creating React components in AgenticFleet's frontend, from design tokens through Tailwind styling, shadcn/ui integration, state management, to testing.
initiate-memory
Comprehensive guide for initializing or reorganizing agent memory and project context. Use when setting up a new project, when the user asks you to learn about the codebase, or when you need to create effective memory blocks for project conventions, preferences, and workflows.
dry-refactoring
Guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use when user asks to eliminate code duplication, refactor repetitive code, apply DRY principle, or mentions code smells like copy-paste, magic numbers, or repeated logic. Implements a 4-step workflow from identifying repetition to verified refactoring.
workbench-workflow
Arma Reforger Workbench workflow, testing guidelines, and debugging patterns
file-analysis
Structured file enumeration and content analysis for understanding codebase structure before reviews or refactoring. Triggers: file analysis, codebase structure, directory mapping, hotspot detection, code exploration, file enumeration, structure mapping, module boundaries Use when: before architecture reviews to understand file organization, exploring unfamiliar codebases to map structure, estimating scope for refactoring or migration DO NOT use when: general code exploration - use the Explore agent. DO NOT use when: searching for specific patterns - use Grep directly. Provides structural context for downstream review and refactoring workflows.
structured-output
Guide to formatting review deliverables for consistency, ensuring findings are comparable across different types of analysis. Triggers: report formatting, deliverable structure, consistent output, review output, findings format, report template, output consistency Use when: formatting final review outputs, ensuring consistent deliverable structure, making findings comparable across reviews DO NOT use when: capturing evidence during analysis - use evidence-logging. DO NOT use when: reviewing changes - use diff-analysis or review-core first. Consult this skill when formatting final review deliverables.
pensive:shared
Shared infrastructure and reusable modules for all pensive review skills. Triggers: pensive patterns, review workflow, output templates, quality checklists, pensive infrastructure, shared review patterns Use when: other pensive skills need common patterns, creating new review skills, ensuring consistency across pensive plugin DO NOT use directly: this skill is infrastructure for other pensive skills. This skill provides shared patterns consumed by other pensive skills.
shared
Shared infrastructure and patterns for imbue analysis skills. Triggers: imbue patterns, todowrite patterns, evidence formats, analysis workflows, shared templates, imbue infrastructure Use when: other imbue skills need common patterns, creating new analysis skills, ensuring consistency across imbue plugin DO NOT use directly: this skill is infrastructure for other imbue skills. This skill provides shared patterns consumed by other imbue skills.
testing-quality-standards
Shared testing quality metrics and standards for cross-plugin use. Referenced by pensive:test-review and parseltongue:python-testing. Triggers: testing standards, quality metrics, coverage thresholds, test quality, anti-patterns, testing best practices, quality gates Use when: evaluating test quality, setting coverage thresholds, identifying testing anti-patterns, establishing quality standards DO NOT use when: simple scripts without quality requirements. Consult this skill when establishing testing quality standards.
evidence-logging
Workflow for capturing evidence and citations to create reproducible analyses and audit trails. Triggers: evidence capture, citations, reproducible analysis, audit trail, documentation, evidence logging, findings documentation Use when: conducting any review that needs evidence trails, creating audit documentation, ensuring reproducibility of analyses DO NOT use when: quick informal checks without documentation needs. DO NOT use when: structured output is the focus - use structured-output. Use this skill as foundation for all evidence-based review workflows.
transcribe-audio
Transcribes video audio using WhisperX, preserving original timestamps. Creates JSON transcript with word-level timing. Use when you need to generate audio transcripts for videos.
youtube-transcribe-skill
Extract subtitles/transcripts from a YouTube video URL and save as a local file. Use when you need to extract subtitles from a YouTube video.
backup-library
Creates compressed ZIP backups of libraries directory. Backs up library.yaml, transcripts, and roughcuts (not video files). This skill can also be useful when you need to restore a library.
mcp
Guide for working with Splitrail's MCP server. Use when adding tools, resources, or modifying the MCP interface.
pulumi-troubleshooting
Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization