「product」の検索結果

Generates a structured attorney work product memorandum from an initial client consultation for commercial litigation. Extracts verifiable facts from uploaded documents, builds a chronological narrative, identifies parties and contracts, flags preliminary legal claims and defenses, and produces a prioritized action plan. Triggers at matter intake when a business client needs a foundational case evaluation document for a pre-filing commercial dispute.

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

Generates California-compliant privilege logs for withheld or redacted discovery materials under CCP 2031.240. Use when the user mentions privilege log drafting, California privilege log, CCP 2031.240, attorney-client privilege logging, work product designation, Evid. Code 952/954, CCP 2018.030, redaction logging, meet-and-confer privilege disputes, waiver analysis, common interest doctrine, or asks for help documenting withheld documents. Also trigger on references to Hernandez v. Superior Court, Costco Wholesale, or Wellpoint.

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

Drafts a BSA/AML Risk Assessment for U.S. financial institutions per FinCEN, FFIEC, and OCC standards. Evaluates inherent risks (customer, product, geographic, transaction, third-party), control adequacy, and residual risk. Use when preparing annual BSA compliance assessments, post-acquisition integration reviews, or when business changes trigger reassessment under 31 U.S.C. § 5318(h).

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

Citation format and verification protocol for legal documents that draw on Bates-stamped source records. Defines the bracket citation format, multi-source citation rules, quotation handling, the verification pass that runs before output, and the [UNVERIFIED] flag protocol. Use this skill any time another skill produces a legal work product that cites Bates-stamped pages, including medical chronologies, deposition summaries, demand letters, case briefs, and discovery responses. Also use any time the user asks how to format a citation or verify that a claim is supported by the source.

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

Bridge the gap from product specifications to implemented features. Document requirements, acceptance criteria, tech design, and track implementation progress in Notion.

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

Help determine pricing strategy for a product or service using minimalist entrepreneur principles. Use when setting initial prices, considering price changes, or figuring out what to charge.

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

Help founders develop a strategy to acquire and sell to the first 100 customers. Use when someone has a product and needs a customer acquisition plan, or is struggling with early sales.

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

Create distinctive, production-ready frontend interfaces with high visual quality. Use this skill whenever the user asks to build, design, or improve any web UI — including landing pages, dashboards, components, app screens, forms, or interactive widgets. Also trigger when the user says "make this look better", "redesign this", "add polish", "build a UI", "create a page", "style this", or references HTML/CSS/JS, React, Vue, Svelte, or any frontend framework. If the request involves any visible output rendered in a browser, use this skill — even if the user hasn't explicitly said "design." This skill produces intentional, memorable interfaces that avoid generic AI patterns.

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

Create a minimalist marketing plan focused on building an audience through free, authentic content. Use when someone has product-market fit (~100 customers) and wants to scale through marketing or needs a content strategy.

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

Create and evolve design systems with design tokens, component architecture, accessibility guidelines, and documentation templates. Ensures consistent, scalable, and accessible UI across products.

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

Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.

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

Use Angular CLI and development tools effectively in Angular v20+ projects. Use for project setup, code generation, building, testing, and configuration. Triggers on creating new projects, generating components/services/modules, configuring builds, running tests, or optimizing production builds. Don't use for Nx workspace commands, custom Webpack configurations, or non-Angular CLI build systems like Vite standalone or esbuild direct usage.

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

Design and deploy copilot-style assistants on Azure with secure model access, tool integration, and observability. Use this skill when users ask to build assistants, agents, or copilot workflows in Azure. Covers orchestration, retrieval, safety guardrails, and production deployment.

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

Build production-ready LLM applications, advanced RAG systems, and intelligent agents. Implements vector search, multimodal AI, agent orchestration, and enterprise AI integrations.

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

Compare brands and products across social media — share of voice, sentiment, positioning, and audience overlap using Xpoz. Use when asked to "compare brands", "competitive analysis", "share of voice", "brand vs brand", or "competitive intelligence".

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

