「single」の検索結果

Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

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

End-to-end Codex-native Amazon FBA research workflow using LaunchFast MCP. Use when the user wants a single report covering product research, IP risk, supplier sourcing, and PPC keyword intelligence. Requires `research_products`, `ip_check_manage`, `supplier_research`, and `amazon_keyword_research`.

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

Use when the user asks to create, convert, style, animate, export, share, or deploy HTML slide decks, presentations, pitch decks, talks, or keynotes; including zero-dependency or single-file output, PowerPoint/PPT/PPTX input, PDF export, browser delivery, visual style exploration, or "loopy slides". Not for general web pages or landing pages.

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

Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews/ChatGPT/Perplexity. Industry detection for SaaS, e-commerce, local, publishers, agencies. Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed, structured data.

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

Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.

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

Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews/ChatGPT/Perplexity. Industry detection for SaaS, e-commerce, local, publishers, agencies. Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed.

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

First-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning.

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

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.

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

Plan, draft, audit, and publish posts and threads for X (Twitter). Use when the user wants to write a single tweet or an auto-numbered thread, build a long-form tweetstorm, remove AI tells from a draft, reverse-engineer the hook from a viral tweet, draft a reply or quote tweet, or plan a week of X content. Tweets and threads publish via the Publora API, which auto-splits long content into a numbered thread. User provides notes or a tweet URL, the skill drafts, the user approves, then it publishes.

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

Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task <task>. Uses get_task, update_task, create_task_comment.

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

ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do", in any language. Picking which task comes next is os-whats-next; this skill is for doing the thing in front of you. First earn the ask: try it yourself, find another route, shrink it to the part only they can do. Then one action per step, commands labelled by what they touch, no jargon. Commands are single lines that prompt for any value - typing hidden for secrets - and confirm in plain words. Afterwards verify their step.

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

Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

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

Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting emerging or newly-coined keywords before competitors arrive, "should we build a cluster or one page", "what do we write next", "we get impressions but no clicks", "our traffic plateaued despite publishing", whether to chase a head term at all, or turning any of it into recurring automation. Also use when asked why an SEO effort stalled despite consistent output. NOT for writing an article, keyword expansion mechanics, or auditing a single tactic for penalty risk.

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

Combines all git commits for a change into a single commit and pushes it to gerrit. Use when you push to gerrit.

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

Generate meaning-carrying editorial data-illustrations in the monotykamary / Linear aesthetic (near-black grayscale, Inter display + mono labels, hairline framed figures) with a single coral accent. This is a GENERATIVE GUIDE, not a template gallery: it teaches the "claim -> geometry" method so any session can invent the RIGHT figure for what a post actually argues, then render it as a self-contained, theme-aware, reduced-motion-safe HTML/SVG figure. Use when writing/illustrating a blog post, essay, spec, or slide and you want a chart, diagram, or illustration that carries a thesis (not decoration) in the house style. Triggers: "make a chart/diagram/illustration for this", "visualize this argument", "monotykamary/Linear style figure", "editorial graphic".

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

Use when deciding whether an anthropology project fits American Anthropologist (AA) and which section to target. AA is the four-field AAA flagship, so the test is significance across anthropology (sociocultural, archaeology, biological, linguistic), not single-subfield novelty. Helps frame the question and pick a section; it does not collect data or conduct fieldwork.

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

Use to understand how Agricultural Systems (AgSy) evaluates a manuscript — single-anonymized peer review with a minimum of two reviewers and an editor decision, desk screening for fit and systems content, what reviewers weigh, and the rapid-review track for Perspectives. Sets expectations and shapes the paper to survive review; it does not contact editors.

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

Use when running the final pre-submission preflight for the American Economic Journal: Microeconomics (AEJ: Micro) via the AEA submission system — single-blind review, the 100-word abstract, JEL classification, the submission fee, format, and the AEA Data and Code Availability Policy. Final checks; it does not draft content.

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

Use when writing the response to an Agricultural Systems (AgSy) revision decision. AgSy review is single anonymized with at least two expert systems reviewers and an editor decision, and revisions often turn on model evaluation, sensitivity/uncertainty, and trade-off framing. The response must convert each reviewer without alienating the editor. Structures the response letter; it does not fabricate new results.

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

Use when a model — a full theory paper's argument or the structural/conceptual scaffolding behind an empirical AER: Insights short-format manuscript — needs to be made minimal, so it carries the single insight in a few pages. Keeps only what the insight requires; it does not develop a general framework.

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

Use when calibrating expectations for the fast, decisive American Economic Review: Insights (AER: Insights) review process — conditional-accept-or-reject decisions, the single-round model, and pre-empting the objections a short paper cannot afford. Explains the process and stress-tests the paper; it does not write the response letter (see aeri-rebuttal).

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

Use when deciding whether a project is the ONE crisp, important, well-identified insight that an American Economic Review: Insights (AER: Insights) short-format manuscript requires, rather than a multi-result paper for AER or a field paper for the AEJ family. Tests single-insight fit; it does not run the analysis.

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

Use as the entry point for any Agricultural Systems (AgSy) manuscript. Routes to the right AgSy sub-skill based on where you are in the lifecycle and which article type (research paper, short communication, perspective, comment, review) fits. AgSy is a systems-science journal, so the router's first job is to confirm there is a real systems question — interactions, hierarchical levels, trade-offs — not a single-factor field trial. It dispatches; it does not draft content.

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

Use when deciding whether a project fits Agricultural Systems (AgSy) and which article type to target. AgSy is a systems-science journal, so the test is a genuine systems question — interactions among components, across hierarchical levels (field → farm → landscape → region → food system), trade-offs, and emergent behavior — analyzed with integrated modelling, NOT a single-factor field trial. Helps frame the question; it does not collect data.

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