three.js model, downloadable as OBJ or GLB
日本語の概要は準備中です。原文の説明を表示しています。
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable. It keeps the smallest focused test with the delivered project and updates coverage when behavior changes. Do not load for greenfield work unless reusable tests are explicitly required, behavior-preserving refactors, verification-only work, plan/review/explanation/documentation/formatting/generated-output-only work, explicit no-change or no-tool work, or when the user declines tests.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Verification is part of the delivered project when it can prevent the same behavior from breaking again. Use the project's existing framework and conventions.
For a bug fix or behavior change, add or update the smallest maintained test in the repository's normal test layout that exercises the changed behavior. If a specification makes a reusable suite or test category a deliverable, implement that suite instead of treating it as private verification.
An inline interpreter command, heredoc, scratch script, temporary-directory test, demo, or manual probe may help diagnose the problem, but it does not replace the maintained test. Keep a useful self-authored test unless the user explicitly asks for a disposable probe.
Do not add a new test framework solely to satisfy this skill. If the repository has no maintained harness and the request does not require one, disclose when durable coverage would be disproportionate or infeasible and use the narrowest honest verification instead.
On a later turn, update the maintained test even when the old suite remains green and the user does not repeat the test request. Cover the new behavior, not merely an unrelated cleanup in the test file.
Observe the authentic failure before the implementation change when it is safe and runnable. Then make the smallest implementation change and run the focused maintained test after the final relevant source or test edit.
Do not weaken or delete a real failing test to obtain green. Fix the product, or explain why the test's expectation is wrong before changing that expectation. Do not repeat an unchanged check solely to collect evidence.
Run a broad or full suite only when the user, a repository gate, or proportionate risk requires it. A focused regression test comes first; broad proof does not substitute for missing focused coverage.
If the real runner is unavailable but the focused test can still be authored honestly, leave the focused test in the repository and say it was not run. Do not fabricate a passing result.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
three.js model, downloadable as OBJ or GLB
日本語の概要は準備中です。原文の説明を表示しています。
Manage your private to-do list for the user. Use to add or update tasks, record what they are waiting on, track blockers, mark tasks complete or canceled, and clean up the list. Not for Dreamers or external task trackers.
日本語の概要は準備中です。原文の説明を表示しています。
Run a goal as a project: you coordinate. Use for "agents <task>", "take this to done", "work on this in parallel", "what are my threads doing", "pick up <slug>", "resume <slug>", "keep going until it is merged". Under `/agents` you do the work yourself unless it needs several lanes or a long wait — you judge; the plan line says why. No target you could verify (a file, API, number or measure) → the grill interview first, not threads. Read this skill before proposing anything for `/agents`: without it a proposal is in-session subagents.
日本語の概要は準備中です。原文の説明を表示しています。
Timeline-based motion design
日本語の概要は準備中です。原文の説明を表示しています。
The user's synced Apple Health (HealthKit) data: daily metrics (steps, distance, calories, heart rate, HRV, VO2max), sleep sessions (stages, quality, efficiency), and workouts.
日本語の概要は準備中です。原文の説明を表示しています。
Create, read, edit, or manipulate Word documents (.docx) and Word templates (.dotx). Use whenever a build task's artifact kind is document with the default docx output, or the task mentions a Word doc, .docx, or .dotx, extracts or reorganizes content from one, inserts or replaces images, does find-and-replace in one, or works with tracked changes (redlines) or comments. Covers python-docx generation, raw OOXML editing of existing files, document structure and formatting, and render verification. Not for PDFs, spreadsheets, or Google Docs.
日本語の概要は準備中です。原文の説明を表示しています。