62건 · 관련도순
Prepare and publish releases of the Cline VS Code extension. Follow separate paths for stable, nightly, and emergency legacy releases, covering version selection, release notes, approval steps, packaged builds, and checks after publication.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and edit draw.io files for workflows, system architecture, database relationships, and service interactions. Organize shapes and connectors, apply consistent styling, and check file structure so diagrams can be opened and edited in draw.io.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Add Storybook stories, examples of component states, for the Kilo VS Code extension UI. The existing Playwright runner turns them into screenshot comparisons to check visual changes across states and widths.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and review icons for Kilo’s VS Code extension and webviews, the extension’s embedded interface panels. Choose existing icons or suitable SVG assets, register them correctly, and check theme appearance and accessible button names.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use the `ccwf` CLI (from @cc-wf-studio/cli) to render, validate, preview, export, or run cc-wf-studio workflow JSON files from the terminal. Apply whenever the user mentions viewing, visualizing, checking, executing, or converting a workflow under `.vscode/workflows/` (or any `*workflow*.json`), wants a Mermaid diagram of a workflow, asks to "see" / "preview" / "open" a workflow, or wants to run a workflow as a Claude Code Skill without opening VSCode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose why Claude Code is (or isn't) prompting for permission. By default reads only repo-local layers (CLI project, CLI project-local, VSCode workspace). Host-global layers (CLI user `~/.claude/`, VSCode user settings) are read ONLY when the user explicitly confirms — those files may contain unrelated paths or secrets. Use when user says "why is it asking me to approve?", "permission check", "why am I getting prompts?", "bypass isn't working", "check my permissions". Read-only diagnostic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bump version in package.json and auto-generate CHANGELOG.md using standard-version for vscode-sidebar-terminal. Triggered by /release or /version commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides guidance for maintaining documentation consistency with implementation in the vscode-sidebar-terminal project. Use this skill when creating or updating documentation, verifying documentation accuracy, preparing releases, or when the codebase has changed and documentation may need updates. This skill should be used proactively after implementing features or bug fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides expert-level guidance for debugging and fixing bugs in VS Code extensions. Use when investigating runtime errors, fixing memory leaks, resolving WebView issues, debugging activation problems, fixing TypeScript type errors, or troubleshooting extension communication failures. Covers systematic debugging workflows, common bug patterns, root cause analysis, and prevention strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides systematic bug detection and discovery capabilities for VS Code extensions. Use when searching for hidden bugs, analyzing code for potential issues, investigating suspicious behavior, performing code audits, or proactively finding bugs before they manifest. Covers static analysis patterns, dynamic analysis techniques, code smell detection, and systematic codebase investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides expert-level guidance for VS Code extension development. Use when implementing new extension features, debugging extension code, designing WebView UIs, implementing Language Server Protocol features, or optimizing extension performance. Covers activation events, contribution points, VS Code API patterns, security best practices, testing strategies, and publishing workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides expert-level guidance for refactoring VS Code extension code. Use when extracting classes or functions, reducing code duplication, improving type safety, reorganizing module structure, applying design patterns, or optimizing performance. Covers systematic refactoring workflows, code smell detection, safe transformation techniques, and VS Code-specific patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides comprehensive guidance for setting up and configuring test environments for VS Code extension projects. Use when initializing a new test infrastructure, configuring test runners (Vitest), setting up CI/CD test pipelines, integrating coverage tools (v8/c8), or troubleshooting test configuration issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides expert-level guidance for implementing VS Code WebView features. Use when creating WebView panels, implementing secure CSP policies, handling Extension-WebView communication, managing WebView state persistence, optimizing WebView performance, or debugging WebView rendering issues. Covers security best practices, message protocols, and VS Code-specific WebView patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides expert-level guidance for Test-Driven Development (TDD) in VS Code extension development following t-wada methodology. Use when writing tests before implementation, creating comprehensive test suites, implementing Red-Green-Refactor cycles, or improving test coverage for extension components like WebViews, terminal managers, and activation logic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for VS Code extension development from scaffolding to Marketplace publication
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates .http files for the VS Code REST Client extension from Express, Next.js, Fastify, or other API routes. Creates organized request files with variables, environments, and authentication. Use when users request "generate http files", "rest client requests", "create .http file", or "vscode api testing".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep Kilo-specific changes small in files shared with upstream OpenCode. The skill guides where to place custom logic and tests, how to mark changes, and how to check annotations while preserving behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify what a development phase should deliver before discussing implementation. Through structured questions and ambiguity scores, the skill produces SPEC.md with testable requirements, explicit scope boundaries, and acceptance criteria for judging completion.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify implementation choices before planning a development phase. The skill reviews existing project context and code, asks about unresolved decisions, and records the answers in a context file for research and planning agents.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
VS Code integration for viewing diffs and comparing files. Use when showing file differences to the user.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture VS Code screenshots and self-contained browser animation scenes through Playwright. Use for editor evidence, slide imagery, or silent WebM scene clips.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when connecting an AI agent to Scenario (scenario.com) through MCP, or when a task involves generating images, video, 3D, audio, sprites, textures, or game assets. Also when picking a Scenario model, running a LoRA, refining a generation prompt, uploading reference images, waiting on generation jobs, checking credits or quota, hitting Scenario auth, scope, or Forbidden errors, or setting up mcp.scenario.com in Claude Code, Cursor, VSCode, or another agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.