1.3천건 · 관련도순
Scaffold and govern an MCP server as a bounded tool seam. Defines which tools the agent may call, enforces the principle that agents call tools and tools call infrastructure. Trigger when adding or reviewing an MCP server in an agent system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating or rewriting a README for a reusable package or library. Focus on installability, minimal usage example, compatibility, and developer onboarding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without naming it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Elite full-stack developer for rapid spec and implementation. Use when the user asks to talk to Barry or requests the quick flow solo dev.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Process] Use when a developer needs to understand and judge scoped work: a change set, subsystem, decision, plan or concept — flow, rationale, trade-offs, testing. Bugs: investigate --mode=debug; one feature's code flow: investigate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ship an already-committed Git branch through GitHub: verify branch/worktree intent, push, create or mark a pull request ready for review, optionally wait for CI, optionally address review comments automatically, and merge with explicit safety gates. Use when a solo developer repeatedly asks to publish committed work, register a ready PR, handle PR feedback, and complete merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analisa seu histórico recente de chats do Claude Code para identificar padrões de codificação, lacunas no desenvolvimento e áreas para melhoria, seleciona recursos de aprendizagem relevantes do HackerNews e envia automaticamente um relatório de crescimento personalizado para suas DMs do Slack.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating Product Hunt launch carousel images for developer tools, AI tools, open-source projects, GitHub launches, or technical products. Research comparable launches, inspect the project, extract verified proof points, then generate 4-5 launch-ready images with consistent branding, product surfaces, readable copy, and source-grounded claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when shipping a macOS app outside the App Store — Developer ID signing with hardened runtime, notarization with notarytool, stapling, building a clean drag-to-Applications DMG, and verifying the result launches on a stranger's Mac.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build production-ready Tavily integrations with best practices baked in. Reference documentation for developers using coding assistants (Claude Code, Cursor, etc.) to implement web search, content extraction, crawling, and research in agentic workflows, RAG systems, or autonomous agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WeChat Mini Program development skill for building, debugging, previewing, testing, publishing, and optimizing mini program projects. This skill should be used when users ask to create, develop, modify, debug, preview, test, deploy, publish, launch, review, or optimize WeChat Mini Programs, mini program pages, components, `tabBar`, routing, navigation, icon assets, project structure, project configuration, `project.config.json`, `appid` setup, device preview, real-device validation, WeChat Developer Tools Nightly workflows, `wechatide` CLI, WeChat IDE Skills/MCP, console/network debugging, `miniprogram-ci` preview/upload flows, or mini program release processes. It should also be used when users explicitly mention CloudBase, `wx.cloud`, Tencent CloudBase, 腾讯云开发, 微信云开发, or 云开发 in a mini program project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
处理 1c7/chinese-independent-developer 仓库的项目提交。 检查 issue #160 新评论、新开的 Issue、新开的 PR， 将有效项目添加到对应 README，关闭垃圾内容。 当用户说"处理提交"、"处理 issue"、"跑一下列表"时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GStack developer-experience review for implemented repositories and workflows, focused on setup friction, command reliability, docs gaps, and maintainability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GStack autoplan method for running a broad CEO, design, engineering, and developer-experience review before opening implementation windows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GStack developer-experience plan review for setup, local commands, docs, test loops, onboarding friction, and maintainability before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to build, adapt, run, or evaluate an OpenAI Agents SDK app from Cursor. Prefer a docs-first workflow and route API credential decisions through openai-platform-api-key before API-backed work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when Cursor is asked to build, run, test, debug, or configure an OpenAI-backed or provider-unspecified AI app, UI, script, CLI, generator, or tool, especially requests phrased only as "using AI" or generators driven by forms/user input; also use for OPENAI_API_KEY or sk-proj setup. Treat this as the credential gate: inspect safely, ask reuse-vs-new before API work, guide manual local setup when needed, verify presence, and never expose plaintext.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user explicitly wants a ChatGPT App, Apps SDK project, MCP server plus widget UI, ChatGPT-compatible tool UI, or submission/deployment work for that surface. Build, scaffold, refactor, or troubleshoot those projects from Cursor, consult openai-docs before generating code, and use openai-platform-api-key before any app path that requires live OpenAI API credentials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an OpenAI API request fails or the user asks what an error means, including blocked access to api.openai.com, 401 invalid_api_key, missing OPENAI_API_KEY, 429 insufficient_quota, 429 rate_limit_exceeded, or 403 model_not_found. Classify the failure, name the next step, route credential setup to openai-platform-api-key, and current guidance to openai-docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.