'does' 검색 결과

Generate an interactive HTML brand playground that shows your brand rendered live — palette, typography, logo, voice — with a social card and OG image preview that updates as you tweak tokens. Opens in browser. The visual approval step for the /cmo flow: /visual-style writes the brand, this skill shows it. Use when the user says "show me my brand", "brand playground", "preview my brand", "what does our brand look like", "visual preview", "brand kit", "see my colors", "how does my brand look", or after /visual-style completes and the user needs to approve the visual identity before moving to content generation. Also use when someone says "I want to see it" during any brand-building conversation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

A zero-risk first Cowork experience for discovering what Cowork does differently. Use when onboarding to Cowork, for getting started safely, during first-time exploration, when starting fresh with a new AI tool, or when the user says "I am new to Cowork", "first task", "show me what Cowork does", "what can you do that Chat cannot", "help me get started", or "safe first task".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sets up a file-based memory system so Cowork always knows who you are, how you work, and where your projects stand. For eliminating repetitive re-introductions at session start, when building persistent context across multiple projects, or during initial Cowork onboarding. Use when the user says "claude doesn't remember me", "memory system", "persistent context", "why does it forget", "remember my preferences", "I keep re-explaining myself", or "how do I make Claude remember things".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to know where a piece of reporting actually came from — the user gives an article URL and asks "where does this come from?", "who is the original source?", "is this just a rewrite?", or another skill needs the provenance chain before grading or citing a report. Follows an article's links and named attributions back to the originating vendor, government, victim or actor document and returns the chain, the primary's stated access and confidence language, publication dates, and every hop it could not resolve. Deterministic — a script or the Liberty91 platform resolves the chain; the model does not reconstruct it from memory. Invoked by /quality-of-information-check, /threat-actor-profiling, /campaign-tracking and /intelligence-writing. Works on any URL with no API key.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a report or article needs to be split into individual claims before it is graded, cited or used as evidence — the user asks "what does this report actually claim?", "split this into claims", "separate the facts from the judgements", or another skill needs a claim list. Turns one document into five to twelve atomic claims, each typed (observation, attribution, assessment, actor claim, victim disclosure) and anchored to the verbatim sentence it rests on, so every extraction can be checked against the source. Preserves the source's own hedging. Does not grade. Invoked by /quality-of-information-check; its output feeds /ach, /key-assumptions-check, /intelligence-writing, /writing-assessments and /threat-actor-profiling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply cultivation theory (Gerbner) to analyze how long-term media exposure shapes worldviews. Use this skill when the user needs to study cumulative media effects on audience beliefs, evaluate mainstreaming and resonance phenomena, or assess how media consumption patterns correlate with perceptions of social reality — even if they say 'does watching news make people more fearful', 'how does media shape worldview', or 'mean world syndrome'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply Affordance Theory (Gibson, 1979; Norman, 1988) to analyze the action possibilities that an artifact provides to an actor. Use this skill when the user needs to evaluate technology design from an affordance perspective, identify why users struggle with an interface, analyze IT-enabled organizational change through affordance actualization, or when they ask 'what does this technology afford', 'why can't users figure out this feature', or 'how does technology enable new practices'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply Consumer Culture Theory to analyze consumption as a cultural practice shaped by identity, marketplace cultures, and ideology. Use this skill when the user needs to interpret consumer behavior through cultural lenses, analyze brand communities or subcultures of consumption, decode marketplace ideologies, or when they ask 'why do consumers behave this way culturally', 'what does this consumption mean', or 'how does identity shape buying'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Focused single-target audit of one Gaia skill, named skill, or real-skill catalog item. Use this skill when: auditing a specific skill by ID or name, a skill looks overpromoted, evidence feels thin or dead, a contributor's skill seems outdated or superseded, the rank doesn't match the source quality, evidence is mapped to the wrong Evidence Type, a skill at 3★+ is missing a working GitHub link, someone asks "does this skill deserve its stars?", or you want the smallest possible correction with validation — not a bulk sweep. This is NOT for bulk curation passes (use /gaia-curate for that) or meta-level registry sweeps (use /gaia-meta-audit). It is specifically for "fix this one skill, get it right."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pulp in the browser — the WAM v2 and WebCLAP adapters, the wasm runtime, the Skia/WebGL2 browser window host, and the WebGPU (emdawnwebgpu) GPU-audio lane. Covers what does and does not compile to wasm, the worklet-thread constraints (no std::thread, no fetch, no navigator.gpu), the non-realtime tick, memory growth, how to PROVE a GPU lane actually ran rather than silently falling back to CPU, and the silent-failure traps that make a wasm build "work" while producing no audio or no pixels.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Building and shipping a Forge app (Modular, Instrument, MIDI, FX, and the sequencer work to come) as a signed installer somebody else can actually use. Covers the seam between the Forge and Pulp repos, what a green signal does and does not prove, shipping the runtime rather than only the binary, and the wiring gaps that make a finished feature behave like a missing one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug or validate Pulp animations / transitions / scroll behavior using in-process motion fixtures and offline visual analysis. TRIGGER on phrases like "animation is wrong", "transition timing off", "fade too late", "card slides too far", "scroll jumps on restore", "scroll offset wrong on restore", "frame jump in the timeline", "easing looks wonky", "imported Figma motion doesn't match source", "settle time / overshoot / drift / monotonic", "what value does the knob reach at frame N", "record this animation so I can replay it", "this animation is expensive — which one and why", "reduced-motion broken", "scrub a captured fixture". Captures fixtures (.motion.jsonl), and ships assertion helpers (is_monotonic / settling_time_seconds / overshoot / start_delay_seconds / final_value / local_step_outlier_ratio) and the `scroll_geometry` trace for `ScrollView` content-offset / visible-rect / content-size observability. Off by default in prod.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explains DSP math concepts to developers who need the theory behind an algorithm. Use whenever the user asks how a signal-processing concept works, wants intuition behind a formula, or hits a math-shaped bug. Trigger on phrases like "how does a Fourier transform work", "explain z-transforms", "what is convolution", "why does my biquad ring", "what is windowing for", "what causes aliasing", or "how do I convert gain to dB". Also trigger when the user pastes DSP code and asks why it behaves a certain way.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Traces and documents signal paths, bus/aux architecture, and sidechain connections in audio systems. Surfaces hidden coupling between audio components. Use when the user asks to trace a signal chain, explain audio routing, understand an audio graph, locate sidechain sources, or describe how audio flows through a plugin or engine. Trigger on phrases like "trace this signal chain", "explain this audio routing", "what calls what in this audio graph", "where does the sidechain come from", "how does audio flow through this plugin".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants to transact on any Volcengine commercial product — purchase/provision it, ask what it costs, or unsubscribe from it. Covers three actions: buy (purchase, subscribe, provision, open, place an order; Chinese "开通 / 购买 / 下单 / 买 / 售卖 / 订购"), price (how much does it cost, quote, billing rules, estimated spend; Chinese "多少钱 / 价格 / 报价 / 费用 / 怎么收费 / 如何计费 / 预估费用"), and unsubscribe (cancel a subscription, refund a prepaid instance; Chinese "退订 / 退款 / 取消订阅"). Trigger even when the user does not mention "sale" but expresses a clear purchase, pricing, or cancellation intent toward a Volcengine product. Only handles these three transaction actions; anything outside them is out of scope.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find every LLM workflow in the current repository and label it, so Caveman Cloud groups spend by what the code actually does (support-reply, nightly-digest) instead of one anonymous bucket. Use when the user pastes the Caveman discovery prompt, says "discover workflows", or asks to break LLM spend down by workflow. The repo should already route through the Caveman gateway (the caveman-setup skill does that part).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Document a machine learning model in a structured, transparent format for stakeholders, reviewers, and future maintainers. Use when the user says "document this model", "write a model card", "model documentation", "how should I document my ML model", "bias and fairness report", "model transparency", "what does this model do", "model handoff", "production model documentation", or needs to communicate what a model does, how it was built, where it works, and where it fails.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze and interpret financial statements to surface performance signals, quality concerns, and red flags. Use when an accountant says "review these financials", "analyze the income statement", "look at the balance sheet", "what does the cash flow statement tell us", "check the financial health", "ratio analysis", "are the earnings real", "working capital review", "does this company have liquidity issues", or needs to interpret any of the three core financial statements - even if they don't explicitly say "financial statement review". Also trigger when someone shares P&L, balance sheet, or cash flow data and asks what it means.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Entry point for the SfSkills Salesforce library: 1,040 skill packages across 11 domains (admin, agentforce, apex, architect, data, devops, flow, integration, lwc, omnistudio, security), 70 run-time agents and 94 slash commands. Use for any Salesforce, Force.com or Lightning Platform question — Apex, SOQL, SOSL, triggers, Flow, LWC, sObject, custom field, permission set, profile, sharing rule, validation rule, deployment, sandbox, Agentforce, OmniStudio, org setup. This skill does not answer Salesforce questions itself; it routes to the specific skill package that does, then hands off to a domain router.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Understand what Skmtc is, how its engine works, and the architectural invariants — for agents building or extending infrastructure *around* Skmtc rather than authoring generators or running the CLI. Covers the three-phase pipeline, the host/Worker boundary, cross-generator coordination, the manifest, the attribution / gen-maps (provenance) subsystem, the package graph, the Deno and JSR platform, and the design decisions that make Skmtc behave unlike a typical codegen tool. Use this skill when the user asks "what is Skmtc", "how does the Skmtc engine work", "explain the Skmtc architecture", or is building platform infrastructure around Skmtc — a hosted generate API, a schema or generator registry, tracing or provenance tooling, a web app or SaaS that wraps the engine, or platform-level CI integration. This skill is the system mental model. It does NOT cover authoring generators (→ skmtc-generator), running CLI commands (→ skmtc-cli), or diagnosing broken runs (→ skmtc-debug).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.