UI/UX、ロゴ、スライド、画像生成（7,403 件）
概要と使いどころ
Hunts for Active Directory credential and replication attacks — DCSync, Golden/Silver Ticket, and DCShadow — by analyzing directory-service-access (4662), Kerberos TGS (4769), and logon (4624) events for replication abuse and forged-ticket anomalies. Activates for requests to hunt DCSync, detect golden/silver tickets, or find Active Directory replication abuse.
日本語の概要は準備中です。原文の説明を表示しています。
Establishes behavioral baselines from historical telemetry (process, network, or logon events) so hunts can flag rare and first-seen activity instead of relying on static signatures. Activates for requests to build a telemetry baseline, find rare or first-seen activity, or compute frequency baselines for anomaly hunting.
日本語の概要は準備中です。原文の説明を表示しています。
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements.
日本語の概要は準備中です。原文の説明を表示しています。
The investigation harness for "why is this slow?" over a Pulp Perfetto trace (.pftrace). Runs the hypothesis→query→drill-down chain-of-evidence loop autonomously and returns a plain-English root cause + evidence + a concrete fix. TRIGGER on "why is my plugin slow to open", "find the slowest frames", "why is the UI stuttering", "why is my plugin using so much CPU", "which DSP node is expensive", "the load meter looks calm but CPU is pinned", or a named `pulp trace gpu-startup|gpu-health|gpu-probe` analysis. Ships Pulp-specific hints for dsp, frame, js, gpu, and cross-platform symptoms.
日本語の概要は準備中です。原文の説明を表示しています。
Build or iterate on a Pulp WebView UI using the native WebView bridge, embedded assets, directory-backed dev resources, and focused WebView validation.
日本語の概要は準備中です。原文の説明を表示しています。
Search, inspect, plan, apply, remove, pack, and scaffold local Pulp package manifests. Use for Pulp-native source/UI/template kits and for untrusted or semi-trusted manifest-bearing artifacts that must be reviewed before project mutation.
日本語の概要は準備中です。原文の説明を表示しています。
Leveraged-prototype dev loop (`pulp loop`) — focus marker plus normal watch/rebuild loop, with AOT analyzer guidance and deferred ar-swap/PR-monitor playbook. Use when porting an existing UI/bundle to Pulp, doing visual/behavioral parity work, or batching upstream framework gap fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Capture faithful PNGs of Pulp view trees / imported UIs headlessly. Covers render_to_png backends (Skia vs CoreGraphics), the image-compositing gotcha, capture_png from a live GPU host, and the --screenshot-backend validate flag. Use whenever you render a UI to a PNG to eyeball or montage it.
日本語の概要は準備中です。原文の説明を表示しています。
Route repository-qualified changes across Pulp and Vellum using Pulp's exact ownership projection. Use when a change touches design import, Chromium authoring, DesignIR, visual harness, screenshot, Skia/Dawn, runtime assets, or another path represented by `.github/vellum-ownership.json`; when deciding whether work originates in Pulp or Vellum; or when validating the cross-repository routing contract.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and maintain browser demos of Pulp audio plugins (both web ABIs — WAM and WCLAP) from one declarative config, so every demo mounts the SAME shared player and the two ABIs stay in lockstep. Invoke it whenever you publish/update a browser demo of a Pulp plugin, add a plugin to a demo gallery, stand up a new gallery, or touch demo pages/hosting. It runs a deterministic generator (config → stamped WAM+WCLAP site + owned-files manifest) and a blocking validator (config schema, cross-origin-isolation coverage, OG metadata, regeneration ownership). Customization is declarative config in <repo>/.pulp-web-demo/config.json (schema bundled) plus at most two typed module seams; the shared player (pinned @danielraffel/web-player) holds all UX behavior and is never vendored. Works in Claude and Codex.
日本語の概要は準備中です。原文の説明を表示しています。
Create publication-quality, editable scientific and engineering schematics with explicit physical meaning, exact labels, visual hierarchy, and provenance. Use for experimental facilities, thermal-fluid mechanisms, workflows, graphical abstracts, system architectures, or research diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
Design clean, graphics-first technical presentations and posters with logical slide progression, visual hierarchy, purposeful motion, and complementary speaker notes. Use for research talks, conference slides, seminars, defenses, posters, or figure-focused presentations.
日本語の概要は準備中です。原文の説明を表示しています。
Step-by-step guide for building a JUCE audio plugin from scratch. Use when the user asks "how do I create a JUCE plugin", "set up a JUCE project", "add parameters to my JUCE plugin", "package my VST3", or "how do I wire up APVTS". Trigger on phrases like "create a JUCE plugin", "JUCE CMake setup", "AudioProcessor skeleton", "add APVTS parameters", or "codesign my plugin on macOS".
日本語の概要は準備中です。原文の説明を表示しています。
Skill体系产品经理角色。专聚焦「这个Skill应该是什么」的产品定义层——引导用户通过双视角设计，输出完整的 skill-product-definition-template 卡片，作为 skill-designer 工程实现的前置输入。不做实现，不跑关卡，纯产品思考。触发词：「我有个Skill想法但还没想清楚」「帮我做这个Skill的产品定义」「作为Skill PM帮我分析」「帮我把这个Skill想清楚」「填写Skill产品定义卡片」「分析这个Skill需求」。不应触发：关于团队组织角色的询问（「谁是我们的Skill PM」）。
日本語の概要は準備中です。原文の説明を表示しています。
Skill/Agent/Rule 开发全流程双视角导引者。新建或重构任何 Skill/Agent/Rule 时激活。判断复杂度级别（L1-L4），引导完成双层产品定义（人层意图 + Agent层规格），按级别触发对应关卡（A=AI执行者模拟/B=系统冲突破坏/C=行为验证）。触发词：「新建Skill」「设计一个Skill」「要写一个新的Skill」「新建Agent」「设计子智能体」「新建Rule」「设计规则」。
日本語の概要は準備中です。原文の説明を表示しています。
UI/UX设计师角色。关键词：设计/UI/UX/用户界面/交互设计/体验感/视觉/组件规范/原型。激活后先定义体验感，再设计交互和视觉，同时输出智能体层接口定义。
日本語の概要は準備中です。原文の説明を表示しています。
前端开发角色。关键词：前端/React/TypeScript/Vite/UI实现/组件/页面/接口联调。激活后读技术架构.md和设计师输出，还原设计意图，不自作主张改交互逻辑。
日本語の概要は準備中です。原文の説明を表示しています。
施测科研人员认知风格量表（RCSS），评估横向整合 vs 垂直深度的认知偏好。当用户选择填写量表、或画像中RCSS数据缺失时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".
日本語の概要は準備中です。原文の説明を表示しています。
Research-grounded workflow for designing, reviewing, and improving video game user interfaces, including HUDs, menus, navigation, focus states, onboarding/tutorials, objective tracking, input prompts, readability, accessibility, and destructive-action flows. Use when asked how to make good game UI, critique a game UI or HUD, propose UI/UX guidelines, design menu or gameplay interfaces, compare HUD vs diegetic/spatial presentation, create a UI design brief, or run a usability/accessibility review for PC, console, mobile, or VR games.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
UI/UX design agent for crafting user experiences, visual designs, and game interfaces. Auto-detects the designer role (UX Designer, UI Designer, Game UI Designer) and spawns a role-scoped sub-agent with only the relevant reference files. Triggers on phrases like "user flow", "wireframe", "design system", "design tokens", "accessibility", "WCAG", "UI pattern", "HUD", "game menu", "inventory UI", "minimap". Full per-role triggers in references/roles/.
日本語の概要は準備中です。原文の説明を表示しています。
Lanhu to Code workflow for Claude Code. Convert Lanhu design URLs into Vue/React frontend code with component reuse, design token mapping, TODO-safe business logic, and optional code review.
日本語の概要は準備中です。原文の説明を表示しています。
Scan frontend src directories and generate docs/components.md so Claude Code can reuse existing Vue/React components during design-to-code generation.
日本語の概要は準備中です。原文の説明を表示しています。