「three」の検索結果

Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.

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

Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay. Optional Replicate hero image with --visual.

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

Three-mode idea engine - generate collides the week's zeitgeist with what you can ship into scored wedges; validate viability-screens the idea backlog; memo writes evidence-backed startup memos.

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

Use ONLY when calling the `browser_execute` tool or driving a real browser via the Chrome DevTools Protocol. Required reading before the first `browser_execute` call in a session. Covers the three connection methods (local Chrome with remote debugging, isolated debug-port profile, Browser Use cloud), the in-process `session` / `console` snippet model, attaching to a page target, common CDP commands, the per-project `.bcode/agent-workspace/` for reusable scripts, and screenshot auto-attachment.

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

Index and shared harness for the 19 signal playbooks. Each playbook turns one buying signal (new in role, raised a round, hiring surge, pricing page, tech on website, ...) into one copy-ready sentence you can drop into a cold email. Every playbook ships three ways to run it: as a Claude skill, as a Clay table built through a browser harness, and as a Clay workflow built from the clay CLI. Use when someone says "personalize this list", "what signal should I use", "build the Clay column for X", or names any of the 19 signals.

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

Amazon sales volume estimator for sellers and product researchers. Estimate monthly sales and revenue from BSR (Best Seller Rank), ASIN, or keyword. Three modes: (A) BSR Calculator — input BSR + marketplace + price + category to get instant sales estimate, (B) ASIN Lookup — input ASIN to auto-fetch data and estimate sales, (C) Keyword Market Analysis — input keyword to analyze total market size and competition. Works on 12 Amazon marketplaces. No API key required. Use when: (1) estimating how many units a product sells per month, (2) sizing a market or niche opportunity, (3) analyzing competitor sales performance, (4) comparing sales across price points, (5) identifying top sellers vs long-tail distribution.

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

Design the three states every data UI forgets. Use for any component that fetches or lists data.

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

Split the Plan/Act/Verify loop across three model tiers — frontier planner, cheap executor, frontier judge — via env vars read by run.sh.

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

Deep need-clarification skill. Use only when the user explicitly invokes $task-clarifier. Once activated, keep asking until all three goals are met: the user fully understands their own needs, the AI fully understands the user's needs, and the user confirms the AI's understanding is correct. Do not intervene in task execution unless explicitly invoked.

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

Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant. Use when reframing competitive strategy, escaping commoditization, designing a new category, or applying Strategy Canvas, ERRC, Six Paths, Three Tiers of Noncustomers, Buyer Utility Map, or Strategic Sequence. Includes selection-bias caveats and inline decline notes for iconic cases that later collapsed.

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

Use when the user mentions GPT Image 2.0 or GPT Image 2.5, gpt-image-2, gpt-image-2.5, gpt_image_2_5, GPT-Image-2 prompts, the Flare / Sunburst variants, a transparent-background image, or wants to generate an image with GPT Image 2.0 or 2.5. Covers when to prefer GPT Image 2.5 over 2.0 (transparent background, xhigh/max quality, extra aspect ratios — from platform and OpenAI facts), the CLI-vs-MCP disagreement on gpt_image_2, the three-format prompt taxonomy (Format A structured JSON for UI mockups and layout-dense images; Format B dense cinematic prose for single-subject scenes; Format C auto-derive meta-prompt for theme-only concepts), per-format craft patterns, output conventions, the 6-item pre-delivery checklist, and cross-surface workflow context (companion static-ads-workflow.md for ad recreation; higgsfield-marketing-studio cross-surface-workflow.md §3 for ms_image / DTC Ads Higgsfield-native alternative).

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

Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with ranked charts, a three-month trend, a multi-year overlay and a data table. Use when asked to benchmark a product against competitors, size up a market, answer "how much traffic does X get compared to Y", build a competitive landscape, or produce a traffic/authority comparison deck or page.

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

BDD requirements discovery methodology - Example Mapping, Three Amigos, conversational patterns, Given-When-Then translation, and collaborative specification

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

Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the full journey, a validate-only pass ("is my idea worth building", "reality-check this idea"), and a plan-only path for someone arriving with validation done ("I already validated my idea", "I have the research, just plan my MVP", "skip the research"). ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.

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

