425 件 ・ 関連度順
概要と使いどころ
Build MindNode-inspired mind mapping interfaces — 8 node shapes, 27+ themes, layout algorithms (horizontal, vertical, radial with D3), keyboard shortcuts, focus mode, dual view. React + xyflow/react v12 + Zustand + Tailwind. Triggers on mind map, visual thinking tool, node-based diagram, brainstorm canvas, MindNode.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creative work is requested with no approved design, or a raw idea or repository must be developed into an approved design document. Not for work with an approved design in context.
日本語の概要は準備中です。原文の説明を表示しています。
Plans and tracks tasks in .claude/harness/plans.json. Use when creating plans, adding tasks, updating markers, checking progress, or brainstorming an idea into tasks.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use before /plan-ceo-review or /plan-eng-review.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when brainstorming ideas, generating raw material, or starting the creative phase of a writing project. Invoke for topic exploration, idea generation, angle discovery, or producing abundant raw content before organizing.
日本語の概要は準備中です。原文の説明を表示しています。
AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions); tech selection; ADR research; migration/refactor planning; performance/security analysis; tests; code reviews; any spec/plan/design/ADR referencing project. WRITE MODE — NET DELTA vs. last doc sync: additions/modifications/REMOVALS/deprecations of previously-synced code or decisions (docs revert: delete BCU file/ADR), AND rollbacks. User signals: sync docs/done/ready to commit/pre-commit/record decision. Auto-fires before final task-completion reply. WRITE MODE does NOT fire on: brainstorming, generic/read-only Q&A, in-session try-and-undo with no net change, already-synced.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
30 → 5 → 15 funnel for brainstorming new features on the existing Forge codebase. Use when adding capability to a mature install, not for greenfield.
日本語の概要は準備中です。原文の説明を表示しています。
Translate strategy into a balanced scorecard, strategy map, OKR bridge, and executive initiative portfolio with clear measures, targets, and owners. Use when leadership needs strategic alignment, portfolio prioritization, or a management dashboard tied to outcomes. Do not use for ad-hoc brainstorming with no strategic horizon.
日本語の概要は準備中です。原文の説明を表示しています。
Generate tailored SaaS and product marketing ideas across organic, paid, community, partnerships, product-led growth, retention, and launch channels. Use when the user asks for `/marketing-ideas`, marketing brainstorms, launch ideas, channel ideas, growth tactics, or a prioritized marketing plan.
日本語の概要は準備中です。原文の説明を表示しています。
在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能或修改行为。在实现之前先探索用户意图、需求和设计。
日本語の概要は準備中です。原文の説明を表示しています。
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
日本語の概要は準備中です。原文の説明を表示しています。
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic roadmap management for GitHub repositories. Syncs ROADMAP.md with GitHub Issues and labels, bootstraps roadmap files from scratch, runs brainstorming sessions with boundary checking, and provides quick status summaries. Use when managing project planning, syncing roadmap state, or exploring feature ideas.
日本語の概要は準備中です。原文の説明を表示しています。
Structured ideation for technical problems: divergent generation, constraint framing, and convergent selection. Use when stuck on a design, naming, architecture, or feature approach and need fresh options.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.
日本語の概要は準備中です。原文の説明を表示しています。
Full SRS workflow: Brainstorm → Spec → Plan (per-section files) → User Review → SRS Generation → Validation → Improvement Report → Context Save. Use when user provides a project topic and wants a complete requirements pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 2 of the SRS workflow. Reads projects/{slug}/brainstorm.md and writes a comprehensive spec.md. No word limit.
日本語の概要は準備中です。原文の説明を表示しています。