「design」の検索結果

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

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

Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.

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

Use when a user asks for or clearly wants to be grilled, interviewed, or to stress-test a plan or design, including when they mention "grill me". Resolve material decisions one at a time until scope, success criteria, and resources are explicit.

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

Use when designing, redrawing, or validating research-paper figures and tables, including Matplotlib plots, LaTeX tables, benchmarks, captions, legends, annotations, color, and typography. Preserves exact evidence and checks rendered PDFs for clipping, overlap, and readability.

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

Frappe Insights and analytics guidance for dashboards, query design, charts, permissions, metrics, ERPNext reporting, and operational analytics. Use when work touches Frappe Insights or analytics in the Frappe ecosystem.

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

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

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

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

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

Convert scattered progress notes, RAID changes, and milestone movement into a clean weekly or biweekly status update. Use when the work is routine status packaging or steering prep. Do not use for project governance design, root cause analysis, or deep portfolio risk assessment.

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

Assess organizational training needs using ADDIE methodology and Kirkpatrick's 4-Level evaluation framework. Maps performance gaps to learning objectives using Bloom's taxonomy. Use when planning L&D budgets, designing training programs, or evaluating training effectiveness.

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

Structure presentations, pitch decks, and internal slide decks from rough ideas into clear outlines with slide-by-slide content guidance, key messages, and data callouts. Use when the work is organizing thoughts into a presentation structure. Do not use for visual design, slide layout, or graphic creation.

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

Format recurring KPI snapshots, exception flags, and owner follow-ups for weekly operations reviews. Use when the work is routine packaging of operational metrics and exceptions. Do not use for root cause analysis, process redesign, or full performance diagnosis.

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

Turn launch dates, campaign inputs, and asset requests into a structured content calendar and workback plan. Use when the work is recurring marketing coordination and schedule packaging. Do not use for brand strategy, positioning design, or deep performance interpretation.

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

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

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

Map the end-to-end customer journey across awareness, consideration, purchase, onboarding, adoption, retention, and advocacy stages. Identify touchpoints, pain points, emotions, and Moments of Truth per stage. Use when designing or improving customer experience. Do not use for internal employee process mapping — use process-mapper instead.

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

Write one-page executive briefs and decision memos that turn messy inputs into a concise recommendation, options, risks, decision ask, and next steps. Use when leaders need a fast read before approving budget, policy, vendor, headcount, or strategy changes. Do not use for long-form reports, slide design, or generic summarization without a decision.

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

Define a Lean Six Sigma improvement project using DMAIC, problem framing, baseline measures, root-cause hypotheses, CTQs, and control planning. Use when an existing process is underperforming and the team needs a charter, SIPOC, baseline, and improvement path. Do not use for brand-new process design or vague complaints with no process boundary.

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

End-to-end pipeline that builds a new, playable Phaser 4 browser game from a natural-language idea (design, build, verify, iterate; Startup derives routing metadata). Trigger when the user asks to make, create, build, or generate a game, describes a game concept, or describes interactive mechanics, levels, or player actions, even without the word 'game'. Do NOT trigger for editing, debugging, or adding features to an existing game codebase, or for general questions about games.

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

Technical Specification Command. Translates a PRD into an implementation-ready technical spec through deep project analysis and clarification. Use when the user says "create a tech spec", "write the technical design", "spec this out", or after a PRD is complete and the user wants to move to technical planning.

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

Use when writing, reviewing, or refactoring Rust code. Covers ownership, borrowing, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Targets Rust 1.80+ and Edition 2024. Invoke with /rust-core.

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

Extract real brands (Wayback for rebuilds). Copy system, headline/CTA rules, trust surfaces, legal pages, SEO+structured data, anti-AI-slop, microcopy, DESIGN.md, W3C DTCG tokens, pSEO 5 types, GEO/AI search.

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

Use when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test helpers/mocks/fixtures

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

Material Design component library for Vue 3

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

CLI specification planning frameworks. Use when a spec touches a command surface, an interactive flow, config precedence, exit codes, or output modes. Covers flag contracts, prompt flow design, precedence tables, exit-code taxonomy, TTY/piped/JSON output, error text, signals, and cross-platform concerns.

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

Readable functional patterns — orchestrators, pure functions, named abstractions

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