「should」の検索結果

Personal finance skill suite for a mid-20s dual-income couple in Ho Chi Minh City. Covers budgeting, emergency fund building, investments, insurance, tax optimization, goal planning, and couple dynamics — all calibrated to Vietnam's financial ecosystem. Use when the user asks about budgeting, saving, investing, insurance, taxes, or financial goal planning — trigger phrases include "review our budget", "how should we invest", "do we have enough insurance", and "plan for a home purchase". Use even if the user only mentions one financial topic without asking for a full review.

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

This skill should be used when the user asks to appeal a MetLife pet insurance claim, dispute a denial, challenge an underpayment, draft an appeal letter, review an EOB for appeal grounds, or fight a pet insurance claim decision.

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

This skill should be used when the user asks about "production management", "film budget", "scheduling", "crew management", "location logistics", "risk assessment", "act as a production manager", "production manager mode", "line producing", "production budget", "crew roles", "film insurance", "production timeline", "location permit", "production paperwork", or needs expertise in film budgets, production scheduling, crew management, location logistics, and risk mitigation for film projects. Part of the AlterLab FC Skills collection (Cinema & Digital Media department).

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

Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".

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

Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".

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

Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".

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

Customer segmentation model builder — tiers customers by ARR, health, and expansion potential; defines CS motion per tier; maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", "build a customer segmentation model", or "who gets high-touch vs. digital".

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

A/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".

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

Metrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".

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

Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority. Use when asked to "fix responsive behavior", "define breakpoints", or "how should this reflow on mobile".

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

Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".

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

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

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

Select and pair fonts for a product — brand display, UI body, and monospace. Use when asked to "pick fonts for our product", "pair a display and body font", or "what typeface should we use".

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

SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".

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

Design meeting and communication cadence — what meetings to run, how often, who attends, and what decisions they make. Use when asked to "design our meeting structure", "what meetings should we have", "reduce meeting load", or "build our operating rhythm".

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

Link prospecting — pick the site's most linkable asset, find pages that plausibly link to it (resource pages, competitor linkers, unlinked mentions, broken links), verify real contact paths, and draft personalized outreach. Never invents contacts. Use when asked to "find backlink opportunities", "who should link to us", "build links to this page", "link prospecting", or "draft outreach for backlinks".

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

Design a color palette with semantic tokens for a brand or product. Use when asked to "design a color palette", "what colors should we use", or "define semantic color tokens".

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

Draft or review legal ops documents — NDA, MSA, SaaS agreement review checklist, vendor contract terms. Use when asked to "review this contract", "draft an NDA", "what should I look for in this agreement", or "build our contract review process".

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

Content brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal link targets, word count, CTA, and competitive gap analysis. Use when asked to "write a content brief", "brief this blog post", "plan this article", or "what should we cover for [keyword]".

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

Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".

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

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".

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

Design a model training pipeline — algorithm selection, cross-validation, and serialization. Use when asked to "train a model for this", "design a training pipeline", or "which algorithm should we use".

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

Use when asked to create a brand identity, define visual design direction, generate a color palette or type system, build a style guide, or establish the look and feel for a product. Examples: "create a brand for X", "define the visual identity", "what colors should we use", "build a style guide", "design system foundations".

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

Translate a design brief — structured I-Lang or plain English — into a concrete DESIGN.md and optional HTML token preview. Resolves 8 dimensions (palette, accent, typography, display font, layout, mood, density, constraints) to specific CSS tokens. Use when asked to "create a design brief", "write a DESIGN.md", "define the design system", "design brief for X", "what tokens should we use", or "I-Lang brief".

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