'surface' 검색 결과

Land a change everywhere the same fact is stated — enumerating the full surface inventory (landing copy, docs, machine-readable summaries, changelog badges repeated across every page, sitemap, README, descriptions embedded in code, and untyped frontend consumers of typed responses), generating a surface instead of restating it, drift tests where you cannot generate, never hand-maintaining a copy of a surface another codebase owns, shipping a paired PR when you change a format a different codebase decodes, and keeping overloaded product words apart. Use when adding or renaming a user-facing feature, editing product/marketing copy or docs, renaming a serialized response field, changing a serialization or share-link format, wiring one repo's output into another's checks, or reviewing a PR that touched only one place a fact appears.

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

Use when the user mentions Marketing Studio, DTC Ads, ad video, UGC video, the marketing_studio_video MCP model, or wants to generate one of the 9 Marketing Studio ad presets (UGC, Tutorial, Unboxing, Hyper Motion, Product Review, TV Spot, Wild Card, UGC Virtual Try On, Pro Virtual Try On). Also triggers on hook+setting picklist questions, preset-avatar / custom-avatar / text-generated-avatar handling, 4–15s ad video questions, or any reference to Higgsfield's ad-video product surface. Cross-surface workflow handoffs (GPT Image 2.0 / Soul Cinema / Nano Banana Pro / ms_image image gen → Marketing Studio video) covered in the companion cross-surface-workflow.md. Also use for Ad Multiplier (`ad_multiplier` — 'multiply my ad', many independently edited versions of one supplied 4–30s ad) and for Genjutsu one-off edits of a finished ad (swap one object / product / garment → `hf_mult_replace_object`; transfer motion → `hf_mult_motion_control`).

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

Checkable-ish surface presentation signals a reviewer notices first — duplicate/near-identical tables, leftover pipeline/template strings, too-few or LLM-looking figures, and page-padding. AUXILIARY ONLY and weak by design: a deterministic pass (tools/check_presentation.py — dup-table + pipeline-artifact) plus a fresh cross-model GROSS-cases-only semantic pass (thin-float, LLM-figure, page-padding), every above-info finding span-anchored to the evidence ledger (claims.json). The adjudicator CAPS everything at minor (SURFACE_ONLY_SKILLS + SURFACE_PATTERNS) — these contribute at most SOFT_FLAGS, never a HARD verdict — default false_positive_risk:high. NOTE: the pure AI writing-STYLE impressions (AI-flavor prose, defensive 'not-X-but-Y' hedging, narrative-arc, jargon-stuffing, invented codenames) MOVED to the zero-verdict-weight AIS track — for those use skills/ai-style-impressions, NOT this. Emits presentation-signals.findings.json; NEVER computes the verdict. Triggers: "presentation signals", "surface check", "duplicate tables", "排版信号".

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

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

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

Evaluates implied volatility surfaces with skew analysis, term structure dynamics, and surface fitting methodologies. Use when analyzing vol surfaces, assessing skew dynamics, or calibrating volatility models.

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

Entry point for rafter. Invoke when a sub-skill is unclear, or when the task needs `rafter run` (remote SAST+SCA), `rafter secrets` (local secrets-only), `rafter agent audit`, policy checks, or command-risk evaluation. Scope by security surface, not task label: engage when the diff touches auth, credentials/secrets/tokens, untrusted input, SQL, shell/exec, file paths, deserialization, crypto, network endpoints, data deletion, or dependencies; for research/experimental/local-only code with none of that, a quick surface check is enough. When such surface IS present and no rafter skill or CLI call has been made, invoke this before handing the task off — an un-evaluated "done" on genuine security surface is not done.

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

