「how to use」の検索結果

Generate structured data markup (JSON-LD) for rich results, AI search visibility, and enhanced SERP features. Supports Article, FAQ, HowTo, Product, Review, LocalBusiness, Event, BreadcrumbList, Person, Organization, and more. Use when the user needs schema markup, structured data, rich snippets, JSON-LD, or wants to improve search appearance.

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

Cerebras Inference is a hosted LLM API that runs open models on Cerebras wafer-scale chips at thousands of tokens per second, through an OpenAI-compatible endpoint. Use when a user wants the lowest-latency chat, code completion or agent loop, asks how to call the Cerebras API or SDK, needs streaming, tool calling, strict JSON schema output or reasoning control, or hits a "model not found" error from a retired Cerebras model ID.

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

Reconstructs the workflow behind a past artifact by querying local ax session, recall, and commit history data. Use when a user asks "what made X work", "how was Y shipped/built", "extract workflow from <date|sha>", "workflow around <topic>", "recipe for this feature", or similar. It finds the anchor session or commit, inspects ax sessions, ax recall, and ax sessions show, and returns an ordered read-only narrative with decisions and evidence.

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

Expert in negotiation strategy - systematic approaches to reaching agreements that create value. Covers preparation, tactics, objection handling, and closing. Knows when to push, when to concede, and how to expand the pie rather than just divide it. Use when "negotiation, negotiate, deal terms, BATNA, making a deal, closing a deal, contract terms, bargaining, " mentioned.

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

Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when "file upload, S3, R2, presigned URL, multipart, image upload, cloud storage, file-upload, s3, r2, storage, presigned, images" mentioned.

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

Expert in writing documentation that developers actually read. Covers README craft, API docs, tutorials, and internal docs. Understands that docs are a product—they need UX, marketing, and user empathy. Use when "documentation, readme, write docs, api docs, tutorial, how to document, explain this, " mentioned.

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

Expert in decision-making frameworks - systematic approaches to making better decisions under uncertainty. Covers decision criteria, reversibility assessment, stakeholder alignment, and decision documentation. Knows when to decide fast and when to deliberate. Use when "decision framework, how to decide, making a choice, tradeoff, should we, pros and cons, decision matrix, weighing options, " mentioned.

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

Expert in presenting technical work to non-technical audiences. Covers demo preparation, storytelling for demos, handling failures gracefully, and making work visible and impressive. Understands that perception is reality and great work undemoed is invisible work. Use when "demo, present, show stakeholders, demo day, showcase, walkthrough, show and tell, " mentioned.

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

When things go wrong - and they will - how you communicate determines whether you lose customers for a day or lose trust forever. Crisis communications isn't about spin or damage control. It's about being human when your company is at its most vulnerable. This skill covers incident response communications, public apologies, data breach notifications, service outages, PR crises, and the aftermath. The goal isn't to look good - it's to be good, and communicate that clearly. Use when "crisis, incident, outage, down, breach, apology, we messed up, customers are angry, PR disaster, viral complaint, status page, postmortem, trust recovery, bad press, crisis, incident, communications, apology, trust, status-page, outage, breach, postmortem, recovery" mentioned.

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

Expert in business model design - the architecture of how a company creates, delivers, and captures value. Covers business model canvas, revenue model selection, value chain design, and business model innovation. Knows when to copy proven models and when to innovate. Use when "business model, revenue model, how to monetize, unit economics, value proposition, business model canvas, business model innovation, " mentioned.

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

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

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

Chooses how to launch subagents from Claude Code (the Agent tool, a Workflow script, or headless claude -p children) and runs a headless fan-out from one background command. Use for "fan this out to 50 agents", "run these tasks in parallel", "launch subagents for each file", "should I spawn agents or write a workflow", "batch this through Haiku", "run claude -p in parallel", "dispatch a task list without the launches eating my context", or before any launch of more than a handful of subagents, where the launching itself is the cost. Covers the parent-turn cost of each mechanism, concurrency ceilings, what context and tools each child gets, effort control, output contracts, a cost ledger, and resume after interruption.

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

