「te-te」の検索結果

Write failing tests from requirements. Invoke for each todo before /implement.

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

Add missing test coverage for your local code changes by generating new test files (covers uncommitted and untracked changes, or the latest commit if everything is committed). Use when you want write tests for new logic or increase test coverage.

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

Create reusable black-background white-text opening animations for new videos. Use when the user asks for "黑底白字开场", "纯黑加白字", "白色文字逐渐出来", "一个个字出来", "打字效果", "打字音效", "字体变化开头", "opening title animation", "kinetic text opener", or a short black-and-white intro before a HyperFrames, Remotion, ffmpeg, SaaS/product, tutorial, commentary, or course video. This is for original opener creation, not pixel-level reference matching.

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

Generate and structure MATLAB unit tests using matlab.unittest and matlab.uitest features, including class-based tests, parameterized testing, fixtures, mocking, and app testing with gestures. Use when writing, generating, or adding tests, creating test classes, adding test methods, parameterizing tests, setting up fixtures, mocking dependencies, or testing App Designer apps. Do NOT use for running tests, collecting coverage, or CI/CD configuration.

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

Write tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.

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

Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the value of proposed coverage, or auditing an entire subsystem. Use write-tests to implement the resulting test changes.

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

Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".

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

Controls authorized cybersecurity exercises through inject scheduling, safety gates, stop and restart decisions, communications, and synthetic-data boundaries. Use when serving as exercise control or white-team coordinator, not as compliance assessor or whitehat operator.

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

Use when asked to generate tests for a file, module or component, to raise coverage, or to bootstrap a suite for untested code. Detects the project's test framework and conventions first, then writes unit, integration and edge-case tests.

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

ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, `.cs`, or `.csproj`; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for hard-to-test framework dependencies; or verifying those C# calls are already abstracted. DO NOT USE FOR: any target lacking the activation prerequisite; generating wrappers (use generate-testability-wrappers); migrating code (use migrate-static-to-wrapper); or general code review.

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

ALWAYS USE when asked to migrate, replace, or make testable existing C# static calls with a named wrapper or built-in abstraction: DateTime.UtcNow/Now or DateTimeOffset.UtcNow to TimeProvider/IClock, File.* to IFileSystem or an existing store such as ITextFileStore, and Environment.* to an existing reader such as IEnvironmentReader. Covers scoped files/projects, constructor injection, replacing temp-file or process-environment tests with fakes, "already registered" abstractions, and static classes whose callers/signatures must stay unchanged. Preserves DateTimeKind and call count. DO NOT USE for finding statics (detect-static-dependencies), choosing/designing a new wrapper (generate-testability-wrappers), behavior tests with no chosen seam (testability-obstacle), or test-framework migration.

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

DO NOT USE when the target already consumes an injected interface or built-in abstraction such as IFileSystem or TimeProvider, even if the request says "generate a wrapper"; no new wrapper is needed. Use only when C# source calls an ambient/static dependency and no injectable seam exists: first-time TimeProvider, IHttpClientFactory, or System.IO.Abstractions adoption; minimal Environment/Console/Process wrappers; IProcessRunner; DI registration; or an ambient seam that preserves a static API. Exclude static detection (detect-static-dependencies), migration to an existing/registered abstraction (migrate-static-to-wrapper), one blocked behavior plus deterministic tests (testability-obstacle), and general interface design.

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

Analyze what changed and generate a structured test plan at .turbo/test-plans/<slug>.md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios", "test plan for this PR", or "what are the test cases".

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

Guides privacy audit sampling methodology including statistical and non-statistical sampling, sample size determination, stratification techniques, attribute sampling for compliance testing, confidence level selection, tolerable deviation rates, and extrapolation of results to the population. Keywords: audit sampling, statistical sampling, attribute testing, sample size, confidence level, stratified sampling, privacy audit.

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

Пишет unit-тесты для указанного файла или функции в стиле существующих тестов проекта. Используй, когда просят добавить тесты, покрыть код тестами или проверить граничные случаи.

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

Fill a raw PowerPoint (.pptx) template with new content by cloning and patching native slides — no SVG conversion, original design preserved, verified through a mandatory OfficeCLI overflow/render loop. Use whenever the user supplies an existing .pptx template or deck plus new material or a topic and wants a generated PPTX, even if they don't say "template" — "use this PPT template to generate a PPTX", "fill this deck with the new content", "replace the copy in this PowerPoint", "keep the original design and swap in this material", "이 템플릿에 내용 채워줘", "이 PPT 양식으로 만들어줘", "기존 PPT 디자인 그대로 내용만 교체해줘". Do NOT use for reusable template package creation (ppt-master create-template), 1:1 beautify, SVG-pipeline deck generation, or finished-PPTX enhancement (native-enhance-pptx).

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

Analyze new commits and generate related test cases.

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

Use when writing Go tests that need test doubles or cover multiple cases - detect the repo's mocking approach (Mockery v3, gomock, hand-written testify mocks, fakes), table-driven cases, testify suites when the repo uses them, and real-Postgres tests for repository adapters

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

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

Klare, überprüfbare Website-Texte für eine definierte Zielgruppe entwerfen und überarbeiten. Nutze diesen Skill für Landingpages, Startseiten, Produkt- und Preisseiten, Überschriften, Handlungsaufforderungen, Nachweisabschnitte und die Überarbeitung vorhandener Texte. Führt ein Aussageverzeichnis, verbindet Fähigkeit, Wirkung und Beleg, erhält Einschränkungen statt sie zu glätten und verzichtet auf falsche Dringlichkeit, erfundene Referenzen und manipulative Muster. Achtet auf Anrede, Preisangaben, Rechte an Zitaten und Logos sowie Barrierefreiheit. Standard ist ein Entwurf im Chat, keine Veröffentlichung.

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

Create tests for Diff Studio demo models

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

CAD fundamentals, 3D printing (FDM/SLA/SLS), CNC machining, workshop skills, rapid prototyping methodology, and testing of physical prototypes. Covers fidelity levels, material selection for prototypes, dimensional tolerancing, assembly planning, and the iterate-test loop. Use when building prototypes, selecting fabrication methods, planning physical tests, or choosing between prototyping technologies.

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

Write tests for untested OSS code as a standalone contribution. Identifies coverage gaps, studies the repo's test conventions, and guides the user through writing tests that match existing patterns. Use when contributing tests to an open source repo, looking for a low-risk first contribution, or improving test coverage. Not for writing tests alongside a bug fix — use oss-contribute for that.

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

Research an issue deeply and present all context to the user. but the user writes the code. The LLM investigates code paths, finds relevant files, explains patterns, and identifies constraints. The user thinks through the approach and implements it. Use when ready to start working on an issue after oss-prep-to-contribute. Not for writing tests or documentation as a standalone contribution. Use oss-write-tests or oss-write-docs for those.

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