Enterprise-specific view across CopilotKit + AG-UI. "Enterprise" here = CopilotKit's COMMERCIAL surfaces (Premium / CopilotKit Enterprise / Intelligence Platform / paid tiers), NOT CopilotKit running inside a big company. Tracks the commercial product surfaces (from product-surface-scan — Enterprise Intelligence, Cloud, self-host license, threads/persistence tier, Inspector, premium UI/Angular SDK, analytics, security bundle, Slack/Teams), applies the free-vs-paid classifier to decide if an issue belongs here, surfaces cross-page product contradictions, and tracks enterprise questions/complaints, community-sourced prospects (with a sales owner), and enterprise reporters with prior-week trend. Elevated to the top of the weekly report. Runs standalone ("who's at enterprise this week") or invoked by weekly-report. Triggers on "enterprise report", "enterprise signals", "enterprise status", "who at enterprise this week".

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

Configure images and videos as surface textures in Three.js, and use environment images for backgrounds and reflections. Adjust placement, color settings, repetition, and filtering, then manage texture memory through compression, reuse, and disposal.

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

• Adjust image placement and tiling on 3D surfaces
• Use HDR images for backgrounds and reflections
• Apply video or Canvas content to a 3D surface

Track gaps between regulatory requirements and company policies, including owners, deadlines, and remediation status. Surface overdue and aging items, record resolutions or accepted risks, and prepare Slack notifications that require explicit confirmation before sending.

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

• Reviewing open policy gaps by owner and deadline
• Recording gaps found by policy-diff
• Sending confirmed Slack reminders to gap owners

Apply subtle gradient borders to cards, pricing panels, buttons, and other web surfaces. Choose layered CSS backgrounds or a masked border to suit existing designs, with guidance on Tailwind syntax, corner alignment, opacity, and light and dark themes.

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

• Adding subtle borders to cards and pricing panels
• Decorating edges without replacing a complex background
• Adding brand accents to hover and focus states

Build a scanning entrance for Three.js models, revealing their wire structure before the solid surface appears. Coordinate both layers with one expanding wave, then remove the temporary wires when the animation finishes.

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

• Introduce a 3D model with a radial scan
• Show a model's structure before its surface
• Create a holographic assembly effect

Add underwater sunbeams to a Three.js scene, with rippling light patterns, a shimmering surface viewed from below, and matching illumination on fish. The beams shift against objects as the camera moves, giving the water depth.

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

• Add sunbeams to an underwater scene
• Render a rippling water surface from below
• Light swimming fish as they cross beams

Create wood surfaces in Three.js using a single material with code-generated grain, pores, end grain, and finishes. Coordinate color, roughness, and surface relief to improve close-up detail and reduce visible repetition across boards.

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

• Creating wood grain for furniture, floors, and tool handles
• Adding pores and end-grain detail for close-up views
• Adjusting oil, wax, and lacquer finishes

Coordinate defect image generation, augmentation, and labeling for circuit board, metal surface, and glass inspection on OSMO. Select workflows that create initial board datasets from CAD scenes, process real images, or fine-tune NVIDIA Cosmos AnomalyGen models.

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

• Creating initial circuit board inspection datasets from CAD scenes
• Generating circuit board texture and component pose defects
• Running inference and labeling on real inspection images

Use when the user asks to "check if our surfaces have drifted from the canon", "watch for competitor repositioning", or "define when we should reposition"; produces a drift report — self-drift per flagship surface vs the narrative-registry canon over time (via wayback.py, change history Measured with as-of dates), competitor-repositioning alerts, an explicit repositioning-trigger condition set, and a D1/W1/M1 message-shift retro (intended vs actual pull-through, evidence-labeled) — feeding the TALE L drift-audit sub-items and the narrative-whiplash guardrail fact base. Not for the first-time consistency check before a surface ships — use narrative-cascade-planner; not for computing the TALE profile result or running the vetoes — use narrative-quality-auditor; not for echo-rate / AI-answer resonance measurement — use narrative-resonance-monitor. 自漂移监测/竞品重定位告警/重定位触发/叙事漂移复盘

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

