1.6천건 · 관련도순
You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Profiles macOS and iOS apps with Instruments and xctrace: choosing templates such as Time Profiler, launching binaries with arguments, recording traces, and exporting results. Use when a Mac or iOS app needs CPU, memory, or responsiveness profiling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and run EMULATORS locally on Windows with the repository-compatible Visual Studio configuration and SDL runtime architecture. Use whenever Codex compiles, links, tests, launches, or smoke-tests an EMULATORS executable on Windows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Give a pocs/ app a Cloudflare Workers preview deploy so a PR returns a testable staging URL (auth-working). Use when wiring a POC for previews, or when "build X as a poc" needs to end at a clickable link. For launched apps/ apps use the /deploy skill instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn one task into a tree of GitHub issues worked by agents. Creates (or reuses) an epic issue, then launches the recursive orchestrator → decomposer → worker pipeline. Use when asked to "decompose a task", "break this down into issues and work it", "spawn agents to build X", or run via /task-decompose.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guidance for Salesforce Flow implementation from design through deployment. Use this skill when building Screen Flows, Record-Triggered Flows, Schedule-Triggered Flows, or Autolaunched Flows. Covers Flow design patterns, metadata XML generation, variable/element reference validation, governor limit optimization, and sf CLI deployment. Critical for preventing reference errors (undeclared variables, invalid element references) and deployment failures. Use when creating new Flows, debugging Flow errors, optimizing Flow performance, or deploying Flows to production.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
アプリの本番品質を保証する統合スキル。セキュリティ監査・例外/エラー処理設計・攻撃別対処・ サーバーコスト最適化・パフォーマンス最適化を1つのゲートで検査する。 「セキュリティチェックして」「リリースしていい？」「本番公開前の確認」「脆弱性診断」「監査して」 「エラー処理を設計して」「例外処理を入れて」「攻撃対策」「レート制限」「コストを抑えたい」 「無料枠に収めたい」「パフォーマンス改善」「重い」などの文脈で必ず使用する。 また、認証・ユーザー入力・API・決済・機密データを扱うコードを書いた直後、およびデプロイ前には ユーザーが明示しなくても本スキルの該当セクションを適用する。 デプロイ手順自体は Skill cloudflare-secure-deploy、認証実装は Skill better-auth-google-gate、 LLMコストは Skill llm-api-integration / llm-cost-simulator を併用する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided setup of Exasol Personal — a free Exasol database running locally on a Mac or deployed to your own AWS, Azure, Exoscale, or STACKIT account. Covers picking the right deployment flavor, the `exasol` launcher CLI (`exasol install <preset>`, `exasol connect`, `exasol info`, `exasol deployments list`, `exasol destroy`), the `local`, `aws`, `azure`, `exoscale`, and `stackit` presets, and following the official exasol/exasol-personal instructions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Controlled restart of a named app, browser or service that keeps the context it can and verifies the new instance answers. Use for /restart chrome, firefox, or any app the user asks to relaunch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect PowerShell Empire framework artifacts in Windows event logs by identifying Base64 encoded launcher patterns, default user agents, staging URL structures, stager IOCs, and known Empire module signatures in Script Block Logging events.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Metaplex development on Solana — NFTs, tokens, compressed NFTs, candy machines, token launches. Use when working with Token Metadata, Core, Bubblegum, Candy Machine, Genesis, or the mplx CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a list of merged changes, closed work items or commit messages the user provides into DRAFT release notes under the version heading and date the user supplies, grouped as features, fixes and other, in the organisation's tone from the style guide or prior notes given, with every entry traced to its source item, breaking changes and required actions flagged first, and internal-only items held back for the release owner to confirm. Use when the user asks to "write the release notes for this version", "turn these merged pull requests into a changelog", "summarise what shipped this sprint for customers", "draft the what's new for this release" or "group these closed tickets into release notes". Do not use for an announcement email or intranet post about a launch, use announcement-drafter instead; for a change ticket, use change-request-pack; for a how-to article about one fix, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews the instructions text and skills of a declarative agent, with its stated capabilities, knowledge sources and audience, for prompt-injection exposure, data-leakage paths, over-broad permissions and missing refusals, and returns an attack-surface map, a findings table with severity, quoted evidence and attack path, one pasteable fix per finding, a probe pack the owner can run and a refusal-coverage table. Use when the user asks to "red-team this agent", "check these instructions for prompt injection", "could this agent leak data", "review the permissions on my agent" or "what should this agent refuse". Do not use for checking a SKILL.md against the format rules, use skill-file-reviewer instead; do not use for designing the launch test set, use agent-evaluation-plan instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds one DRAFT message house for a product, service, programme or initiative from the source material the user provides: an umbrella statement, two to four pillars and graded proof points under each, with every proof point that lacks a source flagged, a claim sensitivity table, an audience coverage check and open questions. Use when the user asks to "build a message house", "write our messaging framework", "what are the key messages for this launch", "turn this research into messaging pillars" or "test our current messaging against the evidence". Do not use for a campaign one-pager, use campaign-brief-builder instead; to check whether a written document's claims are substantiated, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews one SKILL.md against the format rules and returns a findings table: strict YAML front matter with exactly name and description, name equal to the folder, description as the trigger, the eight-heading skeleton, capability-neutral wording, safety boundaries. Each finding carries severity, rule identifier, location, quoted evidence and replacement text; the verdict READY, REVISE or BLOCKED is an apparent state and the owner decides. Use when the user asks to "review this SKILL.md", "check my skill file before upload", "lint this skill description", "validate the front matter of this skill" or "score this skill folder". Do not use to write an agent's instructions field, use agent-instructions-drafter instead; for injection or leakage exposures use agent-instructions-red-team; for launch tests use agent-evaluation-plan. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific passages, marketing risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CMO review", "pressure-test the positioning", "what would a CMO say about this", "challenge the launch plan" or "check the messaging and audience". Do not use for price economics, margins or payback, use cfo-reviewer instead; for sales pipeline mechanics, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose and restore the Claude Desktop app when it will not start, crashes, or runs with no visible window. Use for Windows MSIX launch failures, 'Not main instance', stale AppX job containers, NeedsRemediation or 0x80070020 errors. Separates Desktop from the CLI, reads fresh logs, picks a narrow fix and proves a visible working window. Triggers: /claude-repair, Claude Desktop won't open, Claude app crashed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.