1,206 件 ・ 関連度順
概要と使いどころ
Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.
日本語の概要は準備中です。原文の説明を表示しています。
Apply product-grounded visual quality constraints during user-visible UI changes. Use for layout, styling, content hierarchy, theming, responsive behavior, or interaction affordances. Stay inactive for logic-only changes that preserve the rendered interface.
日本語の概要は準備中です。原文の説明を表示しています。
Use only for user-provided academic text, explicit scholarly claims, existing citations, or known bibliographies needing citations added, verified, replaced, extracted, or formatted. Supports claim-to-source matching, citation-support checks, replacements, and common academic citation formats. Do not use for general fact-checking, legal/journalistic citation work, open-ended 'find literature about X', topic-level exhaustive discovery, systematic-review corpus construction, PRISMA searches, or creating new research claims. Chinese: 为已有段落补参考文献、核验已有引用、替换错误引用、提取需引文论断、GB/T 7714 格式化.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and reorganize the skill inventory into hierarchical sub-skill bundles. Use when the user asks to review, group, or consolidate skills into a parent bundle.
日本語の概要は準備中です。原文の説明を表示しています。
Prismatic API access patterns and GraphQL reference. Covers the two-tier access hierarchy (MCP tools → Prism CLI), CLI usage rules, GraphQL query patterns, pagination, authentication, and managing platform resources programmatically.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
深度研究团队主理人（顾全之 · 研究主编）。带领 6 位专业成员按 5 阶段工作流（初调→规划→逐章深研→报告组装→发布输出）完成系统性深度研究，输出带多源引用的专业研究报告。 触发词：深度研究、行业研究、竞品分析、市场调研、学术综述、出一份研究报告、专题研究、趋势分析、技术综述。
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing or managing persistent, hierarchical memory systems for AI agents. Covers cross-session state, fact supersession, and self-managed memory tools to enable long-term recall and adaptive agent behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in designing, orchestrating, and managing multi-agent systems (MAS). Specializes in agent collaboration patterns, hierarchical structures, and swarm intelligence. Use when building agent teams, designing agent communication, or orchestrating autonomous workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
日本語の概要は準備中です。原文の説明を表示しています。
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Assume the role of Galyarder CMO (Chief Marketing Officer). Growth champion. Lead conversion rate optimization (CRO), analytics architecture, growth engineering, and data-driven market positioning.
日本語の概要は準備中です。原文の説明を表示しています。
Master coordinator for the founder. Filters noise, owns cross-functional processes, enforces consistency, routes decisions, and positions outputs for impact so the founder can think clearly. Doesn't own any function owns the space between all of them.
日本語の概要は準備中です。原文の説明を表示しています。
Assume the role of Galyarder CTO (Chief Technology Officer). Technical guardian. Enforce technical integrity, architectural determinism, self-healing formal verification, and planetary computational leverage.
日本語の概要は準備中です。原文の説明を表示しています。
Assume the role of Galyarder CEO (Chief Executive Officer). Apex Instance of the Intelligence Layer protocol. Deconstruct intent into departmental mandates, optimize strategic direction, and audit operational bandwidth.
日本語の概要は準備中です。原文の説明を表示しています。
Assume the role of Galyarder CFO-COO (Chief Financial and Operating Officer). Stability guardian. Enforce FinOps optimization, legal compliance, GDPR/privacy auditing, and risk parity.
日本語の概要は準備中です。原文の説明を表示しています。
Use when website or web app UI work needs practical design guidance for hierarchy, layout, readability, responsiveness, and interaction quality.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a website needs a broad audit covering UX, conversion, content, SEO, technical correctness, and information hierarchy before changes are planned.
日本語の概要は準備中です。原文の説明を表示しています。
Chief Security Officer mode. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Transaction Cost Economics (Williamson, 1975, 1985) to analyze governance structure choices — market, hybrid, or hierarchy — based on transaction characteristics. Use this skill when the user needs to decide make-or-buy, evaluate outsourcing vs vertical integration, design governance mechanisms for inter-firm relationships, or when they ask 'should we build this in-house or outsource', 'why do firms vertically integrate', or 'how should we structure this partnership'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Hierarchical Linear Modeling (HLM) to analyze nested data structures with random intercepts and slopes, accounting for intra-class correlation and cross-level interactions. Use this skill when the user has students nested in schools, employees in firms, or repeated measures in individuals, needs to partition variance across levels, or when they ask 'how do I handle nested data', 'what is ICC', or 'do group-level factors moderate individual-level relationships'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply pecking order theory (Myers and Majluf, 1984) to analyze how information asymmetry drives financing hierarchy decisions. Use this skill when the user needs to explain why firms prefer internal over external financing, interpret equity issuance as a negative signal, evaluate capital raising decisions, or when they ask 'why did the stock drop on the equity offering', 'should we use debt or equity', or 'why do firms hoard cash'.".
日本語の概要は準備中です。原文の説明を表示しています。