3,237 件 ・ 関連度順
概要と使いどころ
Plan, write, time, style, and validate motion-graphic beats for long-form talking-head HyperFrames videos. Use when Codex is asked to add or improve visual beats, glassmorphism lower thirds, crumpled-paper full-screen takeovers, transcript-synced callouts, pacing coverage, YouTube retention graphics, or render-ready overlays in an existing HyperFrames video project.
日本語の概要は準備中です。原文の説明を表示しています。
Governs the Claude Code/Codex Skill surface: reconciles source/install/catalog-visibility drift without losing cold capability. Use when users ask how many Skills load, why the catalog is truncated, want routers visible while other bundles stay cold, or need duplicate/superseded-Skill or old-cache cleanup. Not for building a marketplace manifest (use marketplace-dev) or repo audits (use marketplace-health-check).
日本語の概要は準備中です。原文の説明を表示しています。
Entry point for local AI conversation history across Claude Code, Codex and Kimi CLI: routes each request to the reader or continuation skill that owns it and keeps the cross-provider inventory. Use when the platform is unknown or plural ("what was I working on", "we discussed this once") and for any Kimi CLI history. When platform and action are already clear, load that skill directly.
日本語の概要は準備中です。原文の説明を表示しています。
Fixes web search on an agent whose model backend can't run it: a relay/reseller proxying Claude or Codex returns empty instead of failing. Use when web search returns nothing, a model insists a shipped product doesn't exist, someone wants to give an agent internet access, or the user is on a third-party base URL, relay, or 中转站. Diagnoses which built-in tools are dead, removes them, and installs a working replacement.
日本語の概要は準備中です。原文の説明を表示しています。
Bridges Claude Code and Codex sessions when native tools can't reach the target. Use for 跨产品通信 / 脚本回帖 / 送达排查: cross-product messages, hooks or scripts posting to a session, verifying delivery (Held messages included), shared-work ownership, or an inbound peer assertion. Not for same-product or parent/subagent messaging (use native tools), spawning agents, moving full history, or cross-machine pairing (deprecated).
日本語の概要は準備中です。原文の説明を表示しています。
Multi-path parallel product analysis with cross-model test-time compute scaling. Spawns parallel agents (Claude Code agent teams + Codex CLI) to explore product from multiple perspectives, then synthesizes findings into actionable optimization plans. Can invoke competitors-analysis for competitive benchmarking. Use when "product audit", "self-review", "发布前审查", "产品分析", "analyze our product", "UX audit", or "信息架构审计".
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator handoff. Use when a repo won't run, a teammate onboards, hook output duplicates, or commit/push/conflict needs guarding. Not for lost-commit recovery (use git-safety-net), GitHub ops (use github-ops), or history scrubbing (use github-sensitive-data-cleanup).
日本語の概要は準備中です。原文の説明を表示しています。
Create visual concepts, image-generation prompts, and optional AI-generated images for product hero images, marketing creatives, social posts, ads, ecommerce PDP visuals, and general visual design tasks. Use when the user asks for visual strategy, image prompt writing, product/marketing image direction, or direct text-to-image generation. In Codex environments use the built-in imagegen tool; elsewhere use the bundled script backed by the apiz CLI.
日本語の概要は準備中です。原文の説明を表示しています。
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user wants to turn past AI coding sessions into reusable skills, asks "what could I make into a skill", "mine my lore", "forge skills from my history", or points at a .specstory/history directory.
日本語の概要は準備中です。原文の説明を表示しています。
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze conversation histories from multiple AI tools (Claude, Codex, Gemini, Qwen, Cursor) and generate themed daily/period work summaries. Filter by date or time window.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-vendor AI image generation with authentication-aware parallel dispatch. Routes to Codex (gpt-image-2 via ChatGPT OAuth) and Pollinations (flux/zimage, free with signup). Gemini provider is present but disabled by default (requires billing). Use for image generation, image creation, visual asset generation, and AI art.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.
日本語の概要は準備中です。原文の説明を表示しています。
The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.
日本語の概要は準備中です。原文の説明を表示しています。
Sets up email on the user's own domain, such as hello@yourdomain.com, a real mailbox that sends and receives, with DropTheHassle. Use when the user wants domain email, a professional email address, an inbox like info@ or hello@ on their domain, or asks "can I get email on my domain". Checks the domain is active with site_status, then hands the human a checkout.stripe.com payment link from get_email_checkout_link (main inbox €5 / $5 a month). The agent never pays and never reads the mail.
日本語の概要は準備中です。原文の説明を表示しています。
Finds a free domain name for the user's website and hands them a payment link to buy it, with DropTheHassle. Use when the user wants to buy a domain, find a domain name, check if a .com is available, "get a .com" or "my own domain" for a site. Checks real availability and price with search_domain or the DropTheHassle domain search API, suggests a short list, and after a yes returns a checkout.stripe.com link the human pays. The site goes live on the name with HTTPS and no DNS. The agent never pays.
日本語の概要は準備中です。原文の説明を表示しています。
Connects a domain the user already owns (bought at another registrar) to their DropTheHassle site, free, with one A record. Use when the user says "use my own domain", "connect my domain", "add a custom domain", "point my domain to my site" or already has a .com at GoDaddy, Namecheap, Cloudflare or similar. Gets the A record from DropTheHassle, shows it to the human to set at their registrar, then checks HTTPS is live. Never edits DNS at the registrar for them. For a name they don't own yet, use buy-domain.
日本語の概要は準備中です。原文の説明を表示しています。
Researches a person across podcasts and YouTube for interview or meeting prep: where they appeared, their own words, who discusses them. Uses arcmira.
日本語の概要は準備中です。原文の説明を表示しています。
Watches a company or topic on podcasts and YouTube: what was said lately (shows, counts, momentum, quotes), then an Arcmira monitor to keep following it.
日本語の概要は準備中です。原文の説明を表示しています。
Compares two podcasts or YouTube shows side by side: size, latest episode, what each talks about, what both cover, and shared sponsors. Uses arcmira.
日本語の概要は準備中です。原文の説明を表示しています。
Sponsor and ad-read research on podcasts and YouTube: who sponsors a show, or which shows a brand sponsors, how often, since when. Uses arcmira.
日本語の概要は準備中です。原文の説明を表示しています。
Finds exact spoken quotes and clip-ready moments on podcasts and YouTube: verbatim words, speaker, date, a timestamped link, clip start and end. Uses arcmira.
日本語の概要は準備中です。原文の説明を表示しています。
Answers what YouTube shows and podcasts said: transcripts, who was mentioned, sponsors, recommendations, momentum. Use for the arcmira MCP server or CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.
日本語の概要は準備中です。原文の説明を表示しています。