2.2천건 · 관련도순
Design performant animation systems with Framer Motion, GSAP, View Transitions API, and spring physics. Activate on: page transitions, micro-interactions, scroll animations, layout animations, spring physics. NOT for: CSS-only hover effects (use css-in-js-architect), video/canvas rendering (use creative-coding-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level idiomatic Rust API design — the patterns that make illegal states unrepresentable and abstractions zero-cost. Type-state programming (PhantomData state machines), newtype + sealed + extension traits, typestate builders, RAII guards & Drop ordering, the interior-mutability decision tree (Cell/RefCell/Mutex/RwLock/Atomic/OnceLock), enum-driven state machines, error architecture (thiserror vs anyhow), dyn vs generic dispatch & object safety, the impl Trait / GAT / RPITIT toolbox, and Deref-for-smart-pointers (and its abuse). Use when designing a Rust library's public API, encoding invariants in the type system, choosing a dispatch or error strategy, or reviewing Rust for idiom. NOT for borrow-checker firefighting / toolchain / test-runner workflow (use rust-development-workflow), NOT for pd-console GPUI rendering/layout/panes (use gpui-rust-console), NOT for app packaging/notarization (use rust-app-distribution).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full-site crawling, scraping, and site mapping via Firecrawl MCP. Use when user says "crawl site", "map site", "full crawl", "find all pages", "broken links", "site structure", "discover pages", "JS rendering", or needs site-wide analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WindowPanel (@ai-matrx/summon/window) and its window manager. Use when a window won't drag, resize, minimize or pop out, the tray or restore is wrong, rendering <WindowPanel> on a page, or editing features/window-panels/**. NOT for opening or registering overlays (use overlay-system).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Shape System — the content_ir kind registry for structured content. Use when adding, activating, or rendering a kind/shape, writing `__kind` JSON, kind schemas or samples, XML-tag/fence detection surfaces, kind components, workflow node input_kind/output_kind, or binding agent output to a kind.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Collapsing every copy of one kind of thing (tables, UIs, hooks, APIs, renderers) into a single canonical one. Use when asked to unify, merge, converge, or 'make one X used everywhere', before migrating callers onto a new canonical piece, or removing a duplicate component. NOT for docs (use docs).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rules for every string rendered inside the app, plus the sweep that removes in-app prose. Use when writing or changing a label, hint, description, tooltip, empty state or KPI tile in a .tsx file, or when running Pattern Patrol P14 or asked to find or fix long UI text.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The staged pipeline that turns any API, provider payload, scrape, or computed result into registered, rendered platform kinds. Use on 'create kinds for X', 'distill X into kinds', 'point yourself at API X', or as a stage (A/B/V/D/C) of a running data-to-kinds run. NOT for consuming existing kinds (use aidream's workflow-io-kinds / matrx-frontend's shape-system).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Printing and PDF export for AI response blocks and messages via @ai-matrx/print. Use when adding a print button or BlockPrinter to a render block, wiring PrintOptionsDialog/usePrintOptions, captureBlockElement, or useDomCapturePrint, or when a print window shows no images or a print fails silently.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Export a Remotion video
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds simple Three.js web apps with scene setup, lighting, geometry, materials, animation, and responsive rendering. Use when creating or prototyping 3D web scenes with modern Three.js (r150+).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, node materials, compute shaders, post-processing, and WGSL integration. Use when working with Three.js WebGPU, TSL shaders, or GPU compute pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Best practices for Remotion video creation in React. Use when building, reviewing, or optimizing Remotion compositions, animation timing, assets, captions, and render pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a running Spark or DSH web service needs real-browser verification — page load, client-plugin boot errors, console errors, failed requests, or onboarding/dialog rendering — with the repository's own Playwright chromium.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proves a Godot 4.x build is actually green and holds its project conventions. Trigger when a GUT or GDScript result needs believing (a suite green while a script failed to parse, a one-file run that ran the whole suite, drifted CI guard counts, a coverage claim, a gate figure, a failing check someone wants softened); to review scenes, signals, awaits, threads, determinism, saves, imports or .uid files, or the upgrade rule (not the migration); to prove a simulation or balance rule; for import settings and the pixel-art render precondition; or say godotsmith (check, guard, gate, review, intake). API reference is the Godot docs'; art reads pixelsmith's; audio direction soundsmith's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Directs screens and proves they fit — game menus and HUD, web dashboards, single-page artifacts, store-page layouts and plugin panes. Writes the design brief (layout, hierarchy, spacing and type scales, every state, focus and hit size, a check against generic-looking output) and probes the rendered page at phone-to-desktop widths in every theme. Trigger to design or lay out a menu, HUD, dashboard, settings screen or panel, or review its mockup before the build; when a page scrolls sideways on a phone, text is clipped or a dark theme breaks; to check that a page or pane fits from 320 to 1440 px in light and dark; for UI direction before a build, even when nobody says design; or say uismith (direct, probe, fit-first audit). The probe needs optional Playwright. A critique, scored review or brand pass of a built page, palettes and type are brandscribe's; sprites and icons pixelsmith's; Godot scene proof godotsmith's; words commscribe's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
使用 A2UI v0.8（以 renderers/lit/src/0.8 与 specification/0.8 为准）生成服务端 JSONL UI 消息，并实现客户端事件与 A2A 扩展回传。适用于把用户需求转成 A2UI 组件树+数据模型+渲染序列，以及处理 action/userAction 与后端接口调用的场景。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3D game development principles. Rendering, shaders, physics, cameras.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3D web graphics with Three.js (WebGL/WebGPU). Capabilities: scenes, cameras, geometries, materials, lights, animations, model loading (GLTF/FBX), PBR materials, shadows, post-processing (bloom, SSAO, SSR), custom shaders, instancing, LOD, physics, VR/XR. Actions: create, build, animate, render 3D scenes/models. Keywords: Three.js, WebGL, WebGPU, 3D graphics, scene, camera, geometry, material, light, animation, GLTF, FBX, OrbitControls, PBR, shadow mapping, post-processing, bloom, SSAO, shader, instancing, LOD, WebXR, VR, AR, product configurator, data visualization, architectural walkthrough, interactive 3D, canvas. Use when: creating 3D visualizations, building WebGL/WebGPU apps, loading 3D models, adding animations, implementing VR/XR, creating interactive graphics, building product configurators.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.