Plan complex coding changes by exploring existing code, clarifying requirements, and tracing effects across the system. Produce a PLAN.md with recommended changes, affected files, and verification steps, then implement after the user approves.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Removes hosted demo restrictions from an Open Harness fork, including session and message caps and deletion blocks. Cleans up related helpers and tests while preserving unrelated authentication, session ownership checks, and sandbox behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write, review, and refactor React and Next.js code using Vercel's performance guidelines. Apply prioritized rules to reduce sequential data fetching, shrink downloaded code, improve server processing, and avoid unnecessary updates to the interface.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and refine web animations for buttons, dialogs, menus, and gestures. The skill guides timing, changes in speed, spring motion, performance, and reduced-motion preferences so transitions fit the interaction and remain responsive.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build workflows with Vercel's Workflow DevKit that preserve progress and resume after restarts. Structure operations as persistent steps, wait for external events, retry temporary failures, and inspect runs to understand how a process is progressing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides deployment of Open Harness on Vercel, from collecting credentials and setting environment variables to checking the first session. Separates a basic setup from a fuller setup with GitHub repository access.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up Zero and retrieve workflow guidance matched to the installed compiler. This skill helps agents load the references needed for editing, checking, and testing code, while preserving the compiler version already used by the project.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn OpenAPI specifications, GraphQL endpoints, MCP servers, or custom JavaScript functions into bash commands and a JavaScript API. The skill guides implementation so agents can call these tools from the isolated execution environment provided by just-bash.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lead workflow for developing vgpu features and Blender assets with the repository's subharness specialists. Use for agent-based research, API design, implementation, shaders, materials, simulations, or ImageGen-guided asset iteration, and when the human mentions the agent flow or subharness team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to explain a problem, issue, PR, or feature as an infographic. Create a step-by-step visual explanation starting from user code or actions, with a clear problem/solution boundary, syntax-highlighted snippets, and focused diagrams. Support standalone educational PDFs and Markdown-first PR explanations, with optional images only for complex diagrams. Also apply when explicitly invoked by the repository PR writer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, debug, test, and optimize WebGPU projects using vgpu, its CLI, or @vgpu packages. Use for vgpu API questions, WGSL workflows, browser or Node rendering, integrations, testing, performance work, and Blender asset modeling, baking, and runtime integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs. Use when creating, editing, or reviewing files in the lat.md/ directory.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated AWS cloud services (S3, SQS, Cognito, IAM, STS) for local development and testing. Use when the user needs to interact with AWS API endpoints locally, test S3 bucket and object operations, emulate SQS queues and messages, test Cognito sign-up, sign-in, JWTs, or Identity Pools, manage IAM users/roles/access keys, test STS assume role, or work without hitting real AWS APIs. Triggers include "AWS emulator", "emulate AWS", "mock S3", "local SQS", "test IAM", "emulate S3", "AWS locally", "STS assume role", or any task requiring local AWS service emulation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated Linear GraphQL API for local development and testing. Use when the user needs to test Linear integrations locally, emulate Linear issues, comments, teams, workflow states, OAuth apps, webhooks, agent sessions, or work with the Linear API without hitting the real Linear service. Triggers include "Linear API", "emulate Linear", "mock Linear", "test Linear OAuth", "Linear webhook", "Linear agent", "local Linear", or any task requiring a local Linear API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated Twilio REST APIs for local development and testing. Use when the user needs to test Twilio Messaging, Verify, Voice, phone numbers, webhooks, status callbacks, inbound SMS simulation, or Twilio SDK integrations without hitting the real Twilio service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated GitHub REST API for local development and testing. Use when the user needs to interact with GitHub API endpoints locally, test GitHub integrations, emulate repos/issues/PRs, set up GitHub OAuth flows, configure GitHub Apps, test webhooks, or work with actions/checks without hitting the real GitHub API. Triggers include "GitHub API", "emulate GitHub", "mock GitHub", "test GitHub OAuth", "GitHub App JWT", "local GitHub", or any task requiring a local GitHub API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated Google OAuth 2.0, OpenID Connect, Gmail, Calendar, and Drive for local development and testing. Use when the user needs to test Google sign-in locally, emulate OIDC discovery, handle Google token exchange, configure Google OAuth clients, work with Gmail messages/drafts/threads/labels, manage Calendar events, upload or list Drive files, or work with Google userinfo without hitting real Google APIs. Triggers include "Google OAuth", "emulate Google", "mock Google login", "test Google sign-in", "OIDC emulator", "Google OIDC", "Gmail API", "Google Calendar", "Google Drive", "local Google auth", or any task requiring a local Google API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and share third-party HTTP API emulators with emulate. Use to emulate an external provider, add a custom service plugin, model stateful vendor endpoints, configure custom seeds, or package an emulator. For an existing built-in service, use that service's skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated Resend email API for local development and testing. Use when the user needs to send emails locally, test transactional email flows, implement magic link or verification code auth, inspect sent emails, manage domains/contacts/API keys, or work with the Resend API without sending real emails. Triggers include "Resend API", "emulate Resend", "send email locally", "test email", "magic link", "verification email", "email inbox", "RESEND_BASE_URL", or any task requiring a local email API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Next.js adapter for embedding emulators directly in a Next.js app via @emulators/adapter-next. Use when the user needs to embed emulators in Next.js, set up same-origin OAuth for Vercel preview deployments, create an emulate catch-all route handler, configure Auth.js/NextAuth with embedded emulators, add persistence to embedded emulators, or wrap next.config with withEmulate. Triggers include "Next.js emulator", "adapter-next", "embedded emulator", "same-origin OAuth", "Vercel preview", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Next.js app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emulated Vercel REST API for local development and testing. Use when the user needs to interact with Vercel API endpoints locally, test Vercel integrations, emulate projects/deployments/domains, set up Vercel OAuth flows, manage environment variables, create API keys, configure protection bypass, emulate Vercel Blob storage, or test without hitting the real Vercel API. Triggers include "Vercel API", "emulate Vercel", "mock Vercel", "test Vercel OAuth", "Vercel integration", "Vercel Blob", "local Vercel", or any task requiring a local Vercel API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Local drop-in API emulator for Vercel, GitHub, Google, Slack, Apple, Microsoft, AWS, Clerk, Linear, Twilio, and other developer APIs. Use when the user needs to start emulated services, configure seed data, write tests against local APIs, set up CI without network access, or work with the emulate CLI or programmatic API. Triggers include "start the emulator", "emulate services", "mock API locally", "create emulator config", "test against local API", "npx emulate", or any task requiring local service emulation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.