Doctrine for designing and evolving any **SDK** Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface rejects the wrong contents and keeps the package testable in isolation. Default is "core, not customizable"; customization is the exception, defended by a deciding table. Use when authoring or evolving any such surface — `@grida/*` published packages, engine crates (gridaco/nothing `crates/*`) published or FFI-exported, intent/message vocabularies, any contract a second author will compile against. Internal-only helper packages are welcome to follow, not forced. Companion skill for two-sided contract work: $sdk-seam. Critique partners: $pedantic, $etiology. Related: $naming.

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

Decide when and how your product and communications must (or should) label AI-generated content, and write the disclosure policy — surface-by-surface rules, exact label wording, and the review trigger for regulations like the EU AI Act's transparency obligations. Use when asked 'do we have to label AI content', 'write our AI disclosure policy', 'are we covered for the AI Act', or when marketing/support/product start shipping AI-generated output. Produces a disclosure policy with a per-surface matrix and ready-to-use label copy. Not legal advice.

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

Use when modeling hard surface in ZBrush 2026 (sci-fi helmet, weapon, prop, armor plates, mechanical parts, kitbash, vents, panel lines, bolts, concept to game asset), when using ZModeler, Dynamic Subdivision and creasing, Live Boolean, Knife, Clip, Slice or Trim curves, IMM, ArrayMesh, NanoMesh or Panel Loops, or when edges look razor sharp, a Make Boolean Mesh fails or leaves holes, planes look wobbly, Mirror And Weld erased an edit, or ZRemesher ruins a hard-surface part.

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

Expert knowledge for Azure External Attack Surface Management development including configuration. Use when filtering EASM inventory by ASN, domains, hosts, IPs, pages, SSL certs, or exporting findings to analytics tools, and other Azure External Attack Surface Management related development tasks. Not for Azure Defender For Cloud (use azure-defender-for-cloud), Azure Security (use azure-security), Azure Sentinel (use azure-sentinel), Azure Networking (use azure-networking).

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

Decision protocol for wrapping a REST / GraphQL / RPC API as a tool an LLM agent can call. The load-bearing premise: the *tool surface* is an LM-friendly subset of the *API surface* — one tool per user intent, not one per endpoint. Activates when a coder agent must expose an external HTTP API to a model (function calling, tool_use, MCP, LangChain `@tool`, CrewAI `BaseTool`). Encodes the *what to surface, how to name, how to shape, how to fail* — not any single framework's API. ~80% of agent tools in production are HTTP wrappers; this is the SOP for getting them right.

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

AAA hard surface modeling for sci-fi, industrial, military, vehicles, weapons, robotics, and mechanical props. Use for boolean/bevel workflows, panel lines, greebles, chamfers, and manufacturing-accurate surfaces in Blender via MCP.

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

Build and refine production Blender geometry through semantic vertex/edge/face editing, BMesh, subdivision control cages, Boolean construction, Displace relief, remesh, sculpt preparation, retopology, and deliberate surface connections. Use after blockout for hard-surface, product, organic, architectural openings, terrain/relief, or reference-driven assets when shape quality, topology, continuity, or realistic part integration matters.

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

OWASP Amass maps an organization's external attack surface: it finds subdomains, IP addresses, netblocks and ASNs from passive sources and active DNS techniques and stores them in an asset database. Use when: comprehensive subdomain enumeration, attack surface discovery, finding forgotten hosts before a pentest, tracking newly appeared assets, building a graph of target infrastructure.

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

Suede Labs copy-only orchestration DAG. Use for one high-stakes piece strangers will read that has to be true: a landing page, launch post, blog post, email, X thread, docs page, README, ad, or store listing, researched, fact-audited, adversarially reviewed, and gated for publish readiness in one pass. The audit targets what the agents invent, never what the requester supplied: their own statements are given, and no phase may verify, hedge, or gate on them. Reads the live surface; never publishes. NOT FOR: multi-surface campaign writing (use johnny-suede-write); changing code (use suede-graph-flo-xr); one surface in one pass with no research (use suede-copy); stripping AI patterns from existing text (use suede-deslop); bulk generation of many independent pieces (private Suede Labs companion, not in this pack: suede-codex-fleet).

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