「product」の検索結果

typed trigger 신호는 production 공급자 grep으로 도달성 판정

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

Produce a UGC-style talking-head video ad end to end on the MaxFusion MCP — research the product with user-supplied competitor leads, tear down 5 competitor Meta ads and 5 organic TikToks, write a pain-driven script that sounds like a person talking (never like an ad), reverse-prompt a rights-clean photoreal actor from a user-supplied reference photo, generate two chained 10-second Gemini Omni clips that play as one continuous take, and ship a single seamless 9:16 MP4. Use whenever the user wants a UGC ad, a talking-head ad, an ad for an app or product, mentions Omni or Gemini Omni Flash, drops an actor photo and asks for a video ad, or says anything like "make me some UGC", "let's make ads for X", or "another variation". Built for Claude Code (local ffmpeg); degrades to Claude app with documented fallbacks.

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

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

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

Turn a product idea into a repeatable manual process you can start delivering today. Use to design manual-first products before writing any code.

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

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

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

Validate Azure deployments against functional, security, performance, and operational criteria before production release. Use this skill when users ask for readiness checks, health verification, or production sign-off gates. Covers Well-Architected Framework validation, SLA verification, and release readiness.

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

6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.

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

Patterns for vibe coding that produce production-quality output instead of garbage. Covers prompt engineering for AI coding, verification without reading every line, accept/reject/refine decision framework, architectural guardrails, context management (CLAUDE.md, .cursor/rules), TDD-driven vibe coding, screenshot-driven development, diff review discipline, and the anti-patterns that destroy quality. Activate on: "vibe coding", "AI coding quality", "Claude Code workflow", "AI-assisted development", "how to use AI for coding", "coding with AI", "agentic engineering workflow", "AI code quality", "vibe code without garbage", "production quality AI code", "CLAUDE.md setup", "cursorrules setup", "pre-commit hooks for AI", "TDD with AI", "test-driven vibe coding". NOT for: multi-person collaborative coding sessions (use cooperative-vibe-coding), building AI/LLM applications (use ai-engineer), prompt engineering for non-coding LLM use cases (use prompt-engineer).

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

Expert in turning data visualizations into compelling video and animation content for social media and marketing. Activate on: data commercial, animated chart, data storytelling video, chart animation, Remotion data video, Motion Canvas, Flourish animation, D3 animation, data viz social media, dashboard recording, data narrative video. NOT for: static data visualization (use data-viz-2025), general video editing (use video-processing-editing), full video production pipeline (use ai-video-production-master).

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

What you can build and do with an always-on AI agent that has episodic memory. Covers concrete product ideas, workflows, emergent capabilities from persistence plus memory, and real-world examples of deployed persistent agents. Helps you go from "I have the architecture" to "here's what it actually does for me." Activate on: "what can an always-on agent do", "persistent agent use cases", "agent applications", "proactive agent ideas", "what to build with episodic memory", "always-on agent product", "personal AI assistant ideas", "/always-on-agent-applications". NOT for: building the architecture (use always-on-agent-architecture), designing inputs (use always-on-agent-inputs), safety and privacy (use always-on-agent-safety).

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

Build production-ready LLM applications, advanced RAG systems, and intelligent agents. Implements vector search, multimodal AI, agent orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM features, chatbots, AI agents, or AI-powered applications.

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

Product Research / 产品研究编译器：当用户要围绕一个产品问题做系统调研、竞品证据、替代方案、行业信号、 用户与市场研究、最佳实践提炼、产品候选池、本地 HTML 研究看板、可视化研究报告或跨职能 Dashboard 时使用。 当用户只有大白话、模糊方向、业务愿望或 Roadmap/PRD 前置材料想法，需要先转成清晰研究目标、研究问题和输出要求时也使用。 适合把研究转成 Research Project、学习报告、证据矩阵、PM 决策看板、候选池、模板、实践任务、业务判断、商业化输入或高门槛应用研究前置。适合“系统研究一个主题” “整理到 Obsidian”“做深度专题”“研究行业最佳实践”“概念解读”“概念源流”“PM 技术评审提问脚本” “行业演进看板”“这个主题对我的产品决策有什么用”“让我系统学会并输出 learning report HTML”。不适合创建 Skill、评审 SKILL.md、普通即时搜索或一次性摘要。 当用户已经要在明确候选项中选一个、需要最终推荐和排除理由时，应使用 decision-research。 当 decision-research 或 grill-me 返回一个可研究、可关闭的精确证据 gap 时，也使用本 Skill 只补 Evidence Delta。

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

