「rules」の検索結果

Always-on spam and deliverability guardrails for cold email copy. Apply these rules whenever writing, reviewing, or QA-ing subject lines, openers, follow-ups, CTAs, or any cold outreach copy. Trigger on phrases like "check this for spam", "spam word check", "deliverability review", "QA this copy", "flag banned words", "check subject line", "is this safe to send", "scan for spam triggers", or any time cold email copy is being generated or reviewed. Also trigger automatically as a background rule whenever the campaign-copywriting or cold-email-copywriting skill is active -- these guardrails apply to EVERY piece of outbound copy generated, even if the user does not explicitly ask for a check.

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

Coupon and promotion planning — coupon types, stacking rules, deal timing, redemption optimization

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

Amazon repricing strategy and Buy Box optimization. Competitive pricing analysis, dynamic pricing rules, margin protection strategies, repricing tool selection, and automated pricing workflows. Use when the user asks about Amazon repricing, pricing strategy, Buy Box optimization, competitive pricing, or dynamic pricing.

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

Designs products around price using the 9 rules from Ramanujam and Tacke - WTP conversations, needs-based segmentation, Good/Better/Best configuration, monetization models, behavioral pricing, and price integrity. Use when designing new products, validating pricing for SaaS/B2B/B2C launches, choosing between subscription/usage/freemium models, fixing post-launch sales below plan, diagnosing failed launches as Feature Shock/Minivation/Hidden Gem/Undead, or when product teams say 'let's price it later'. Not for pure commodities or cost-plus regulated environments.

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

Define a brand's verbal identity — tone, voice, writing style, vocabulary, and messaging rules. Use when the user says "brand voice", "tone of voice", "how should we write", "writing guidelines", "copy style guide", "brand language", "verbal identity", "how should the brand sound", "tone guide", "our copy doesn't sound right", "copywriter guidelines", "voice and tone", or when onboarding a copywriter or content team. Also use when the user has a brand strategy and wants to define how the brand communicates.

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

AGENTS.md / CLAUDE.md 最佳实践顾问。用于用户询问 agents markdown、AGENTS.md、CLAUDE.md、Claude Code memory、AI coding agent 指令文件的格式、结构、最佳实践；也用于审查、诊断、重写、优化或从零创建 AGENTS.md、CLAUDE.md、CLAUDE.local.md、.claude/rules 等 agent 指令文件。不适用于通用 README 写作，除非目标是给 AI coding agent 提供项目上下文。

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

Manage capa CLI configuration — `capabilities.yaml` / `capabilities.json`, skills, MCP servers, tools, hooks, sub-agents, rules, plugins, AGENTS.md / CLAUDE.md, security options, tool exposure modes, `capa wrap` shadow workspaces, `--passthrough` native writes, registries (including Claude marketplaces), activity traces, and the local Web UI. Use whenever the user edits the capabilities file, runs any `capa` command (init, install, add, wrap, clean, sh, start/stop/restart/status, auth, upgrade, cache, registry), wires up an MCP server, adds a skill from GitHub / GitLab / a registry / a remote URL / a local path, configures secrets via `${VarName}` placeholders, installs lifecycle hooks, defines sub-agents, or troubleshoots a failed install. Use even when the user only names a fragment ("add a skill", "wire up brave search", "wrap cursor", "block this phrase in skills") without saying "capa" — if a `capabilities.yaml` or `capabilities.json` lives at the project root, this is almost certainly the right skill. If the project does NOT yet have a capabilities file, point at the `bootstrap` skill instead.

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

Status match and status challenge rules for airlines and hotels. Covers free direct matches, paid concierge via statusmatch.com with fees, card-granted status, and critical lifetime/once-per-N-years restrictions that make wasted matches expensive.

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

Per-program stopover rules for award redemptions. Which programs allow free stopovers, how many, how long, and which don't. Covers Icelandair, Aeroplan, Alaska, Flying Blue, Singapore, Cathay, JAL, and the negative space (BA, AA, Delta).

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

Per-program rules for placing award flights on hold before transferring points. Covers programs with holds (AA, Lufthansa, Flying Blue, Cathay, Turkish, Virgin Atlantic, ANA, Emirates, EVA Air) and those without. Includes transfer-speed reference.

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

Cents-per-point (cpp) valuations across major loyalty programs from four publications. Floor/ceiling rules for deciding if a redemption is good or exceptional.

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

Convert YouTube videos to SEO-optimized blog posts. Extract video title, description, and content, then generate a search-engine-friendly blog post with embedded video, cover images, optimized metadata, structured Markdown sections, clean resource blocks, and canonical 5-8 keywords. Auto-generates English filenames and saves to the configured Hexo blog posts directory. Includes tag management rules to maintain a clean, consistent tag taxonomy.

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

Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate concession-threshold guard that blocks acceptance on unresolved critical findings. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".

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

Run the four paper-quality autoraters from PaperOrchestra (arXiv:2604.05018, App. F.3) — Citation F1 (P0/P1 partition + Precision/Recall/F1), Literature Review Quality (6-axis 0-100 with anti-inflation rules), SxS Overall Paper Quality (side-by-side), and SxS Literature Review Quality (side-by-side). TRIGGER when the user asks to "score this paper draft", "evaluate against the benchmark", "compare two papers", or "run the autoraters".

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

Use for the owner's personal creator-content thumbnails and covers for short video, Bilibili, Douyin, WeChat, or similar platforms from a title, summary, established real portrait, kangaroo IP, product Logo, screenshot, or app reference. It enforces the owner's visual signature, runs a four-concept selection stage, then five responsive platform ratios. Do not use for generic clients, book or album covers, slide title pages, generic posters or social cards, article body illustrations, document headers, website hero art, or unrelated image edits unless the user explicitly invokes cover-skill and accepts the personal-signature rules.

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

Use when setting up providers, combining requests, managing state disposal, passing arguments, performing side effects, or testing providers (Riverpod).

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

Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.

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

Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.

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

Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.

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

Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.

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

Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.

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

Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.

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

Use when setting up providers, consuming state, optimizing rebuilds, using ProxyProvider, or migrating from deprecated providers (Provider package).

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

Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.

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