2,518 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify existing code for clarity and maintainability without changing behavior. Use when asked to clean up or simplify code, especially recent changes.
日本語の概要は準備中です。原文の説明を表示しています。
Find documentation and repository evidence for library behavior, API contracts, error messages, and known bugs. Use when a programming question needs current public documentation, issues, pull requests, or implementation examples.
日本語の概要は準備中です。原文の説明を表示しています。
Verify app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.
日本語の概要は準備中です。原文の説明を表示しています。
New App Intents APIs and behaviors for iOS 27 and macOS 27: SnippetIntent, LongRunningIntent, execution modes, and interactive snippets.
日本語の概要は準備中です。原文の説明を表示しています。
UE (user experience engineering) skill for defining end-to-end user experience behavior and interaction logic. Use for tasks like flow design, interaction models, state machines, error recovery, input validation, usability heuristics, accessibility, and turning UX intent into testable acceptance criteria for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture-first UI/UX design skill for Codex that helps agents reason from product truth, user journeys, causal design decisions, art direction, interaction, responsive behavior, imagery, iconography, and motion before implementation, then validate the result through rendered browser critique.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim Design System Intelligence — token architecture (primitive→semantic→component), component library governance, CSS variable systems, Tailwind integration, design-to-code handoff, Storybook, Figma token export. Activate for design system creation, token audits, component specs, dark mode systems, brand-to-token sync. Powered by Maxim behavioral science + Atomic Design + TOGAF governance.
日本語の概要は準備中です。原文の説明を表示しています。
Security audit of a codebase — web apps, APIs, services, CLI tools, libraries, daemons, and more. Use when asked to find security bugs, do a security review, audit for vulnerabilities, or pen-test the code. Focuses on exploitable issues with real impact, not theoretical concerns or industry-standard behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim Brand Intelligence — brand identity, voice architecture, visual identity systems, messaging frameworks, brand consistency enforcement. Activate for brand strategy, brand audits, brand guidelines, tone of voice, asset compliance, color palette, typography specs. Powered by Maxim behavioral science layer.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an ambiguous factory issue into human-approved product, behavior, design, and implementation slices. Use interactively before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Write, edit, or review UI copy, CLI messages, help text, code comments, and technical documentation covering product behavior, errors, status, setup, compatibility, or technical results.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether a task deserves its own git worktree and, if chosen, run it end to end: branch from the integration branch rather than the current tree, keep the main working copy untouched while the task runs, compare the result against the untouched baseline before declaring it done, and prepare it for a pull request instead of merging. Use when a request says to do the work in a new worktree or branch, when a change is large or risky enough that the main tree should stay usable, when several tasks need to run in parallel on one repository, when a result has to be diffed against current behavior, and when deciding where screenshots, builds, and other artifacts produced in a worktree should end up.
日本語の概要は準備中です。原文の説明を表示しています。
Judgment rules for user-facing text and docs: CLI and diagnostic output, error and help text, README and docs structure, code comments, titles, and generated reports, decks, or exports. Use when writing or changing any user-visible string, when adding or restructuring docs or deciding which page owns a fact, when a page is about to record a version, a deployment state, or a value the code already owns, when a comment, title, or artifact could carry the reasoning or an abandoned option behind the change, when a behavior change needs its copy sites swept, or when reviewing a diff that touches copy or docs.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.
日本語の概要は準備中です。原文の説明を表示しています。
tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex. Use for configuring or diagnosing tlive, connecting IM platforms, printing session links, or explaining approval behavior. Triggers "tlive", "IM bridge", "phone approvals", "remote terminal", "Telegram/Feishu notifications".
日本語の概要は準備中です。原文の説明を表示しています。
Score and prioritize leads based on firmographic fit and behavioral engagement signals, producing ranked tiers for sales team focus. Use when the user requests lead scoring or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk. Use when evaluating a third-party skill before installing, enabling, updating, publishing, or distributing it; reviewing an untrusted SKILL.md, agent configuration, MCP integration, archive, or repository; comparing a package with a known-good version; or investigating unexpected tool, network, credential, or filesystem behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Membrane Biophysicist. Use when a task calls for Membrane Biophysicist judgment. Reasons from Helfrich elasticity, Lo/Ld phase behavior, and intrinsic curvature; builds GUVs, SLBs, nanodiscs, and BLMs; reads Laurdan GP, FRAP/FCS, aspiration, and electrophysiology while treating multilamellarity, detergent carryover, and probe misinterpretation as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Foundation Engineer. Use when a task calls for Foundation Engineer judgment. Reasons from effective stress, ULS versus SLS limit states, and construction-altered soil behavior through CPT/SPT logging, triaxial and oedometer testing, LRFD φ-factor checks, and LPILE/PLAXIS analysis while treating liquefaction-driven lateral spread, negative skin friction downdrag, differential settlement, and scour as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。