738건 · 관련도순
Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize, categorize, rename, and manage files systematically using automated rules, naming conventions, and folder structures for efficient file management. Use when organizing uploaded files, implementing file naming conventions, categorizing files by type or metadata, creating folder structures, cleaning up messy directories, automating file movements, implementing media libraries, or building file management systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring techniques like extracting functions, removing duplication, simplifying conditionals, and applying design patterns. Use when reducing technical debt, extracting functions or classes, removing code duplication, simplifying complex conditionals, renaming for clarity, applying design patterns, improving code organization, reducing coupling, increasing cohesion, or maintaining test coverage during structural improvements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically review pull requests, feature implementations, and code changes to ensure quality, maintainability, security, and adherence to best practices. Use when reviewing code before merging, conducting peer reviews, performing self-reviews, auditing code quality, checking for security vulnerabilities, ensuring consistent coding standards, verifying test coverage, assessing performance implications, evaluating architectural decisions, or providing constructive feedback to improve team code quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about CMV maintenance program requirements under 49 CFR 396.3 — what records must be kept, retention periods (12-18 months on vehicle file + 1 year after disposal), what counts as systematic inspection/repair/maintenance, preventive maintenance scheduling, brake adjustment records, and what auditors look for in vehicle files. Cite 49 CFR 396.3 + 396.21.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when conducting a self-audit of your DQF library before an FMCSA compliance review. Covers the systematic approach to verifying all 12 documents are current, complete, and properly maintained.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert debugger for Next.js + Cloudflare Workers + Supabase stacks. Systematic troubleshooting for auth, caching, workers, RLS, CORS, and build issues. Activate on: 'debug', 'not working', 'error', 'broken', '500', '401', '403', 'cache issue', 'RLS', 'CORS'. NOT for: feature development (use language skills), architecture design (use system-architect).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction design across any domain (portfolios, e-commerce, SaaS, adult content, technical showcases). This skill should be used when users need exhaustive design research, pattern recognition across large example sets, or systematic visual analysis for competitive positioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify and counteract cognitive biases in medical decision-making through systematic error analysis and contextual algorithm application. For diagnostic reasoning, treatment decisions, and clinical judgment improvement. NOT for basic medical knowledge, technical procedures, or non-clinical healthcare domains.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement systematic checklists that reduce errors by 30-50% in complex, high-stakes domains (medicine, aviation, construction, finance). NOT for simple tasks or when comprehensive instruction is needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic framework for resurrecting and modernizing legacy codebases through archaeology, resurrection, and rejuvenation phases. Activate on "legacy code", "inherited codebase", "no documentation", "technical debt", "resurrect", "modernize". NOT for greenfield projects or well-documented active codebases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic methodology for eliciting, representing, and operationalizing expert cognitive skills—pattern recognition, situation assessment, mental simulation—from practitioners without requiring research training. Bridges academic rigor and practical usability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic methodology for eliciting, representing, and operationalizing expert cognitive skills—pattern recognition, situation assessment, mental simulation—from practitioners without requiring research training. Bridges academic rigor and practical usability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.