Monthly, browser conditional. On its first run it discovers the member's properties from the sites they name, writes the three strategy files, creates every ledger and folder the kit reads, files the opening cards, and registers the eight scheduled jobs. Every month after that it re-reads the evidence rather than its own previous conclusions, rebuilds the topic map and the internal link map, corrects any property fact it can prove wrong, and records every change with the path of the evidence that forced it. It holds publishing and spending unless you released the channel, and it never touches a credential.

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

Weekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.

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

Monthly, on the last weekday, file work only, no browser at all. Folds the decision ledger, scores this Employee's own judgement against the metric files that measured it rather than against its own predictions, appends one outcome line per closed decision, retires a move proposed three times and never accepted, and rewrites the priorities where the evidence disagrees with them. It refuses to publish a calibration figure on too few closed decisions, changes nothing outside its own folder, proposes nothing to anybody, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

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 PERSONAL brand needs AI avatar video at scale — three tool tiers, four workflows for single avatar, translation, batch, and hybrid, reference image intake, face, style, logo, and palette replacement, voice clone pairing, anti-detection, and a QA score, with disclosure-law variants for US FTC, EU AI Act, SEA, and LATAM, covering HeyGen and Synthesia. Trigger on 'AI avatar', 'HeyGen video', 'Synthesia', 'talking head AI video', 'translate my videos with AI', 'I cannot be on camera every day'. Not for — the words the avatar says, see `04-script-video-global`; audio-only voice clone and podcast, see `25-voice-clone-podcast-global`; a company product video edit, see `44-video-editor-brief-global`.

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

Use when a PERSONAL brand needs to make money — three funnel versions for founder, coach, and creator, an offer ladder from free to low to mid to high ticket, pricing psychology, inbound versus outbound outreach, and brand deal and sponsorship negotiation, with tax and legal variants for US LLC, EU per country, SEA Pte Ltd, and LATAM MEI. Trigger on 'monetize my personal brand', 'offer ladder', 'launch my course', 'coaching packages', 'sponsorship rates', 'I have an audience and no income'. Not for — a company product offer, see `31-offer-design-global` and `17-pricing-strategy-global`; the strategy that comes first, see `23-personal-brand-strategy-global`; running the community, see `28-community-building-global`.

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

Use when a PERSONAL brand — founder, coach, or creator — needs a 12-month strategy: niche selection with Ikigai and a 3x3 matrix, positioning statement, a three-chapter story arc, four content pillars with 28 topics, a five-stage authority ladder, and a Q1 to Q4 growth plan. Trigger on 'personal brand strategy', 'founder brand plan', 'coach positioning', 'creator strategy', 'what niche should I own', 'I post constantly and nothing compounds'. Also use when the user has followers and no direction. Not for — a company brand, see `58-positioning-global` and `00-marketing-plan-global`; the context file this reads first, see `22-personal-brand-context-global`; turning it into revenue, see `27-personal-brand-monetize-global`.

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

Use when a PERSONAL brand needs its OWN community — Skool, Mighty Networks, Discord, Circle, or Slack: a three-layer public, member, and inner-circle blueprint, seven-day onboarding, engagement rituals, a moderation playbook, and activation metrics. Trigger on 'build a community', 'Skool community', 'Mighty Networks setup', 'Discord for my audience', 'paid community', 'my group is dead and nobody posts'. Also use when the user has members and no reason for them to come back. Not for — posting inside communities you do NOT own, see `38-community-seeding-global`; pricing and packaging the membership, see `27-personal-brand-monetize-global`; referral loops, see `18-referral-program-global`.

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

Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline directions. Trigger on 'positioning', 'positioning statement', 'what makes us different', 'USP', 'why should customers choose us over them', 'we sound the same as everyone else'. Also use when the user can list features but not a reason to pick them. Not for — competitor teardown research, see `08-competitor-research-global`; how the brand sounds in writing, see `35-brand-voice-global`; the offer and its value stack, see `31-offer-design-global`; the launch built on it, see `59-go-to-market-global`.

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

Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.

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