3,247 件 ・ 関連度順
概要と使いどころ
Design a reservation and savings plan strategy — commitment level, term, and coverage targets. Use when asked "should we buy reserved instances", "design a savings plan strategy", or "what commitment coverage do we need".
日本語の概要は準備中です。原文の説明を表示しています。
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
日本語の概要は準備中です。原文の説明を表示しています。
Design compensation framework - salary bands, equity philosophy, offer templates, and total comp benchmarking. Use when asked to "design our comp bands", "how much equity should we give", "is our comp competitive", or "write an offer template".
日本語の概要は準備中です。原文の説明を表示しています。
MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement a feature engineering pipeline for a ML problem. Use when asked to "engineer features for this model", "what features should we build", or "design feature transformations".
日本語の概要は準備中です。原文の説明を表示しています。
Design drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".
日本語の概要は準備中です。原文の説明を表示しています。
Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".
日本語の概要は準備中です。原文の説明を表示しています。
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
日本語の概要は準備中です。原文の説明を表示しています。
Design a caching strategy for an application — pattern selection, key design, TTL, and eviction policy. Use when asked to "add caching to this", "design a cache strategy", or "what should we cache".
日本語の概要は準備中です。原文の説明を表示しています。
Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels. Use when asked to "design a deprecation policy", "how should we version the API", or "set a sunset timeline".
日本語の概要は準備中です。原文の説明を表示しています。
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
日本語の概要は準備中です。原文の説明を表示しています。
Design support metrics dashboard -- CSAT, FRT, TTR, ticket deflection rate, volume trends, and agent efficiency. Use when asked to "what metrics should support track", "build our support dashboard", "measure support quality", or "audit our support performance".
日本語の概要は準備中です。原文の説明を表示しています。
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
日本語の概要は準備中です。原文の説明を表示しています。
Design ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".
日本語の概要は準備中です。原文の説明を表示しています。
Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".
日本語の概要は準備中です。原文の説明を表示しています。
Design escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".
日本語の概要は準備中です。原文の説明を表示しています。
How nutrition science becomes dietary guidance, and how industry, agriculture, and politics shape that process. Covers the US Dietary Guidelines cycle, food labeling, WIC and SNAP, commodity subsidies, and the documented history of industry influence on research and recommendations. Use when a question asks why a guideline says what it says, how a recommendation got written, or whether an industry-funded study should be trusted.
日本語の概要は準備中です。原文の説明を表示しています。
Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks "what should I work on", mentions GSD phases, ROADMAP, or .planning/ artifacts. Routes to the correct GSD command for the current project state.
日本語の概要は準備中です。原文の説明を表示しています。
用户在帖子没爆时感到焦虑、怀疑自己是否适合做 X,或连发一批内容后评估整体表现、设定增长目标时使用。核心认知:公共平台传播是长尾分布(3861 帖均值 188/中位数 42),一条没爆是预期的中位数而非失败;目标不是让每条都爆,而是系统性提高进前 10% 的概率。Trigger signals: "我连发20条只2条过百该放弃吗""怎么让每条都爆""发了这么多没水花""一条没爆就怀疑人生""是不是我不适合做X" / "only 2 out of 20 hit 100, should I quit" "how to make every post go viral" "my posts get no engagement"。不适用于:单条内容生产(用 x-short-content-craft)、数据复盘操作(用 x-data-review)、理解推荐算法机制(用 x-foryou-algorithm)。
日本語の概要は準備中です。原文の説明を表示しています。
新号注册或老号解冻后做开业准备时用：装修Profile四要素（头像真人/昵称关键词+身份/简介价值承诺/背景图）→开蓝V(Premium)→养号3天只浏览→再发内容。Trigger："新号第一天""要不要开蓝V""怎么装修主页/头像/昵称/简介""新号怎么养号""day 1 new account""should I get Premium""set up profile""warm up account"。不适用：已运营账号日常发内容/没粉丝(→x-cold-start-playbook)、被限流封号后排查(→x-account-pitfalls)。
日本語の概要は準備中です。原文の説明を表示しています。
用户要起草一条 X 短内容(推文/帖子)、不知道用什么结构或类型时;或问"怎么发一条教人用 XX 的帖""怎么排版推文能让更多人收藏""what structure should I use for a tweet / how to write a tutorial post"时。先按目标指标选四类型之一(故事→涨粉 / 列表→收藏 / 观点→互动 / 教程→忠诚),再用 Hook-Body-CTA 三段骨架起草;资源/工具类可套爆款公式(工具+场景+三步)。不适用于:已有草稿想检查五件套完备性(→x-five-piece-checklist)、想把公告腔改写成帮助式语言(→x-three-translations)、想按读者功能分类预测传播上限(→x-content-archetypes)、纯信息查询(如推文字数上限)。
日本語の概要は準備中です。原文の説明を表示しています。
发帖前自检"这条内容帮读者省了几步路"时使用;用户问"值不值得发/有没有价值/该不该发这条"时激活。不适用于:已决定要发只需检查结构完备性(用 x-five-piece-checklist)、需要分类内容原型(用 x-content-archetypes)、需要改写表达方式(用 x-three-translations)。Trigger 词:"值不值得发""省了几步""内容价值""worth posting""content value""should I post this""save steps"。
日本語の概要は準備中です。原文の説明を表示しています。