이메일, 캘린더, 할 일 관리, 자동화 (7.8천건)
Closed-loop compare-adjust-repeat workflow for fitting Blender models to supplied front/side/back/top templates and originals. Use when the user asks to compare the product to templates/originals and adjust until it fits across all dimensions, or when all views must pass measurable bbox/centroid/silhouette/edge validation before export.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Harmonize multiple Blender skills into a coherent pipeline with clear activation precedence, handoff artifacts, dependency gates, and conflict-resolution rules. Use when a Blender task spans several skills, when reference-locked work conflicts with generic production workflow, after adding/updating skills, or when repeated failures indicate skill interference or missing inter/intra-play.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for any request that spans multiple phases of 3D work, even if the user does not say "workflow" — also covers "make a final image of X", "produce a hero render", "professional-looking result".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task touches a Jupyter or marimo notebook, asks to productionise or schedule notebook logic, or when you are tempted to do the work in a notebook — extract logic into tested modules, keep the notebook thin and reproducible, and commit it the way the repo does
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you start an analiz task - explore every affected repository and resolve unknowns before writing the report
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an analiz task arrives in done (approved) - turn the approved split into implementation tasks with repository, AC, derived_from and ordering arguments
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task in code_review was sent back before (an earlier need_revision comment exists) - verify every prior point was fixed at its root
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an approved analiz spans more than one repository - split the work per repository and open one or more tasks per repository, each carrying its own plan slice
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when planning a delivery request as the only orchestration agent - one board-writing subtask, backlog first, one approval question, then move approved tasks to todo
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approved
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz task
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a stakeholder sends a request - route it to backlog tasks, an analiz task, or a focused question, decide ask-vs-assume with a Definition of Ready, and ask only what a wrong guess would actually cost
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task is in pm_uat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to human_uat or need_revision
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-first discipline and what makes a test worth keeping. Use when implementing any feature or bug fix, before writing production code, and whenever writing or changing a test.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to work a production incident remediation task. Use when the task title starts with "Incident:" or its description carries an incident id and a suggest/auto_fix policy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.