2.8천건 · 관련도순
Generate publish-grade SVG+PNG technical diagrams (architecture, data flow, sequence, ER, state-machine, etc.) in 8 styles. Writes to tasks/visuals/. Needs rsvg-convert for PNG; else SVG-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing, reviewing, or refactoring Vue 3 code — components, composables, reactivity, Pinia state, Pinia Colada data-fetching, file-based routing, and forms. Targets Composition API + <script setup> + TypeScript. Auto-activates on .vue files. For deep best-practices review/recommendations or the full ordered workflow (built-in components, animations, performance pass), use mk:vue-best-practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser automation CLI for AI agents using agent-browser. Use for navigating websites, clicking/filling pages, screenshots, data extraction, web app testing, exploratory QA, dogfooding, Electron apps, Slack automation, Vercel Sandbox browser runs, AWS AgentCore cloud browsers, auth-heavy flows, and long autonomous browser sessions. Prefer over generic browser tools when a fresh/tool-managed Chrome session is fine. NOT for the user's real Chrome cookies/profile (see mk:chrome-profile); NOT for reusable Playwright specs (see mk:qa-manual).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement backend service changes: API contracts, service boundaries, auth integration, reliability and delivery checks. Use for backend/API handlers, services, webhooks, jobs, or backend architecture changes. Routes schema/migrations to mk:database; security review to the existing security workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python Invoke task automation for DTX website. This skill should be used when running repo commands, backend tests via Docker, database migrations, updating invoke tasks, Docker operations, or workflow automation. Supports dev/test/prod environments with run, exec, up, down commands. References docs/development/invoke-tasks.md for complete command reference.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load a skill profile to switch active plugin set. Use when user wants to focus on a specific workflow (web-app/data-eng/harness-dev/minimal) and reduce skill enumeration block size per
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / contributing / security policy", "Show HN", "release workflow", "star growth", "get contributors".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authorized testing of LLM applications, agents, chatbots, RAG systems, guardrails, and tool-using model workflows. Use for LLM mode selection, jailbreak and prompt-injection assessment, guardrail bypass review, tool misuse, tool or system prompt disclosure, data exfiltration paths, model refusal/stop detection, bypass hypotheses, and hardening guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically interpret a Medtronic CareLink or MiniMed 780G Daily Review download in a structured 6-step clinical workflow — covering Time in Range, insulin delivery, day/night patterns, hypo and hyperglycemia root causes, and a prioritised action plan. Trigger when a clinician uploads or shares a CareLink report, MiniMed download, 780G Daily Review, pump download, or asks to review a patient's CGM or insulin pump data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft a Workflow Phase 4 technical spec from an intake (and optionally a BRD + scout + research memo). The spec defines how the system will change: design (C4 + UML + dependency graph in PlantUML), data, APIs, tests, rollout, rollback. Output lives at `docs/specs/<slug>.md`. Never self-approves — approval happens via `/approve-direction`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Workflow Phase 3 — Research and Solution Exploration. Surfaces 2–4 candidate solution approaches with concrete tradeoffs, grounded in current library docs (fetched through the provider named in `.claude/docs-provider.json`) — never in training-data recall. Output lives at `docs/research/<slug>.md`. Candidate ranking and the memo execute in main context; doc/source gathering MAY be delegated to read-only advisory subagents (seed.md §4.2-A).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, `main`) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep, whenever the user asks "where does X come from?", "what API/data populates Y?", "what renders or wraps the Z panel?", "which file for feature F?", "how is this wired up?", or any code-navigation question mapping a UI element, route, or feature concept to source files. Also reverse queries ("what uses /api/foo?", "who consumes this service?"). Keyword search routinely picks up unrelated flows sharing a domain word and produces wrong answers; the walk follows the actual graph. The JS/TS `walk.mjs`/`discover.mjs` are an optional accelerator, not required — the walk is language-agnostic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Replace this with a precise trigger description. State the Amazon PPC workflow, user intent, required data, and when Codex or Claude should use this skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Planning] Use when a workflow step or the user asks for adversarial scenarios for failure, data integrity, access, replay and recovery risks before planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing data flows, support macros, refund templates for GDPR/CCPA/HIPAA fit — regime, consent, PII redaction (email, order-id), breach triage. Triggers 'is this GDPR-safe', 'PII redact'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for deep Node.js / Express project analysis: boot flow, middleware order, async behavior, data layer, auth/security, and Node-specific runtime failure patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for deep Zend Framework or Laminas project analysis: bootstrap, config merge order, service manager, MVC flow, data layer, and migration-specific risks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates complete newsletter editions for the Flow Factor Newsletter on Beehiiv. Generates full newsletter text (1,200-1,500 words), SEO metadata, subject lines, header illustration prompts, and NotebookLM audio briefing prompts. Use when user asks to write a newsletter, create email content, plan newsletter editions, or produce Beehiiv-ready content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when choosing .NET concurrency patterns for async I/O, queues, pipelines, or thread safety. Keywords: async/await, channels, dataflow, Rx, lock contention, producer consumer, parallel processing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refine an existing skill in place with minimal diffs. Trigger when asked to improve a skill's trigger description/frontmatter, workflow text, metadata, scripts/references/assets; also for requests to iterate, refactor, rename, or fix a skill using usage/session-mining evidence (for example from /tw-seq).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.