3,387 件 ・ 関連度順
概要と使いどころ
Search engine optimization strategies and tactics for organic growth. Use when optimizing content for search, conducting keyword research, performing SEO audits, or building link strategies.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
日本語の概要は準備中です。原文の説明を表示しています。
Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).
日本語の概要は準備中です。原文の説明を表示しています。
Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).
日本語の概要は準備中です。原文の説明を表示しています。
Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).
日本語の概要は準備中です。原文の説明を表示しています。
Check a text fragment for potential secrets (API keys, tokens, passwords) BEFORE sending to chat / committing / publishing. Second protection layer on top of the pre-commit hook — manual gate, user explicitly calls on potentially sensitive text.
日本語の概要は準備中です。原文の説明を表示しています。
Classifies raw pilot request → structured JSON {task_type, class, artifact, budget_estimate, confidence, routing_tag, resolution_path, schema_version, result_type, expected_result_kind, result_kind_resolution, hypothesis_relation}. Keyword-fast (<200ms) or Haiku fallback (<60s). Does NOT create WP or call executor.
日本語の概要は準備中です。原文の説明を表示しています。
Write and optimize prompts for AI-generated outcomes across text and image models. Use when crafting prompts for LLMs (Claude, GPT, Gemini), image generators (Midjourney, DALL-E, Stable Diffusion, Imagen, Flux), or video generators (Veo, Runway). Covers prompt structure, style keywords, negative prompts, chain-of-thought, few-shot examples, iterative refinement, and domain-specific patterns for marketing, code, and creative writing.
日本語の概要は準備中です。原文の説明を表示しています。
Generate semantic + keyword match score. Compares resume content against job description to calculate a fit score and identify gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Operate E2B agent sandboxes using the CLI. Use when user needs to run code in isolation, test packages, execute commands safely, or work with binary files in a sandbox environment. Keywords: sandbox, e2b, isolated environment, run code, test code, safe execution.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates multi-agent workflows by delegating ALL tasks to spawned subagents via /spawn command. Parallelizes independent work, supervises execution, tracks progress in UUID-based output directories, and generates summary reports. Never executes tasks directly. Triggers on keywords: orchestrate, manage agents, spawn agents, parallel tasks, coordinate agents, multi-agent, orc, delegate tasks
日本語の概要は準備中です。原文の説明を表示しています。
Add Qdrant embedding support to v3 WordPress components for RAG chatbot. Implements component-level content chunking for searchable, structured embeddings. Use when adding embedding to new or existing v3 components.
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered diary generation for agents - creates rich, reflective journal entries (400-600 words) with Quote Hall of Fame, Curiosity Backlog, Decision Archaeology, and Relationship Evolution. Generates personal, emotional entries from the agent's perspective. Works best with Claude models (Haiku, Sonnet, Opus).
日本語の概要は準備中です。原文の説明を表示しています。
Build and query a local Markdown knowledge base ("vault"). TWO functions — (1) CONVERT raw files (PDF, Word/docx, PowerPoint/pptx, Excel/xlsx, csv/tsv, images, html, md/txt, json/yaml/code, audio/video) into clean Markdown with retrieval-friendly frontmatter; local-first (pandoc / python-pptx / openpyxl / pymupdf4llm / whisper), with cloud OCR (MinerU) only as a fallback. (2) ANSWER questions over the resulting vault with retrieval discipline — self-monitor coverage, flag missing/lossy content, and propose Maps-of-Content (MOCs). Triggers: "build/sync my local knowledge base", "convert these files to markdown for AI", "整理我的资料库", "把文件转成 md 给 AI 读", "本地知识库", "读我的本地 vault 回答", "这个主题我的资料里怎么说". Not for: one-off web research, or files that are already in a single doc you can read directly.
日本語の概要は準備中です。原文の説明を表示しています。
The harnesses a campaign keeps, read outside a run: which there are and where each came from, what each is made of and what moved from its parent, what each was measured to be, trying one on a task, the audit before a promotion and the blind review at a handover, whether a part earns its place, and changing what makes a harness or what a seat is told about one. Use when the operator asks which harness is current, what a Builder changed, whether a harness is ready to promote or hand over, to run a kept harness on a task, or to change the harness contract. Reading one run is whole-run-investigation's, wording a claim attribution-and-proof's.
日本語の概要は準備中です。原文の説明を表示しています。
Draft commit titles and optional commit bodies using the workspace commit naming convention. Use when the user asks for a commit message, commit text, commit title, or wants commit wording in the format `chore|bugfix|feature - <issue_id(s)> <short description>`.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user wants to find, shortlist, vet, or enrich US web development firms — building, refreshing, or rebuilding marketing sites, landing pages, ecommerce, WordPress/Webflow/Shopify, headless CMS, microsites, and web frontend work. Triggers on "find a web developer for a marketing landing page", "shortlist three Webflow agencies in California", "rebuild our ecommerce site on Shopify", or "pull contact info for these 8 web dev shop domains", even when described indirectly (redesign and rebuild our site, ship a microsite). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer to find-software-developer for custom backend/API/mobile/internal-tool work — anything beyond a website. Defer to find-marketing-agency when scope spans broader marketing beyond the build. Skip in-house web-engineer hires, "how do I build X" DIY questions, hosting/CMS-product comparisons, non-US firms, individual freelancers.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the pure-Go SQLite password identity store, reusable parser, immutable account evidence, idempotent enrollment, portal injection, and login E2E tests. Excludes local JSON database internals and MFA/profile feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain or embed pkg/authclient for portal login, password/TOTP and API-key authentication, native credential transport, configuration parsing, and credential files. Covers authdbctl login wiring; management commands and the admin API have separate owners.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain conditional authentication challenge policies, reusable authchal and user-transform FromDirectives parsers, safe claim substitution, GitHub ID/organization transforms, registered-factor inventory, passwordless WebAuthn selection, verified AMR access claims, and policy revalidation across portal login, refresh, OIDC, and direct authentication.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain injected credential authenticators, method-isolated caching, request-context propagation, and the pure-Go SQLite API-key plugin. Excludes interactive portal password authentication and identity-store provisioning.
日本語の概要は準備中です。原文の説明を表示しています。
Condense the current or given task plan by compressing its wording. Use when the user calls to "condense", "compress", "shrink" or "shorten" the "task", "plan", "spec", or "specification".
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the documents for spelling, capitalization, punctuation, word break, or grammar errors. Use when the user wants to "proofread" or "spellcheck" a document.
日本語の概要は準備中です。原文の説明を表示しています。
Shorten a document toward a target length, given as either `--chars <N>` or `--words <N>`: first tighten the sentences, then drop low-value content, then compress the remaining content into shorter expressions -- each stage entered only while the target is still not met. Use when the user wants to "shorten", "cut down", or "reduce the length of" a document.
日本語の概要は準備中です。原文の説明を表示しています。