「design」の検索結果

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

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

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

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

SQL query optimization, schema design, indexing strategies, and relational database mastery for production data systems

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

Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features

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

Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.

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

Data pipeline architecture, ETL/ELT patterns, data modeling, and production data platform design

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

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

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

Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.

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

Visual weight, attention order, and the decisions that guide the eye. Use when building layouts, evaluating information architecture, or diagnosing why a design feels confusing.

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

Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.

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

Navigate the gap between what you can see and what you can make. The Ira Glass gap. Use when a designer is frustrated by the distance between their taste and their output, when mentoring someone through a creative plateau, or when someone is considering quitting because their work doesn't match their vision.

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

Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.

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

Micro-decision analysis. Catalog the border radii, spacing scales, type sizes, and state coverage that most people miss. Use when auditing design systems, evaluating craft quality, or training granular perception.

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

Response timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.

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

Density, whitespace, rhythm, and how space communicates relationships between elements. Use when building layouts, evaluating spacing consistency, or diagnosing why a design feels cramped or empty.

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

Build a reference system that returns the right reference in under 60 seconds. Use when setting up a design reference library, reorganizing existing collections, or helping teams build shared reference systems.

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

Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.

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

15-minute daily taste exercises. Monday through Friday. Compound effect over time. Use when building personal practice habits, training a team's design eye, or adding structure to professional development.

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

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

Design and run reproducible benchmarks. Use when measuring performance scaling, comparing branches, or analyzing speedup metrics.

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

Guides the discovery, design, validation, and delivery of Agent Skills. Use when identifying skill gaps, creating or revising a SKILL.md, improving skill descriptions, or checking a skill against the Agent Skills specification.

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

Survey one surface of tdmcp (artist controls, library/packaging, CLI/DX, AI/LLM, or TouchDesigner depth) for candidate NEW features — inventory what exists, cross-check the roadmap, apply the gap-finding lenses, vet each idea, and emit a structured, novelty- and confidence-labelled candidate list to _workspace/discovery/. Use when a td-surveyor agent is scouting a surface during the feature-discovery harness.

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

How to use windows-computer-use-mcp effectively — tool selection, focus rules, safety, and mission design.

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

Survey the whole tdmcp project and produce a prioritized list of NEW features it could implement — across artist controls, CLI/DX, AI/LLM integration, and TouchDesigner depth. Use whenever the user wants to brainstorm, discover, survey, list, or audit what features/tools/effects/controls/commands/prompts/capabilities tdmcp *could* add, asks 'what could we build / what's missing / what are the opportunities / ideas for the project', or wants a feature backlog or gap analysis. Also for follow-ups: re-run, refresh, update, re-survey, deepen, or re-prioritize the backlog, or survey just one surface (e.g. 'CLI ideas only'). This is the IDEATION harness — it produces a list to decide from; it does NOT build. When the user has already chosen a feature and wants it implemented/shipped/added, use tdmcp-pipeline instead.

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