「design」の検索結果

Design APIs for AI services. TRIGGERS - Use when user needs help with ai-api-design related tasks.

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

Design multi-step AI agent architectures with tools, memory, and orchestration. TRIGGERS - Use when user wants to design AI agents, multi-agent systems, or autonomous AI workflows.

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

Design after-school programs. TRIGGERS - Use when user needs help with after-school-program-design related tasks.

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

Design advisory boards. TRIGGERS - Use when user needs help with advisory-board-design related tasks.

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

Design learning for adults using andragogy principles. TRIGGERS - Use when user needs help with adult-learning-design related tasks.

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

Design activation metrics. TRIGGERS - Use when user needs help with activation-metric-design related tasks.

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

Design adaptive learning systems. TRIGGERS - Use when user needs help with adaptive-learning-design related tasks.

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

Design accessible documents. TRIGGERS - Use when user needs help with accessible-document-design related tasks.

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

Design for accessibility compliance. TRIGGERS - Use when user needs help with accessibility-design-architecture related tasks.

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

Design 360-degree review processes. TRIGGERS - Use when user needs help with 360-review-designer related tasks.

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

Design accessible apps. TRIGGERS - Use when user needs help with accessible-app-design related tasks.

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

Design accessible websites. TRIGGERS - Use when user needs help with accessible-website-design related tasks.

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

Guide accessible design compliance. TRIGGERS - Use when user needs help with accessibility-design related tasks.

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

You MUST use this before any creative work — creating features, building components, drafting documents, designing workflows, or modifying behavior. Explores your human partner's intent, requirements, and design before any implementation begins.

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

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.

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

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

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

Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.

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

REQUIRED before writing code for any feature touching auth, payments, credentials, tokens, sessions, file upload, user data, untrusted input, deserialization, network endpoints, or data deletion. Scope by that surface, not the task label — a research/experimental/local-only feature with none of it doesn't need this. Invoke it, record answers inline in the design doc or PR description, then write the code. Skipping this is how auth bypass, token leakage, and delete-the-wrong-record bugs ship. If the feature touches any of those surfaces and this hasn't run, the design is incomplete — do not proceed to implementation.

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

Review the UI and style files changed in the working tree against this repo's own design system, before they are saved or committed. Runs the same deterministic check as the CLI's --check flag (no tokens, about a second): hardcoded colours where a token exists, near-identical colour twins, off-scale spacing, radii, font sizes and shadows, typefaces outside the system, arbitrary Tailwind values, static inline styles, !important, duplicate component definitions and imports of the copy to avoid, new tokens that copy an existing one, chart colours written by hand where the repo keeps a chart palette (and one calm warning asking for a palette where it keeps none), on a repo built on MUI, Mantine, Chakra or Ant Design, colours or pixel sizes written onto kit components where the theme has a value, and on a Tailwind theme or a shadcn repo, palette classes such as text-gray-500 where the theme names a colour of that kind. Findings name the file, the line and the fix. This is the small, fast check for what just changed; the roast skill is the full scan of the whole repo with a report.

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

Best practices for designing Claude Code agent files (.claude/agents/*.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official guidance with battle-tested patterns from agent team usage.

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

Design and build custom Claude Code agents with effective descriptions, tool access patterns, and self-documenting prompts. Covers Task tool delegation, model selection, memory limits, and declarative instruction design. Use when: creating custom agents, designing agent descriptions for auto-delegation, troubleshooting agent memory issues, or building agent pipelines.

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

Agent skill for arch-system-design - invoke with $agent-arch-system-design

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

"Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.".

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