UI/UX、ロゴ、スライド、画像生成（7,281 件）
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for ANY visual / UI / design work on Commonly — picking colors, choosing fonts, styling new v2 components, building HTML mocks, designing marketing pages, or auditing whether a change matches the brand. Triggers on tasks involving v2.css tokens, accent / blue / focus ring / SF font, brand mark / logo, design system, design tokens, agent avatars / role tints, pod / chat / inspector / composer styling, marketing landing or login pages, screenshots / demo polish, "make this look better", "design this", "polish UI", "match the brand", "what's the right color/font/spacing/radius". Sources of truth live at `frontend/design-system/` (tokens.css, README.md, brand mark SVG, preview cards) and `frontend/src/v2/v2.css` (production tokens). Read both before recommending or shipping anything.
日本語の概要は準備中です。原文の説明を表示しています。
3D Morph PPT — extends morph-ppt with GLB model insertion, cinematographic camera, model-content layout, and enriched visual design system.
日本語の概要は準備中です。原文の説明を表示しています。
Context-aware translation that preserves tone, style, and natural word order. Use when translating UI strings, documentation, marketing copy, or any multilingual content. Infers register, domain, and style from the source text and surrounding codebase context.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.
日本語の概要は準備中です。原文の説明を表示しています。
Design schemas and migrations, tune queries, or plan vector retrieval and database operations. Application API implementation uses oma-backend.
日本語の概要は準備中です。原文の説明を表示しています。
Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation. Use for brainstorming, ideation, exploring concepts, and evaluating approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.
日本語の概要は準備中です。原文の説明を表示しています。
AI design specialist skill with DESIGN.md management, anti-pattern enforcement, optional Stitch MCP integration, and component library guidance. Covers typography, color systems, motion design (motion/react, GSAP, Three.js), responsive-first layouts, and accessibility (WCAG 2.2).
日本語の概要は準備中です。原文の説明を表示しています。
Translate or revise localized UI strings and prose while preserving meaning, terminology, placeholders, and structure.
日本語の概要は準備中です。原文の説明を表示しています。
Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Explore goals, constraints, and alternative approaches before choosing a design. Use when the user requests ideation or design exploration.
日本語の概要は準備中です。原文の説明を表示しています。
Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.
日本語の概要は準備中です。原文の説明を表示しています。
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop skill for PRODUCT UI - dashboards, data tables, forms, multi-step flows, settings, list/detail, app shells. The agent reads the surface, budgets the frame first, and ships dense interfaces that are correct at every edge case (overflow, long labels, empty/error/loading states, i18n expansion, keyboard/a11y). House-system-first; maps to Carbon/Polaris/Atlaskit/Fluent/Primer/Material3/Radix-shadcn/Ant. The counterpart to taste-skill, which owns landing/portfolio/marketing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defending the research design of an American Educational Research Journal (AERJ) manuscript — quantitative (multilevel, IRT, quasi-experimental, RCT), qualitative (case study, ethnography, interview), or mixed methods. AERJ judges each tradition on its own terms against the AERA reporting standards. Strengthens the design; it does not write code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building exhibits for an American Anthropologist (AA) manuscript — photographs, maps, site plans, artifact images, kinship diagrams, transcripts, evidence tables, and multimodal media — so they are self-contained, accessible (alt text), ethically cleared (consent, permissions), and count toward the word budget. Designs exhibits; it does not run analysis or clear permissions for you.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defending the research design of an American Anthropologist (AA) manuscript — fieldwork and participant observation, interview and archival design for ethnographic/qualitative work, material/contextual analysis for archaeology, and appropriate lab/quantitative design for biological anthropology. AA judges each mode on its own terms with reflexivity. Strengthens the design; it does not write code or run fieldwork.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or trimming the exhibits of an American Economic Review: Insights (AER: Insights) short-format manuscript to the hard five-exhibit budget, one page each, no significance asterisks. Designs the minimum exhibit set; it does not run the analysis behind them.
日本語の概要は準備中です。原文の説明を表示しています。
Use when articulating why an Agricultural Systems (AgSy) result matters — its relevance for farm design, management, decision support, or policy. AgSy values systems analysis that informs a decision, so this is what separates an AgSy paper from a methods demo. It frames implications honestly within the model's scope; it does not over-claim or invent impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building figures and tables for an Agricultural Systems (AgSy) manuscript so exhibits communicate interactions, dynamics, trade-offs, and model performance clearly. AgSy is a systems journal, so the best exhibits show trade-off frontiers, observed-vs-simulated fit, resource flows, and conceptual system diagrams — not just a bar chart of one treatment. Designs exhibits; it does not run the analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding which robustness checks belong in the few in-text words of an American Economic Review: Insights (AER: Insights) short-format manuscript versus the online Supplemental Appendix. Triages checks against the length cap; it does not design the identification (see aeri-identification).
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding whether a project fits AEJ: Economic Policy rather than J. Public Economics, AEJ: Applied, or AER, and when sharpening the policy question and its welfare stake for an AEJ: Economic Policy manuscript. Frames fit and the policy-question-first contribution; it does not design the identification or run estimation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting or revising the prose of an AEJ: Economic Policy manuscript — especially the abstract and introduction — to translate causal estimates into a clear policy takeaway without overclaiming. Shapes the policy-first narrative and house style; it does not design identification or build the welfare model.
日本語の概要は準備中です。原文の説明を表示しています。