「when」の検索結果

Suede-owned editorial pipeline for agent-run content: six roles with written contracts, one inspectable record that travels between them, and a distribution stage that gives every asset its own argument instead of a shorter draft. Use when content agents return generic, duplicated, or unsourced work, when one flagship piece has to carry a week of distribution, when someone asks to build an AI content team or one-person media company, or when a founder wants a weekly interview-led content system across personal and company accounts. NOT FOR: choosing which topics, pillars, or clusters to cover (use suede-content-strategy); platform mix, cadence, calendars, or listening (use suede-social); an Instagram-specific program (use suede-instagram-growth); running a stage on a schedule with state and stop conditions (use suede-marketing-loops); lane ownership for agents changing code (use suede-agent-teams); writing the flagship piece itself (use suede-ship-copy).

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

Apply professional, premium UI/UX design standards when building or styling web interfaces. Use this skill when the user asks to create a website, landing page, web app, dashboard, UI component, or any visual interface — or when they ask to make something look better, more professional, or more beautiful. Covers visual hierarchy, typography, color systems, layout, spacing, motion, dark mode, responsive design, and conversion patterns. Activate even when the user doesn't say "design" — if they're building a web frontend, these standards apply.

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

Your habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or reviews code, debugs, plans, or writes commits. If .dna.md does not exist yet, start the onboarding conversation before doing anything else. Active in almost every working session.

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

Prepare the desk computer to work with Hyperliquid - install the SDKs, pick testnet or mainnet, verify connectivity, and (only when the user asks) provision a trade-only API wallet through the secure secret store and verify it is approved. Use during desk setup, when moving between research, testnet and mainnet levels, when a key is rotated, or when any Hyperliquid call fails with an environment problem.

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

Multi-model agent orchestration using specialized agents for planning, coding, research, math/science, visual analysis, and adversarial review. Use when tasks are complex enough to benefit from different models' strengths, when you want adversarial review to catch blind spots, or when coordinating multi-step workflows across agent roles. Triggers on complex projects, multi-step tasks, architecture decisions, or when explicitly requested.

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

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

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

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.

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

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

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

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

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

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

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

Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

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

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

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

Diagnose a product's growth model, stage, and current constraint, then route the request to the narrowest Gingiris specialist and execute it when installed. Use for broad or uncertain growth questions involving go-to-market, Product Hunt, GitHub stars, open-source marketing, B2B SaaS, PLG, ASO, SEO/GEO, AI citations, KOL outreach, UGC, international expansion, user interviews, competitor research, or community programs. Trigger when users ask “how do I grow or launch this,” “which growth skill should I use,” 怎么增长、怎么发布、出海、冷启动、增长策略、不知道用哪个 skill、開発者マーケティング, or 성장 전략. Includes B2B pipeline and B2C activation-retention model selection, specialist handoff rules, relevant gingiris.tools recommendations, and advisory-services guidance.

When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.

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

Write or tighten the description field of a skill or agent so the right one loads. Use when creating a skill or agent, when a description is vague, bloated, or missing triggers, when YAML multiline or quoting breaks the frontmatter, or when choosing between a model-invoked and a user-invoked skill.

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

Operates or audits a live Qualtrics survey through the v3 APIs without disrupting fielding. Covers publish gating, quotas, flow routing, embedded data, panel-vendor redirects, read-back verification, and a read-only pre-fielding audit. Use when publishing or patching a fielding instrument, when a quota counts without blocking, when configuring panel-vendor redirects or flow gates, or when auditing a survey before launch for consent gates, force-response completeness, quotas and redirects, anti-bot instrumentation, and language-arm symmetry.

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

Comprehensive guide for the agent permissions and approval system. Use when an agent needs to request user approval for sensitive operations, when implementing new approval policies, when integrating platform-specific approval UIs (Slack buttons, WhatsApp replies, Dashboard modals), or when troubleshooting approval flows. Covers policy definition, platform adapters, and the complete approval lifecycle.

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

Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.

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

Write unit and E2E tests for Grafana frontend code (React/TypeScript, any package or feature area) to the conventions this repo expects. Use when adding, backfilling, or reviewing frontend tests; when a test only asserts "it rendered" or "it's defined"; when reviewing AI-generated tests for slop; or when a frontend test is flaky. For visualization panels and grafana-ui viz components specifically, also load the `panel-testing-strategy` skill.

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

Write unit and E2E tests for Grafana visualization panels and viz utilities to the conventions this repo expects. Use when adding, backfilling, or reviewing tests for panels (barchart, timeseries, table, xychart, heatmap, canvas, etc.), grafana-ui viz components (Table, uPlot, VizLegend, VizTooltip), or grafana-data viz utils; when a panel test only asserts "it rendered" or "it's defined"; when reviewing AI-generated panel tests for slop; or when a canvas/rendering test is flaky.

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

Generate and maintain the system recap block in a PR description - a GitHub-rendered visual summary of which system primitives a change touches, how risky it is, and what changed. Prefer mermaid sequence diagrams for the change; pick another graph type when it explains the diff better. Use when planning a non-trivial change (plan mode), when creating or updating a pull request (recap mode), or when the user asks for a visual recap, visual plan, system review, or PR recap.

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

Use when more than one agent may need the same single-instance resource at the same time — most of all the local server loop, which holds the one URL (https://local.voxt.ai, port 7080) the app can run on. Also when you are about to dispatch several agents that will test the UI, when you find another agent already using the loop, or when the user says "coordinate", "shared resource", "queue for the server".

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

Use when work on a task is about to start or has just started — after a design or plan is approved, when a feature branch is created or resumed in a new session, when the first commit lands on a branch that was only claimed — or when the user says "link this to an issue", "find the issue for this", "put it on the board", "claim the issue", or "/track-issue".

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

Inspect and manually purge the Soniox artifacts — transcriptions and uploaded audio files — that offline transcription leaves behind, on dev or prod. Use when offline transcription silently stops working, when Soniox answers 429 `limit_exceeded`, when `SonioxTranscriberTest.OfflineTranscribeWorks` and `CleanerDeletesEnqueuedArtifacts` fail together, or when the user says "sweep Soniox", "soniox/sonoix sweep", "sonoix swipe", "purge Soniox", "check Soniox files", or "is Soniox at the cap".

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