1천건 · 관련도순
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. Based on Anthropic's Frontend Designer Skill
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates sustainability-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify environmental impact requirements, and provide actionable recommendations to build, deploy, and manage the workload sustainably in Google Cloud.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search, score, and compare flights with jetlag impact analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for prioritization, or when there are more tasks than capacity: "what should we do first?", "rank this backlog", "cut scope for the MVP", "RICE score these". Picks a method (RICE, ICE, MoSCoW, impact-effort), scores items and sets a cut line. Skip for choosing between two designs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design randomized controlled trials for causal inference. Use when user mentions: randomized evaluation, RCT, field experiment, randomized experiment, treatment assignment, causal impact, experimental design, control group, intervention evaluation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Low-ceremony workflow for trivial, low-risk changes: typos, comments, CSS/styling tweaks, string changes, single-line fixes with no logic impact. Use to avoid the overhead of the full feature workflow when the change cannot break anything. If during the fix the change turns out to touch logic, security, config, or schema, stop and escalate to the feature-workflow skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely develop, verify, and document proof-of-concept exploits and payloads for authorized targets inside isolated Workspace Containers. Use when a Hypothesis is well-founded, target authorization covers scope, and each active step will carry a durable approval — for minimal PoCs, impact verification, or reproducible exploit Evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recommends ACTH stimulation during AVS to improve success rate of bilateral selective catheterization, acknowledging unclear impact on diagnostic accuracy for laterality. Triggers include when setting up AVS and asking 'Should I administer ACTH?' or considering procedural optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate the gatOS mod against a new upstream Kitten Space Agency (KSA) game build — the break-check playbook run when the KSA game / its decompiled sources are bumped and you must decide whether gatOS needs changes. Covers exactly which gatOS surface couples to KSA and where, how to diff the CURRENT (new) vs PREVIOUS (old) decompiled sources, build-as-alarm, semantic-drift review, the reflection + render-internals coupling the compiler can't catch, and which docs to update in lockstep. Use when asked to "check gatOS against the new KSA build", "upgrade KSA", run the version-diff / break-check, or review a game update's impact. REQUIRES two KSA decompiled-source trees to be provided: CURRENT and PREVIOUS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level transportation engineering covering highway design, traffic flow, intersection design, pavement design, traffic impact studies, and public transit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use BEFORE writing any test — enumerate cases per behavior (happy / boundary / error / abuse), prioritize by likelihood × impact, cross-check via subagent — even if the user just says 'add tests'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when ranking competing initiatives for a roadmap, breaking a tie between two features, or auditing a backlog for hidden low-value work via Reach × Impact × Confidence ÷ Effort.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When shaping feedback — situation-behavior-impact, growth-vs-corrective split, cadence design, ladder-of-inference checks. Triggers on 'how do I give this feedback', 'perf review shape'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Fix & Debug] Use when a workflow step or the user asks for read-only code-flow investigation. --mode=debug finds bug root causes; --mode=explain narrates purpose, flow and impact. Plans/decisions: understand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consulte o banco de dados de grafo de código para entender relacionamentos de componentes, dependências e impacto de mudanças. Use quando o usuário pedir para "encontrar chamadores", "verificar dependências", "o que usa isso", "mostrar relacionamentos", "encontrar serializadores", ou ao ler código e precisar entender o que depende de um componente antes de fazer modificações.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks. Guides an agent through the complete lifecycle of making architectural decisions, documenting them, writing FAQs, and cleaning up stale plans while adhering strictly to repo ethics and brand tone. Use whenever you need to make a structural change, write an ADR, update the doc lattice, or govern repository architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when work produces a deliverable, factual claim, dataset, code change, decision, publication, deployment, automation, or irreversible action whose failure would matter; when the user asks for a quality gate, acceptance criteria, QA, completeness, validation, audit, evidence, preflight, release readiness, or a definition of done; or before claiming completion on medium- or high-risk work. Automatically decide whether a formal gate is warranted, derive task-specific pass/fail criteria, gather evidence, and block unsupported completion. Make sure to use this skill even when the user does not say "quality gate" if consequential work needs acceptance criteria or completion evidence. Skip formal gating for trivial, reversible, low-impact requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company with a security applicability statement extends its management system to privacy or to AI, and asks "extend our SoA for privacy", "which privacy controls apply to a processor", "AI controls applicability", "SoA for our AI management system", "are we controller or processor for this" or "do the AI development controls apply if we only use a model". Settles the company's role per processing activity and per AI system, decides applicability of the additional controls from those roles and the risk or impact assessments, and writes an extension to the applicability statement plus role and scope notes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.