3.4천건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run taste-informed design reviews using Observation > Principle > Question. Use when facilitating design critiques, improving feedback quality on a team, or building a shared vocabulary for quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds multi-touch pipeline attribution models and generates stakeholder-ready narratives from campaign performance data. Use when analyzing channel contribution to pipeline, preparing monthly/quarterly revenue reports for leadership, diagnosing pipeline misses, modeling budget reallocation scenarios, or translating raw attribution data into board-deck language. Designed for B2B SaaS demand gen teams that report on pipeline and revenue, not leads or MQLs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates the monthly revenue-accountable marketing report that B2B SaaS marketing leaders deliver to CEOs, CFOs, executive teams, and boards. Use when preparing the monthly CEO report, drafting the marketing section of a board deck, defending budget decisions, diagnosing pipeline gaps, or transitioning marketing from MQL/SQO reporting to revenue, CAC payback, and forward pipeline coverage. Designed for B2B SaaS demand generation leaders who own pipeline targets across segments, geos, and motions, and need to explain marketing's revenue contribution in executive language.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates sourced, BDR-ready account research briefs for named target accounts in B2B SaaS ABM and outbound motions. Use after a target account list is built and before outreach sequences are written. Best for Tier 1, Tier 2, and intent-qualified accounts where BDRs need a clear "why this account, why now, why this persona" hypothesis. Designed for B2B SaaS teams selling compliance, security, GRC, risk, or other technical platforms into mid-market and enterprise buyers. Not intended for broad list building or mass enrichment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM program review. Also use when asked to "build an ABM program," "set up account-based marketing," "design a target account strategy," "plan ABM campaigns," or "measure ABM results." Designed for demand gen teams selling to Mid-Market companies with $10K-$50K+ ACV, multi-persona buying committees, and 3-6 month sales cycles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire, standardizing campaign tracking, fixing broken lead routing, cleaning up HubSpot or CRM data, building QA checklists for campaign launches, or creating incident response procedures for marketing system failures. Also use when asked to "fix our UTM mess," "standardize campaign naming," "build a QA checklist," "audit our marketing ops," or "create an ops runbook." Designed for B2B SaaS marketing teams running HubSpot with multi-geo, multi-segment operations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates and maintains competitive battlecards from win/loss data, competitor intel, G2 reviews, and sales feedback. Use when building battlecards for a specific competitor, updating existing battlecards with new intel, preparing BDRs or AEs for competitive deals, analyzing win/loss patterns against a competitor, or responding to a competitor's product launch or pricing change. Also use when asked to "build a battlecard," "update competitive intel," "how do we beat [competitor]," "what do we say when a prospect mentions [competitor]," or "analyze our win/loss against [competitor]." Designed for B2B SaaS teams selling against known competitors in deals with multi-persona buying committees.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates the dedicated Kinect wall harp implementation team. Use whenever the user asks to build, implement, continue, fix, QA, document, or ship the Kinect wall harp, Kinect v2 wall-depth harp, FreenectTD depth-blob hand tracking, projected wall strings, pluck synth harp, or this feature's Layer 1 tool/recipe/docs. Use this before the generic tdmcp-pipeline for this feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates the tdmcp feature team end-to-end: design/wireframe → build → integrate → QA → release. Use whenever the user wants to build, implement, develop, ship, or add one or more tdmcp features/tools/effects/controls/AI-prompts for TouchDesigner, or to run them through a coordinated design→develop→QA→deploy pipeline. Also use for follow-ups: re-run, continue, update, fix, or improve a feature/batch, ship the next version, or rebuild just one part of a previous run. Single feature or a whole batch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run or maintain the full tdmcp repo quality-audit team: command sweeps, all package/Makefile/CI gates, security review, usability/flow review, refactor/test-gap analysis, coverage hardening, QA, and follow-up fix waves. Use whenever the user asks for a complete audit, improve repo/code quality, test all commands, find security/usability failures, refactor debt, add missing tests, re-run the audit, continue a previous quality wave, or verify the repo is ready.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Linear issues, projects, and teams
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs a small, throwaway multi-agent fan-out (a couple of parallel workers plus a review pass) in ANY project — trigger phrases "spawn a few parallel agents", "fan out", "quick worker team" — without the full /startcycle-graph contract, no .agents/graph.md bootstrap, no state.json schema, no persistent files. Roles run on the session model unless `.aos/pipeline.json` overrides one (an external CLI can take the worker step) and portable across machines that may not have Antigravity/OpenCode/Codex installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When asynchronously reviewing peer code before merging into the main branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with the asc cli. Use when onboarding a new app, rotating signing assets, or sharing them across a team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage Linear issues and claim work with the Linear MCP tools - find the triage queue or your assigned work, check for duplicates and existing owners, set team/priority/labels, and claim an issue (assign to me, move to In Progress) only after confirming nobody else owns it. Use for "triage the queue", "what should I work on", "claim LIN-123".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: Good night Team, EOD, Wrapping up, or end-of-day consolidation. Archives session context, promotes durable patterns, and compacts live agent memory files for the next session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: the agent captures a correction from the team lead, hits an unexpected error, discovers a capability gap, or finds a better practice. Logs to .learnings/ and promotes durable patterns to permanent project memory.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: 'do work', 'dispatch builder', or team lead triggers automated task implementation. Governs end-to-end flow from dispatch through verification, fail handling, batch mode, and escalation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: Good morning Team, start-of-day briefing, or morning status request. Architect orchestrates; Builder, Tester, and Router return their sections as subagents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.