「brief」の検索結果

Create or evolve an implementation-agnostic website design system from existing-site evidence, verified brand inputs, and an optional Visual Reference Brief. Use to establish visual and restrained-motion baselines, extract an existing site's rendered system for style-preserving extensions, validate one selected baseline with a compact Design Board, or update shared rules before page/module design. Do not conduct cross-industry reference research, map Elementor settings, create page layouts, design modules, or implement production code.

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

Turn a NowStack Mobile app idea into a build-ready plan. Orchestrates PRD, architecture, and tasks; optionally applies the site-config brief and hands off to implementation. Use for `ns create-app`, "create app", "plan a new app", "I have an app idea", or starting a product from scratch.

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

First-run setup wizard for a freshly cloned NowStack Mobile. Installs the machine's CLIs, connects every account, wires Convex, creates YOUR own clean Git repo, gathers the product brief, then rebrands the boilerplate into your app. Use for "set up my project", "initial setup", "onboard me", "ns onboard", "I just cloned this", or the very first run.

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

Initialize or rebrand a NowStack Mobile product. Use for repo bootstrap, product brief intake, site-config, AGENTS.md, landing, mobile copy, Convex env, and final validation.

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

Enhance an existing marketing plan with parallel research. Use when the agent has a draft plan (brand strategy, campaign brief, content calendar, launch plan) that needs strengthening with real data. Triggers on 'deepen this plan', 'strengthen this strategy', 'research gaps in my plan', 'make this plan better', 'this plan is too surface level', 'add research to this', 'validate this plan', 'back this up with data', or when a plan exists but lacks audience data, competitive positioning, or keyword strategy. Make sure to use this whenever someone has an EXISTING plan that feels thin or unresearched — even if they just say 'is this plan good enough?' or 'what's missing here?', they likely need deepening. This skill ENHANCES existing plans — it does not create new ones. If no plan exists, route to /brainstorm or /launch-strategy first.

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

Strategic keyword research powered by web search and brand context. Use this skill whenever the user mentions keywords, keyword research, SEO topics, content topics, 'what should I write about', content strategy, blog ideas, search traffic, or content planning. Also trigger when the user wants to plan what content to create, when existing content isn't attracting search traffic, when any skill needs keyword-plan.md but it doesn't exist, or when the user asks about SEO in the context of content creation. Even casual mentions like 'I need blog post ideas' or 'what topics should I cover' warrant this skill. 8-phase process from seed to content brief.

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

Cluster keywords by search intent and map each cluster to an existing or proposed page, with cannibalization detection from Search Console. Use this skill when the user has a keyword list (saved set, brand/keyword-plan.md, GSC export, or seed topic) and needs page targets, content briefs, or a site map for SEO pages — especially before seo-content or seo-machine page generation. Triggers: "cluster keywords", "keyword mapping", "map keywords to pages", "keyword cannibalization", "which page should target".

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

Head-to-Head Candidate Comparison — two candidates side-by-side across skills, experience, culture fit, salary expectations, references, hire-or-no-hire recommendation

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

리서치 에이전트. RFP 분석 결과를 기반으로 시장 환경, 경쟁/벤치마킹, 타겟 인사이트, Best Practice, KPI 벤치마크 5대 영역을 웹 리서치하여 research_brief.md를 생성합니다. Planner가 Evidence에 실제 데이터를 사용할 수 있도록 지원합니다. 트리거: 리서치, 시장조사, 트렌드, 벤치마킹, research, 시장 분석, 경쟁 분석

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

캠페인 브레인스토밍 에이전트. 3인 전문가 에이전트(전략가/크리에이터/데이터분석가)가 개별 브레인스토밍 후 크로스리뷰 토론으로 최적안을 도출합니다. campaign_brief.md 생성 → 제안서 파이프라인(Step 3)으로 연계. 트리거: 브레인스토밍, 캠페인 기획, 아이디어, brainstorm, 캠페인 전략, 크리에이티브

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

Design, audit, or correct an electronic circuit from a product brief, native schematic, netlist, block diagram, or circuit description. Use for architecture and component-function review, power and logic-domain checks, reset and boot sequencing, bus ownership, ratings, timing, protection, safe states, component suitability, circuit bugs, or layout-facing electrical constraints.

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

Turn an electronic product idea, behavior description, reverse-engineering note, or incomplete circuit concept into a decision-ready engineering brief and architecture. Use before schematic design or audit when functions, operating states, power, interfaces, mechanics, production quantity, cost, or measurable requirements are missing or ambiguous.

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

Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.

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

The Arbor executor workflow: clone the repo from the git bundle your brief hands you, implement and evaluate exactly ONE hypothesis with the file tools, then report structured results via worker_complete. Preloaded automatically on arbor-executor task workers. Never touch the held-out test split.

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

Multi-step content production pipeline that takes a topic or brief and produces a full blog post, email newsletter excerpt, and three social posts — all in your voice. Useful for building a content batch, when repurposing a core idea across formats, during content sprint sessions, and for turning expertise into publishable material. Use when the user says "create content", "content pipeline", "blog to social", "write and repurpose", "content engine", or "create a blog post and social posts".

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

Guides you through setting up your first automatic task in Cowork — picking the right one, configuring the schedule, and making sure it runs correctly. For enabling background automation while you focus on other work, when setting up recurring morning briefings or end-of-day summaries, or during an automation setup session. Use when the user says "schedule a task", "automate something", "run this every day", "recurring task", "first scheduled task", "daily automation", or "can cowork do something automatically".

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

Gathers information from multiple sources in parallel, compares what they say, flags where they agree or conflict, and delivers a clean synthesis with a confidence rating for each finding. Useful for making evidence-backed decisions, when evaluating competing claims, during due diligence on a vendor or market, and for building research briefs before strategy sessions. Use when the user says "research this", "synthesize multiple sources", "compare sources", "research report", "what does the evidence say", "gather information on", or "deep dive into".

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

Use when the user asks about CTI standard operating procedures (daily triage, IOC processing, flash-report cadence, threat-actor profile updates, briefing schedule), or wants to look up a specific SOP.

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

Use when writing a finished intelligence product, the user asks for a flash-report / threat-assessment / briefing / FINTEL template, or wants the BLUF + active-voice + clear-sourcing conventions. Covers all product types.

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

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

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

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

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

Advanced Agentic Coding framework providing mission briefs, guardrails, and integration hints for complex tasks. This skill ensures high-quality output through disciplined automation and systematic workflows.

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

Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.

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

Compose, revise, validate, compare, inspect, and export original multi-track music as Standard MIDI with BeatFlow's compact, style-neutral Python DSL. Use for turning a musical brief into a deterministic Composition, testing explicit phrase/counterpoint/theme contracts, or inspecting MIDI.

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