「interactions」の検索結果

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

日本語の概要は準備中です。原文の説明を表示しています。

Use when adding or fixing Formax tests (especially Ink UI tests) and you need deterministic synchronization in test interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-agent self-inspection of your AI-agent stack. Audits skills, MCP servers, hooks, plugins, commands, credentials, and memory files across Claude Code, Codex, OpenClaw, and NanoClaw. Produces a structured inventory and narrative briefing with cross-ecosystem risk analysis. Use when the user asks to audit their own setup, check what they have installed, review their agent stack security posture, or understand cross-tool interactions. Use when a user has accumulated skills/plugins/MCP servers over time and wants visibility into their attack surface. Use after installing new skills or plugins. Do NOT use for vetting external code before install (that is repo-forensics). Do NOT use for incident response during active attacks. Do NOT use for fixing or patching vulnerabilities (forensify is read-only).

日本語の概要は準備中です。原文の説明を表示しています。

CesiumJS interaction and picking - ScreenSpaceEventHandler, multi-key KeyboardEventModifier input actions, Scene.pick, Scene.drillPick, Scene.pickPosition, Scene.snap edge snapping (1.144), mouse and touch events. Use when handling user clicks on the globe, selecting entities or 3D Tiles features, registering modifier-key shortcuts, implementing hover effects, snapping to model edges for measurement, or building drag-based interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Stimulus JS framework for Symfony UX -- client-side behavior via HTML data attributes, zero server round-trips. Use when creating controllers for DOM manipulation, handling click/input/submit events, managing targets and values, wiring outlets between controllers, wrapping third-party JS libraries, or building toggles, dropdowns, modals, tabs, clipboard interactions. Code triggers: data-controller, data-action, data-target, data-*-value, data-*-class, data-*-outlet, stimulusFetch lazy, connect(), disconnect(), static targets, static values. Also trigger when the user asks "how do I add a click handler", "how to toggle a class", "how to build a dropdown/modal/tabs", "how to wrap a JS library in Symfony", "add keyboard shortcuts", "lazy-load a controller", "listen to global events", "communicate between controllers". Do NOT trigger for partial page updates without JS (use turbo), server-rendered reactivity (use live-component), or reusable Twig templates (use twig-component).

日本語の概要は準備中です。原文の説明を表示しています。

World-class motion design expertise combining Disney's 12 principles of animation, Material Design's motion system, and the performance-first philosophy of production interfaces. Motion design is the craft of bringing interfaces to life - not through decoration, but through clarity, continuity, and communication. Great motion design is invisible. Users don't notice the animations - they notice that the interface feels natural, responsive, and alive. Every transition tells a story: where did this come from? Where is it going? What just happened? Motion is the language of cause and effect in digital interfaces. Use when "animation, motion, transition, microinteraction, easing, timing, choreography, loading animation, skeleton loader, page transition, hover effect, scroll animation, spring animation, keyframes, framer motion, gsap, lottie, animation, motion, transitions, microinteractions, easing, timing, accessibility, performance, frontend, design" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding. Use when ", discord, bots, slash-commands, interactions, real-time" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 2025. Critical distinction: Testing automation (predictable apps you control) vs scraping/agent automation (unpredictable sites that fight back). Different problems, different solutions. Use when "playwright, puppeteer, browser automation, headless, web scraping, e2e test, end-to-end, selenium, chromium, browser test, page.click, locator, playwright, puppeteer, browser, automation, testing, scraping, headless, e2e, selenium, web-testing" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement agent-based models (ABM) for simulating complex systems with emergent behavior from individual agent interactions. Use when "agent-based, multi-agent, emergent behavior, swarm simulation, social simulation, crowd modeling, population dynamics, individual-based, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Map customer journeys from awareness to advocacy. Visualize touchpoints, identify drop-off points, analyze channel interactions, and optimize the end-to-end experience. Use when the user asks about customer journey, funnel mapping, touchpoint analysis, or experience optimization.

日本語の概要は準備中です。原文の説明を表示しています。

Plan integration tests across modules or services. Use when a mid-level developer needs to verify system interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Practical prompt patterns and techniques for effective Claude Code usage. Reference when crafting prompts, planning workflows, or debugging interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Read Bluesky/ATProto without depending on Bluesky's AppView — interactions on a user's posts, thread replies, any repo's records, network-wide backlinks across every lexicon, an account's handle and PDS history, which collections are active network-wide, and layer-by-layer outage diagnosis. Use when bsky.app or the AppView is down or slow, when a Bluesky read returns timeouts or 5xx, when asked who liked/replied/quoted/reposted something, when pulling live Bluesky context cheaply, when reading records straight from a PDS, when asked who references a record or account anywhere on the network, whether an account has changed handle or migrated servers, or which lexicons and non-Bluesky apps are active on atproto. Complements browsing-bluesky, which routes everything through the AppView and fails when it does.

日本語の概要は準備中です。原文の説明を表示しています。

Design adaptive layouts and interactions that work across all screen sizes and input methods.

日本語の概要は準備中です。原文の説明を表示しています。

Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.

日本語の概要は準備中です。原文の説明を表示しています。

Design gesture-based interactions for touch and pointer devices.

日本語の概要は準備中です。原文の説明を表示しています。

Apply animation principles to UI motion for purposeful, polished interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever reasoning about immunology, host-pathogen interactions, innate immunity, Toll-like receptors (TLRs), or experimental design in molecular biology. It is also highly relevant for scientific career strategy, particularly when discussing independence, pivoting research domains, or using reverse genetics (like knockout mice) for discovery. Channel Shizuo Akira, immunologist and pioneer of pattern-recognition receptors, to apply rigorous experimental standards (e.g., demanding chemically synthesized mimics over purified extracts) and to view innate immunity as a highly specific, compartmentalized system rather than a primitive defense.

日本語の概要は準備中です。原文の説明を表示しています。

Design tactile interaction feedback and timing.

日本語の概要は準備中です。原文の説明を表示しています。

Perform QA testing on running web applications using cmux_browser. Covers functional testing, accessibility auditing, edge case testing, and structured reporting with evidence. **Triggers — use this skill when:** - User says "test this", "QA this", "QA this PR", "check the app" - User says "run QA", "verify the build", "test the UI" - User asks to "check if it works", "validate the feature" - User says "acceptance testing", "smoke test", "regression test" - User asks to "find bugs", "test for bugs", "break it" - User wants to "check accessibility", "run axe", "a11y audit" **Covers:** Any web application accessible via HTTP. Uses cmux_browser (Playwright under the hood) for all browser interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Encode Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great. From the creator of Sonner (13M+ weekly npm downloads), Vaul, animations.dev, and Linear's web team. Use when user wants to polish UI, audit animations, review component interactions, add micro-feedback, or elevate motion quality.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to turn a static scene, character images, aerial map, drawn path, or route-control image into an immersive first-person FPV AI video prompt, especially Seedance/Kling/Runway/Veo style one-shot videos with numbered stop markers, red-line path control, world-map flythroughs, camera route planning, variable character counts, non-human POVs such as drones, pets, robot vacuums, character references, timed interactions, dialogue, spatial audio, and negative constraints.

日本語の概要は準備中です。原文の説明を表示しています。

Implementing CSS/JS animations for hover effects, loading states, modal transitions, and gesture interactions. Use for meaningful motion, interaction feedback, or performance-safe animation.

日本語の概要は準備中です。原文の説明を表示しています。