2.8천건 · 관련도순
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other frontends.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes bounded context boundaries in DDD projects. Detects cross-context coupling, shared kernel violations, context mapping issues, and ubiquitous language inconsistencies. Generates context map diagrams and boundary recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Accessibility audit for CSS covering focus styles, color contrast, text sizing, screen reader support, and WCAG compliance. Provides actionable fixes. Use when auditing accessibility or fixing a11y issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sentry error tracking and monitoring for OneKey. Use when configuring Sentry, filtering errors, analyzing crash reports, or debugging production issues. Covers platform-specific setup (desktop/mobile/web/extension) and error filtering strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Development commands for OneKey monorepo. Use when running dev servers, building apps, linting, testing, or troubleshooting build issues. Triggers on yarn, dev, build, lint, test, desktop, mobile, web, extension, ios, android, compile, bundle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this to view the timeline of GitHub issues or pull requests. Note that it does not fetch the title and description, unlike `gh pr view`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
status:ready な issue に対して issue-implementer agent を並列起動し、実装→PR作成を行う
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
status:needs-investigation な issue を並列調査し、結果をコメントして status:investigated に更新する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs the daytime maintainer loop for NemoClaw, prioritizing items labeled with the current version target. Picks the highest-value item, executes the right workflow (merge gate, salvage, security sweep, test gaps, hotspot cooling, or sequencing), and reports progress. Use during the workday to land PRs and close issues. Designed for /loop (e.g. /loop 10m /nemoclaw-maintainer-day). Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Describes the NemoClaw plugin and blueprint architecture and how they orchestrate the OpenClaw sandbox. Use when looking up architecture, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw plugin blueprint structure, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete knowledge domain for Firecrawl v2 API - web scraping and crawling that converts websites into LLM-ready markdown or structured data. Use when: scraping websites, crawling entire sites, extracting web content, converting HTML to markdown, building web scrapers, handling dynamic JavaScript content, bypassing anti-bot protection, extracting structured data from web pages, or when encountering "content not loading", "JavaScript rendering issues", or "blocked by bot detection". Keywords: firecrawl, firecrawl api, web scraping, web crawler, scrape website, crawl website, extract content, html to markdown, site crawler, content extraction, web automation, firecrawl-py, firecrawl-js, llm ready data, structured data extraction, bot bypass, javascript rendering, scraping api, crawling api, map urls, batch scraping
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic performance profiling and optimization methodology. Covers CPU profiling, memory profiling, heap analysis, goroutine/thread analysis, FlameGraph generation, latency profiling, database query profiling, network I/O profiling, and continuous performance regression detection. USE WHEN: investigating performance issues, optimizing slow code, reducing memory usage, diagnosing GC/CPU bottlenecks, finding N+1 queries, analyzing pprof/flamegraph output, or establishing a performance baseline. Triggers on "profiling", "performance analysis", "slow code", "flame graph", "pprof", "heap dump", "memory leak", "CPU spike", "bottleneck".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adds debugging capabilities and troubleshoots Pine Script issues in TradingView's opaque environment. Use when scripts have errors, unexpected behavior, need debugging tools added, or require troubleshooting. Triggers on "debug", "fix", "error", "not working", "wrong values", or troubleshooting requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and run multi-agent content production teams on OpenClaw with single-repo architecture, symlink-based file sharing, role-specialized AGENTS.md, and automated review-fix-score loops. Use when: (1) Setting up a team of 3+ agents with writer/reviewer/scorer/fixer roles for content creation, (2) Creating a quality-controlled publishing pipeline, (3) Bootstrapping agent workspaces with symlinks and tool configs from scratch, (4) Running multi-round review→fix→score cycles until a quality threshold is met, (5) Debugging agent spawn permissions, tool-call loops, or symlink issues. Based on real production experience building a 6-agent content team (2026-03-30).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.