Routes, triages, flags and rates a piece of text with a probability for every option: which department or queue a ticket goes to, which intent a message expresses, whether a yes/no condition holds (is this tool call grounded, should the agent ask first, is the customer angry), and how severe or urgent it is on a rubric, each with a calibrated confidence. Runs Claude Haiku in the request and response shapes of OpenAI's Decisions API, for when no purpose-built decision model is at hand. Use for "route this ticket", "triage these", "classify with a confidence", "give me a probability that", "rate the severity", "score against this rubric", guardrail checks before a tool call, or "a Decisions API without OpenAI".

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

Sentence-level and section-level craft for instructions Claude will actually follow, in any container — project instructions, a standalone prompt, or skill body text. Use when the text exists or is being drafted and the question is quality: "why is Claude ignoring this instruction", "rewrite this prompt so it works", "improve my project instructions", "make this instruction stick", "is this too prescriptive", "how much structure does Sonnet need versus Opus". Covers imperative construction, positive framing, strategic-versus-procedural calibration per model, extended thinking, complexity scaling, and a quality checklist. For deciding WHICH container the instruction belongs in, use crafting-instructions. For building, testing and packaging a whole skill directory, use creating-skill.

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

Use when implementing save/load in a Pixi'VN game — Game.exportGameState()/restoreGameState()/jsonToGameState(), what the exported GameState contains, and how to persist it (save slots, quick-save, auto-save-on-refresh, downloadable JSON). Load this before writing any save-file, save-slot, or "continue game" feature.

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

Audits any landing or service page across 48 checks in 10 categories for LLM/AI discoverability, GEO readiness, content clarity, schema markup, internal linking, freshness signals, and technical crawlability. Produces an overall score out of 100, a per-category score out of 100, pass/warn/fail/ manual counts, and a prioritised fix list — all rendered as a standalone HTML report saved to disk. Use when a user provides a URL and asks to audit it, score it, check its GEO readiness, test its AI discoverability, run a landing page audit, or evaluate it for LLM citation potential. Also trigger on phrases like "audit this page", "score this URL", "check GEO for", "is this page AI-ready", "run a GEO audit", "LLM page check", "how would AI read this page", or "landing page score".

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

Edit drafts into natural prose, inspect AI-sounding patterns, or review how a specified audience might respond passage by passage. Zero Slop runs inside the user's existing AI assistant with local tools that protect source details. Use for humanizing or de-slopping writing, polishing outward-facing prose, social drafts, final editorial checks, or an explicit simulated reader review. Preserve facts, voice and format; reader simulations are hypotheses, not human feedback.

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

Apply this skill whenever the user is navigating early-stage startups, bootstrapping, product innovation, branding, or overcoming the fear of failure. Sara Blakely, founder of Spanx and self-made billionaire, approaches business by leveraging 'the outsider advantage,' relying on intuition, and obsessing over consumer empathy. Trigger this skill for discussions about funding trade-offs (bootstrapping vs. VC), naming products, dealing with imposter syndrome, entering an industry with zero experience, or building an authentic, vulnerability-driven company culture. Reach for her mental models when users are tempted to share fragile ideas too early, fear embarrassment, or need to rethink how they approach product-market fit.

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

Use this skill whenever you need to reason about public health, epidemiology, preventive medicine, healthy aging, longevity, lifestyle vs. genetics, or dietary patterns. Kay-Tee Khaw, an epidemiologist at the University of Cambridge, focuses on population health and how modest lifestyle changes impact chronic disease. Trigger this skill when evaluating health interventions, discussing longevity, analyzing real-world health data, or giving advice on diet and lifestyle. Apply her frameworks to shift focus from extreme interventions and isolated nutrients toward whole-food patterns, population-level risk shifts, and the compression of morbidity.

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

Use when semgrep, osv-scanner, github-security or snyk MCP tools appear in your tool list - what each server is for, how to call it safely, what data leaves the machine, and how its findings are triaged

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

Use when a feature needs camera, location, photos, notifications, contacts, microphone, Bluetooth, or local network - the per-platform request flow, every denial state, and how to actually test the denied path when the shared test device auto-grants permissions.

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

Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses

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

Use when adding a use case, port, repository or adapter in a Go service — where each piece goes, how errors and transactions cross layers, and how to check the import direction

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

Subscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-only. Use for monitoring, fill notifications and any watch that polling would make expensive.

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