Run a one-shot buying-intent lead scan across Reddit, Twitter/X, Instagram, and TikTok using Xpoz. Finds fresh posts from people actively looking for what a product does or frustrated with its competitors, classifies and prioritizes them, and reports where to engage and who to reach. Use when asked to "find leads", "who is asking for a tool like mine", "find people complaining about [COMPETITOR]", "buying-intent scan", or "social selling opportunities".

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

Search and analyze Reddit discussions for market research, product feedback, and community insights using Xpoz. Use when asked to "search Reddit", "what does Reddit think about X", "Reddit feedback on X", "subreddit analysis", or "Reddit market research".

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

Auto-activate for polyfactory, ModelFactory, DataclassFactory, MsgspecFactory, AttrsFactory, Use, register_fixture, pytest plugin, __random_seed__, or coverage(). Not for production seeding.

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

复杂探索资产化 / Complex Exploration：当用户面对复杂、不确定、多轮迭代的产品策略、Roadmap、商业化定价、竞品定位、复杂 PRD 前置探索、项目复盘或方法论沉淀任务时使用。它先判断任务类型，暴露隐含假设，重构真正问题，规划探索路径和中间产物，并在结束后沉淀认知、结构、方法论、工具和影响力资产。不用于简单润色、翻译、摘要、明确执行任务；问题只需早期认知校准时优先用 ai-collaboration-calibration，已有方案要压力测试时用 grill-me，系统专题研究用 research-topic-compiler。

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

Use when / 当用户进入一个新项目或跨仓库工作区，需要扫描产品、用户、业务工作流、技术架构、仓库边界、领域语言、阅读入口和历史踩坑，并生成或持续维护全局 PROJECT_CONTEXT.md。适合用户说“先完整看下项目并沉淀上下文”“给这个项目建上下文文档”“把这次踩坑更新到项目上下文”。不用于单个 PRD 起草、纯目录治理或一次性代码实现。

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

StyleWork 需求排期共创 / 需求优先级讨论：当用户给出云效导出、钉钉 Sheet、Excel、截图或一批需求标题，希望先汇总这一批在解决什么，再识别重复、依赖、前置能力和模糊项，并结合领导重点、客户承诺、阶段方向、技术难度与容量讨论建议迭代和优先级时使用。适用于信息不完整但仍需要临时排期建议的场景。只读分析，不用于导出到钉钉、自动修改云效/钉钉、替用户作最终排期决定或承诺交期。

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

PRD 评审 / 需求评审：当用户已有 PRD 初稿、handoff、需求文档或产品方案，需要从 PM、研发、测试视角找缺口、 冲突、不可实现点和不可测试点时使用。可用中文唤起：“帮我审 PRD”“从研发和测试视角挑问题” “这个需求文档能不能交付开发”“帮我给 PRD 出修改草案”“检查 PRD 图示是否缺失或不可编辑”。 不用于凭空生成 PRD 初稿、直接写代码，或对 PRD 背后的成熟方案做一问一答压力测试；方案压测用 grill-me。

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

Agent trace 诊断器：当用户提供 trace、日志 JSON、agent 执行记录、工具调用序列，或说“看下这个日志/trace，定位根因”“只说明问题不要改文件”时使用；用中文输出核心根因、可视化执行流程图、trace 证据链、可能文件/行和修复建议，默认只读。不用于没有日志证据的新功能设计、普通代码解释或直接修复代码。

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

方案拷问 / 压力测试：当用户有一个产品方案、架构设计、计划或决策，想被连续追问、反方挑战、 压测取舍和失败模式时使用。可用中文唤起：“拷问我的方案”“压力测试这个设计”“帮我问 hard questions” “这个方案哪里会翻车”“grill me”。目标是一问一答把决策树走清楚，不是直接替用户写最终方案。 跨 Skill 运行时只输出 Challenge/Critic Handoff，并把一个 gap 返回最小责任节点；不重写完整方案。 如果用户还不知道真正问题是什么，先用 ai-collaboration-calibration；如果用户要标准 PRD 交付准备度评审， 用 prd-review。

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