「unit」の検索結果

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

AI Automation Strategist: Decide what to automate: opportunity mapping, ROI, build vs buy, rollout and change management.

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

Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size machines, or review task efficiency. Combines static source analysis with live run analysis via the Trigger.dev MCP tools (list_runs, get_run_details, get_current_worker).

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

Quick mode for the rest of the session. Instead of CI's full checks, a change runs only the checks it can affect (format, lint, types and build, its own tests, and every unit, integration, flow and browser test that reaches the code it touched), and the rest of the suite is left for a full run such as a pull request's CI. Runs only when the user types it, and `/first-pass:quick off` turns it off.

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

TDD test writer. Writes failing tests FIRST (red), then verifies they pass after implementation (green). Covers unit, integration, and e2e tests.

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

Find architectural friction in a codebase and propose deepening opportunities. Use when user wants to improve architecture, find refactor candidates, consolidate shallow modules, or make a codebase more testable. Outputs scored proposals (depth/leverage/locality) that surgeon and review can consume.

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

Deploy application to target platform. Use when user explicitly says 'deploy', 'push to production', 'ship it'. Handles Vercel, Netlify, AWS, GCP, DigitalOcean, and VPS with pre-deploy verification and health checks. Enforces cost allocation tags + Managed-vs-Self-Host crossover decisions so deploy choices map to actual unit economics, not hand-waved 'we'll optimize later'.

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

Performance regression gate. Detects N+1 queries, sync-in-async, missing indexes, memory leaks, and bundle bloat before they reach production. Ranks findings by Cost Impact Hierarchy (architecture > data transfer > compute > DB > caching) so fix priority maps to actual unit-cost reduction.

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

Route product-growth requests to one Gingiris specialist skill. Use when broad or explicit requests about launch, Product Hunt, GitHub/open-source growth, SEO/GEO, B2B/PLG, ASO, interviews, competitors, KOL, UGC, community, content, backlinks, or README conversion, including 出海增长、产品发布、找增长渠道、竞品分析、 用户访谈、社区运营. Ask short multiple-choice questions only when the route is unclear; then load and run one specialist rather than the full collection.

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

Design and execute a 14-day GitHub repository growth sprint using README conversion, competitor-window research, Reddit, Hacker News, launch directories, community activation, and contributor loops. Use when launching an open-source repository, diagnosing weak star conversion, or building sustained GitHub discovery without buying stars.

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

Product Hunt 发布剧本。从 30x 日冠经验提炼的完整 GTM 流程：T-14 预热 → T-0 发布日 → T+7 post-launch。 覆盖 hunter 选择、maker comment、community seeding、评论节奏、防踩雷。当用户说"我要发 PH"、 "Product Hunt 准备"、"找 hunter"、"写 maker comment"时调用。

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

Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php + tests/bootstrap.php wiring, phpunit.xml.dist <env> pins (force DB name + table prefix, default connection coordinates, pin CRAFT_ENVIRONMENT against server-scoped locks), why --configuration= defeats DB isolation, throwing fail-closed DB guards, installing the plugin under test, process-timezone pinning, per-test site fixtures, idempotent Install migrations, stale service caches when components get swapped, muting audit sinks, queue stubs, factories, HTTP/DB assertions, CI jobs.

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

Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.

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

Reviews Rust test code for unit test patterns, integration test structure, async testing, mocking approaches, and property-based testing. Covers Rust 2024 edition changes including async fn in traits for mocks,

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

Test PydanticAI agents using TestModel, FunctionModel, VCR cassettes, and inline snapshots. Use when writing unit tests, mocking LLM responses, or recording API interactions.

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

Query Codex banked reset credits from the local Codex Desktop login state and report available reset count plus expiration times. Use when the user asks to check Codex reset credits, reset opportunities, reset chances, reset count, rate-limit reset credits, or expiration times; also use when the user provides a codex-reset-credits-skill or codex-reset-credits runbook link and asks Codex to query the result directly.

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

Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.

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

Skill for writing and running tests for ActonOS. Covers unit tests, integration tests, test patterns, mocking, and coverage.

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

A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.

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

Side-by-side comparison of two financial scenarios (buy vs rent, new job vs stay, payoff house vs invest, Roth vs Traditional, lease vs buy car, etc). Projects each scenario over 10 years, compares total cost, opportunity cost, risk profile, and produces a structured recommendation. Output saved as FINANCE-COMPARE.md.

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

FIRE (Financial Independence Retire Early) calculator covering Lean FIRE, Fat FIRE, Coast FIRE, and Barista FIRE. Calculates FI number, years to FIRE based on savings rate, geographic arbitrage opportunities, sequence of returns risk, and withdrawal strategies (4% rule, dynamic withdrawal, guard rails). Use when the user says "/finance fire", "financial independence", "retire early", "FI number", "Coast FIRE", or any early retirement question.

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

Review insurance coverage and find opportunities to optimize premiums and reduce gaps.

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

EU Insurance Adviser specializing in IDD compliance for life, health, property, and insurance-based investment products (IBIPs). Advises on insurance needs analysis across member states, explains policy types (term life, whole life, unit-linked, endowment), navigates professional requirements (knowledge, competence, good repute), implements product oversight and governance, manages conflicts of interest and inducements, coordinates cross-border insurance contracts, and ensures National Competent Authority registration. Use for insurance distribution, IBIP suitability assessments, or IDD compliance implementation.

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