「how to」の検索結果

Debug GitHub Actions workflows by downloading logs, analyzing summaries, and understanding how agentic workflows and the AWF firewall work together.

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

Show the codeArbiter command catalog — the public command list and what each routes to.

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

Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

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

Mobile, tablet and desktop are different paradigms, not one layout scaled. Use when designing responsive layouts or deciding what each breakpoint shows.

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

Show a table and its map, diagram, timeline or chart together, with selection synced both ways. Use when data appears in two representations at once.

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

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

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

Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.

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

Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships.

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

Optimize existing blog posts and web content for GEO (Generative Engine Optimization) — AI search visibility on ChatGPT, Perplexity, Claude, and Google AI Overviews. Use whenever a user provides a blog URL or pastes existing content and asks to optimize it for AI search, rewrite for LLM visibility, improve GEO score, make content answer-first, add FAQ sections, restructure headings for AI retrieval, improve citation potential, or audit content for AI readiness. Also triggers on "GEO optimize this", "make this AI-search ready", "rewrite for Perplexity", "optimize for ChatGPT", "optimize for Google AI Overviews", "improve AI visibility", "reformat for AI search", "make this content citation-worthy", "content isn't showing up in AI search", "why isn't my blog cited by AI", "GEO audit", "answer-first rewrite", "restructure for AI", "make my blog AI-friendly", "improve LLM citability". Do NOT trigger for writing new content from scratch — use geo-content for that.

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

Use when the user asks which paad skills exist, what a paad skill does, which one fits their situation, or how to invoke one — including "what can paad do", "list the paad skills", "is there a paad skill for X", or a request for the arguments of a named paad skill

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

How the desk watches markets and the account between trades using Grok Bot routines and WebSocket or polling watches - the desk brief, book checks, funding and price watches, alert conditions and what a watch may and may not do. Use when the user asks for briefings, alerts, "watch X" or scheduled checks.

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

Prepare a git repo before new work: review uncommitted changes, fix .gitignore, delete merged branches, end on clean main, or inspect one branch before deciding. Don't use for dead code, commit-and-push, releases, LICENSE files, or git how-tos.

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

Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"

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

Use when an "enable observability" card asks for rum on a frontend, or web.* signals are unbound - how the developer collects Core Web Vitals and page views (web-vitals to the app's own endpoint as log lines, or Sentry / PostHog), what each event must carry, and what stays out of it

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

Use when an "enable observability" card asks for metrics, traces or logs - what the developer task must add per language (Go, Node/TS, Python, Java/Kotlin, .NET, Ruby, PHP), the zero-code agents, the OTEL_* environment variables and resource attributes, and how to reach GCP, AWS, Vercel or a plain OTLP endpoint

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

Use before proposing error definitions (propose_error_definitions) - how to read an error group, pick its category and action, write a match that catches one kind of error and nothing else, and when a definition should not be proposed at all

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

Use when you want deterministic evidence for a review - which already-installed scanners may be run against the checkout, their exact read-only invocations, how to triage their output, and what must never be run or installed

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

Use when writing or changing analytical SQL or a dbt model — CTE structure, window functions, grain and join correctness, dbt data tests, unit tests, contracts and incremental models, and how to run them

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

Use when a task is in code_review - how to read the diff, which findings block, and the verdict move

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

Use when adding a screen, a tab, a deep link, or back-navigation handling - the per-stack navigation APIs, state preservation, auth-boundary resets, and how to verify a deep link actually opens the right screen.

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

Use before any review_criterion approval or column move - the evidence each verdict needs, how to treat skipped, blocked and intermittent cases, and which exit a blocker takes

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

Use when capturing what a feature must do - write testable user-story requirements that state WHAT and WHY, never HOW, with assumptions made explicit

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

Use when designing or building any screen, section or component that a user sees — visual hierarchy, typography, colour, spacing, states, forms and how to avoid the generic AI look.

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

How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.

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