方案到交付 Workflow：当用户显式调用 `$solution-to-delivery`，或明确要求运行“方案到交付”完整流程时使用。 把已确认产品方案转成经过独立 Review 的 PRD、适用的 UI/HTML/截图、版本拆分和 Product Delivery Package；当前 Agent Runtime 只做 Package 发布 dry-run，真实写入保持 authorization_required。

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

交付闭环：当用户显式调用 `$delivery-loop`，或明确要求进入“交付闭环”时使用。 面向已有 PRD、UI/HTML、截图或 Product Delivery Package 但仍有 Review 缺口的场景，在独立评审与定点修订之间最多循环三轮，直到 package_ready 或进入 Human Gate；不用于从模糊问题开始。

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

竞品决策分析 / Competitive Decision Brief：当用户要调研竞品、替代方案、新产品、SaaS/AI 产品或市场信号， 并希望把官网、定价、评论、文档、更新日志、登录态走查、截图或浏览器取证转成产品定位、路线图、定价、 功能优先级、差异化、Go/No-Go 或 PRD 输入时使用。核心行为是先锚定产品决策，再选择证据渠道， 最后输出可行动的 Product Decision Brief；不要把它降级成泛泛功能清单、纯 UX 走查或“点完所有按钮”报告。

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

Use when publishing a local PRD Markdown file to DingTalk Docs or Drive with version-history preflight and read-back, or when validating an approved Product Delivery Package through its fail-closed dry-run path. Package mode real writes require a trusted host approval capability and are unavailable in the current Agent runtime.

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

Content-addressed baseline-archive epoch partitioning. Partition baseline_archive.jsonl + the self-improving hub's baseline serving by a HASH of the full baseline-production+measurement spec — when the spec (margin_rule, fitness/margin logic version, the 4 roles' model+source, rubric/dim-set, bench, seed-pool identity) changes, the hash changes → a new epoch series (like seed-gen gen-*). Triggered by "baseline epoch", "baseline 아카이빙", "epoch partition", "spec hash", "content-addressed", "margin_rule namespace", "production logic 구분", "baseline 하위 서빙" keywords.

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

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises.

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

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. Use AFTER a plan exists. For validating the idea itself before planning, use /mk:office-hours first.

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

Use when running an autonomous multi-hour build of a green-field product — orchestrates planner → contract → generator ⇄ evaluator loop with adaptive scaffolding density per model tier. Triggers on /mk:autobuild, "build me a kanban app", "build a retro game maker", "autonomous build", or any green-field product spec. NOT for scoped single-task work (see mk:cook); NOT for initial project scaffolding only (see mk:bootstrap).

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

YC-style product strategy assessment with forced questions and CEO scope modes — adapted from gstack /office-hours pattern

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

Orchestrator for the Product Design skill set — turn early ideas into reviewable prototypes. Routes to the right sub-skill (get-context, research, audit, ideate, image-to-code, url-to-code, prototype, qa, share) based on where you are in the design process. Use when the user gives a high-level design goal like "design a UI for X", "prototype this idea", "rebuild this screen", "review our flow", or isn't sure which design step they need. Delegates to design-* skills.

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

Clarify the brief BEFORE any design work to avoid building the wrong thing. Interrogates goal, user, constraints, success criteria, and scope, then writes a short context doc the other design skills consume. Use when the user says "let's design X", "build a UI for Y", "get context", "clarify the brief", or kicks off any product-design task without a clear spec. First stage of the Product Design set — highest leverage for reducing rework.

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

Build visual territories (mood boards) for team alignment before production. Groups references into 2-4 named territories, each with palette, texture, typography feel, and 4-6 generated sample tiles, so a team can agree on a direction. Use when the user says "moodboard", "visual territories", "align the team on a look", "reference board", or needs stakeholder sign-off on aesthetic before generating final assets. Part of the Creative Production set.

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