「how to use」の検索結果

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

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

How App Store ratings actually behave — per-storefront isolation (your US stars show nowhere else), the never-reset rule, phased release + manual release as rating protection, and where prompting/replying fit. Use when planning ratings strategy for new markets, considering a ratings reset, setting release options, or diagnosing "why is my rating missing in country X."

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

Monetization strategy for iOS/macOS apps. Covers readiness assessment, pricing model selection, tier structuring, free trial strategy, and implementation guidance. Use when deciding what to charge, how to price, or planning monetization end-to-end.

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

Build a product-specific Amazon FBA prep, labeling, packing, and shipment-readiness plan. Use when a seller asks how to prepare units for FBA, choose barcode and labeling steps, plan poly-bagging, bubble wrap, sets, case packs, cartons, dangerous-goods review, supplier or prep-center instructions, or prevent receiving delays. Do not use as a substitute for current Seller Central requirements.

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

Use when the user asks about visual styles, aesthetics, color grades, film looks, or how to set the tone and atmosphere of a Higgsfield generation.

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

Use when the user asks about camera movements, shot types, or how to describe camera behavior in a Higgsfield prompt. Contains all named camera controls with descriptions, best use cases, and example prompt phrases.

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

Writes the character-performance layer of a video prompt as behavior under pressure, not displayed emotion — objective, obstacle, tactics, beats, subtext, listening, body/status/proxemics, and mandatory eye life. Produces a reusable 150–220-word acting master profile per character plus a per-scene rewrite of it, and a locked voice prompt. Use whenever a prompt needs acting, performance, or emotion direction; whenever characters read wooden, dead-eyed, or 'AI'; whenever a character must stay themselves across many shots; or when the user asks for character behavior, mannerisms, tics, a gait, or how someone reacts. Pairs with higgsfield-facs (muscle-level AU codes) and higgsfield-seedance (the prompt the paragraph goes into).

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

Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.

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

Use when the user asks whether GSD is up to date or wants to upgrade it. Checks the local and global install against npm, shows the changelog, warns before a clean install, then clears the cache.

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

Use when the user wants to switch the GSD model profile for agents: quality, balanced, budget, or inherit. Runs the gsd-tools config-set-model-profile command and shows its output verbatim.

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

Use when the user supplies a music track, a video to pull audio from, or a mood brief, and wants a beat-synced video: lyric video, slideshow, or kinetic promo. The music drives pacing; zero assets are required.

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

Use when the user asks what GSD commands exist or how to use GSD. Outputs the complete GSD command reference verbatim, with no project analysis, status, or next-step suggestions.

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

Use when the user asks to create, scaffold, update or package a skill, or asks how skill frontmatter, progressive disclosure or bundled resources should be structured. Walks through init_skill.py, writing SKILL.md and package_skill.py.

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

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

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

Weekdays, file work only, no browser at all. Takes the single highest ranked open fault on the fleet and turns it into something the member can act on in a minute: the fault in one sentence, the first record that shows it, what changed around that date, three ranked causes each with its evidence line, what the failure has cost, and one paste ready correction line with the exact path it belongs in. It reads other Employees strictly read only, writes nothing outside its own folder, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Use when a PAID MEDIA plan is needed — work backward from revenue to max CPA and required budget, split spend across channels, funnel stages, and campaign types, build a ramp-up timeline, set KPI targets per channel, and prepare a contingency plan. Trigger on 'media plan', 'paid media budget', 'how much should I spend on ads', 'channel mix for the campaign', 'plan the ad budget', 'we have 10k a month and no plan'. Also use when a budget number exists and nobody has decided where it goes. Not for — the pure revenue-to-budget math, see `10-reverse-kpi-global`; the whole marketing budget including non-paid, see `61-budget-planning-global`; the next period plan built from results, see `57-next-ads-plan-global`.

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

Use when a finished DESIGN needs scoring and feedback — brand consistency, hierarchy plus readability plus accessibility, conversion elements, and platform fit, 10 points each, with per-issue feedback in issue, why, and how-to-fix form and a verdict of approve, minor fix, or redo. Trigger on 'design review', 'review this design', 'score this creative', 'is this design good', 'brand check on this banner', 'can we ship this or not'. Also use when the user just sends an image and asks for thoughts. Not for — reviewing copy and briefs, see `62-marketing-review-global`; writing the brief before production, see `42-image-brief-global`; the brand rules being checked against, see `46-brand-guideline-global`.

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

Use when an ad account HIERARCHY needs designing or cleaning up — campaign, ad set, and ad structure by objective, a naming convention that keeps data readable, CBO versus ABO by stage, how many ad sets and creatives to run, and the minimum daily budget an ad set needs to exit learning. Trigger on 'account structure', 'campaign structure', 'naming convention', 'how many ad sets should I run', 'CBO or ABO', 'our account is a mess of duplicated campaigns'. Not for — scoring an existing account against 84 checkpoints, see `21-ads-audit-global`; pixel and conversion setup, see `53-tracking-setup-global`; budget across channels, see `54-media-plan-global`; scaling a winner, see `55-scaling-ads-global`.

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

Use when a team wants to design, audit, or operate an AI Marketing OS — a Brand Hub source of truth, role-based AI projects for leader, content, design, performance, and knowledge, skill chains, ChatGPT plus Claude plus NotebookLM workflows, MCP connectors, a Notion or Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'set up our marketing AI system', 'Brand Hub', 'AI workflow for the team', 'MCP for ads data', 'how do I make AI actually useful for marketing'. Not for — one campaign brief, see `02-campaign-brief-global`; the weekly report, see `07-marketing-report-global`; the brand visual rules, see `46-brand-guideline-global`; the product context file, see `product-marketing-context-global`.

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

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

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

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

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

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

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

Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Use when adding, renaming, splitting, or reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase or ExternalApi QuerySpec/MutationSpec tests; or running make test / feature tests.

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

Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…

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