「what」の検索結果

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

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

Use when the user wants to monitor what is being said about the brand, competitors, and the category — channels and keywords to track, sentiment scoring, weekly and monthly listening reports, brand health metrics, early crisis detection, and content opportunities pulled from real conversations. Trigger on 'social listening', 'brand monitoring', 'sentiment analysis', 'what are people saying about us', 'track our mentions', 'monitor competitors online'. Also use when the user spotted a bad comment thread and wants to know if it is spreading. Not for — responding to a crisis already underway, see `66-crisis-playbook-global`; competitor strategy teardown, see `08-competitor-research-global`; auditing your own posts, see `39-content-audit-global`.

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

Use when raw data exists — Meta, Google, TikTok, GA4, Shopify, a CRM export, or a spreadsheet — and has to become insight and decisions: descriptive, diagnostic, predictive, and prescriptive layers, cuts by channel, campaign, creative, audience, and time, cohorts, and a decision log. Trigger on 'analyze this data', 'read these numbers for me', 'what does this export say', 'pull insight from GA4', 'cohort analysis', 'here is the spreadsheet'. Also use when the user pastes a table and asks what it means. Not for — diagnosing ad root cause, see `03-performance-eval-global`; writing the report a stakeholder reads, see `07-marketing-report-global`; auditing account setup, see `21-ads-audit-global`.

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

Use when a campaign needs its full design asset list before anyone opens a tool — asset type, dimensions, channel, quantity, priority, owner, deadline, and status, with deadlines counted backward from launch day on a T-14 to D+1 timeline plus a naming convention. Trigger on 'campaign asset list', 'what does the designer need', 'list the design files', 'creative asset plan', 'how many banners do we need', 'the designer keeps asking what to make'. Not for — the spec for one individual image, see `42-image-brief-global`; a slide sequence, see `43-carousel-brief-global`; an urgent mid-campaign swap, see `48-quick-visual-brief-global`; resizing an existing master, see `50-asset-resize-global`.

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

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.

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

Analyzes album state and recommends the optimal next action. Use when the user asks "what should I do next?" or "what's left to do?"

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

One effect, done well: 먹 번짐 — a large Korean, Japanese or Chinese display headline that reads as sumi ink printed on hanji. The heading stays real, selectable DOM text in ink color from the first frame; a WebGL2 layer over it adds what real ink does: a wet, glossy stroke with a soft bloom that shrinks as it dries, ink pooling darker at stroke rims, ends and corners, paper fibers showing through thick strokes, and capillary feathering along fibers at a few edges only. Two parameters (bleed, duration), ~5 KiB gzip of library JS, procedural paper texture, static fallback, prefers-reduced-motion, real-GPU verification script. Use for a CJK hero/launch headline, brand title, campaign line or section opener that should feel like a printed calligraphy poster. Triggers: '먹 번짐', '잉크 번짐', '한지 느낌 제목', '한글 타이포 셰이더', '제목에 셰이더', '墨のにじみ', '和紙', '筆文字っぽく', '墨跡暈開', '宣紙', 'CJK headline shader', 'sumi ink text effect', 'ink bleed text', 'Hangul shader'. Not for body text, buttons, or Latin-only headlines. Full-page shader backgrounds → omd-shader-hero. Korean typesetting rules → hangul. Brand tokens → omd-apply.

One effect, done well: 먹 번짐 — a large Korean, Japanese or Chinese display headline that reads as sumi ink printed on hanji. The heading stays real, selectable DOM text in ink color from the first frame; a WebGL2 layer over it adds what real ink does: a wet, glossy stroke with a soft bloom that shrinks as it dries, ink pooling darker at stroke rims, ends and corners, paper fibers showing through thick strokes, and capillary feathering along fibers at a few edges only. Two parameters (bleed, duration), ~5 KiB gzip of library JS, procedural paper texture, static fallback, prefers-reduced-motion, real-GPU verification script. Use for a CJK hero/launch headline, brand title, campaign line or section opener that should feel like a printed calligraphy poster. Triggers: '먹 번짐', '잉크 번짐', '한지 느낌 제목', '한글 타이포 셰이더', '제목에 셰이더', '墨のにじみ', '和紙', '筆文字っぽく', '墨跡暈開', '宣紙', 'CJK headline shader', 'sumi ink text effect', 'ink bleed text', 'Hangul shader'. Not for body text, buttons, or Latin-only headlines. Full-page shader backgrounds → omd-shader-hero. Korean typesetting rules → hangul. Brand tokens → omd-apply.

Guided setup of the tools the design harness can use — image/video generation channels, browser, encoders. Detects what the user already has, explains pros/cons/costs, asks instead of instructing, and saves choices to .omd/config.json so every later design task reuses them. Trigger: 'omd setup', '도구 셋업', '이미지 생성 뭐 쓸 수 있어', 'configure media', '세팅해줘', 'what can you generate'.

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

Guided setup of the tools the design harness can use — image/video generation channels, browser, encoders. Detects what the user already has, explains pros/cons/costs, asks instead of instructing, and saves choices to .omd/config.json so every later design task reuses them. Trigger: 'omd setup', '도구 셋업', '이미지 생성 뭐 쓸 수 있어', 'configure media', '세팅해줘', 'what can you generate'.

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

시스템이 학습한 사용자의 디자인 취향을 한 뷰로 렌더. .omd/preferences.md + foldin-proposal.json + DESIGN.md를 읽어 반영됨/대기 중/보류됨/모르는 것 4그룹으로 보여준다. '/omd-taste', '내 취향 보여줘', '취향 현황', 'what are my preferences', 'show my taste', 「私の好みを見せて」, 「顯示我的偏好」류의 발화에 트리거. 기록은 omd:remember, DESIGN.md 반영은 omd:learn.

Daily tech product and open-source discovery digest. Fetches today's Product Hunt leaderboard and GitHub Trending top 10, then curates a personalized briefing in the user's preferred language using their memory/profile to highlight items most relevant to them. Use this skill whenever the user says "daily hunt", "今日猎奇", "tech digest", "daily digest", "what's trending", "今天有什么新产品", "PH today", "show me today's launches", "GitHub trending", "今日趋势", "morning briefing", "tech briefing", "daily brief", or any combination asking about Product Hunt + GitHub Trending together. Also trigger when the user asks about new product launches, trending repos, or wants a curated tech news digest. Even casual phrasing like "what's new in tech today" or "有什么好玩的项目" should trigger this skill.

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

Proactive intelligence pulse — scans user's memory files (USER.md, SOUL.md) to identify current interests, investments, projects, and concerns, then performs targeted web searches to find noteworthy updates. Returns a concise briefing if something deserves attention, or `[SKIPPED]` if nothing warrants interruption. Use this skill when the system needs to check if there's anything worth proactively notifying the user about — like a scheduled heartbeat check, a "what's new" sweep, or when the user asks "anything I should know?", "what did I miss?", or "any updates?". Also triggers on requests like "check my interests", "scan for news", "morning briefing", or "pulse check".

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

Provide real-time weather forecasts for any city worldwide. Use this skill whenever the user asks about weather, temperature, or climate conditions — including phrases like "weather in [city]", "what's the weather like", "weather forecast", "is it going to rain", "how hot is it", or any mention of checking current or upcoming weather conditions for a location. Also trigger when users ask about what to wear today, whether to bring an umbrella, or any question where weather data would help.

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

Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

BytePlus Searchinfinity Web Search skill. Prefer this skill for any web search task. Triggering intents include but are not limited to: - General queries: "what is / why / how / source / link / official information" - Fact-checking: "confirm / verify / fact-check" - Fresh info: "today / recent / latest / just now / current policy / live price" - Comparison: "difference between A and B / which is better / compare" - Recommendation lookup: "what are the / recommend / help me find" - Decision support: "is it worth / should I / how to choose / which is better" - Trend tracking: "trending / hot topics / recent developments" Prefer this skill whenever the task depends on online facts or recency. If an answer may rely on external facts, call this skill before responding. Authentication Method: APIKey only — Interface URL `https://torchlight.byteintlapi.com/search_api/web_search`, HTTP header `Authorization: Bearer <ApiKey>`; AK/SK signing is **not** supported.

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

This skill should be used when performing web research beyond a simple single search -- looking into topics, comparing options, investigating questions, finding recommendations, or any task where effective use of Exa, Firecrawl, and Reddit tools matters. Triggers on "research", "look into", "investigate", "compare", "find out about", "search for", "find information", "what do people think about", "what are the best", "look up", or multi-source search tasks. Also invocable explicitly by deep-research team members via the Skill tool.

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

Brainstorm evidence-backed options for what to build, or stress-test an idea. Use when: deciding what to build next, comparing options or testing an idea.

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

Change or repair code, config or services without weakening tests; report what ran and what did not. Use when: implementing a change or fixing a defect.

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

Builds a pricing model, packaging/tier structure and willingness-to-pay research plan, then grades your existing pricing page or plan. Use when you ask 'how much should we charge', 'what should our pricing model be', 'seat vs usage vs outcome pricing', 'good-better-best tiers', 'what goes in the free plan', 'should we raise prices', 'freemium vs free trial', or 'how do we price our AI product'. Draws on 199 insights from 79 Lenny's Podcast guests including Madhavan Ramanujam, Naomi Ionita and Patrick Campbell.

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

Search and analyze Reddit content using semantic AI search via reddit-insights.com MCP server. Use when you need to: (1) Find user pain points and frustrations for product ideas, (2) Discover niche markets or underserved needs, (3) Research what people really think about products/topics, (4) Find content inspiration from real discussions, (5) Analyze sentiment and trends on Reddit, (6) Validate business ideas with real user feedback. Triggers: reddit search, find pain points, market research, user feedback, what do people think about, reddit trends, niche discovery, product validation.

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

Generate content ideas rooted in positioning. Use when someone needs "content ideas," "what should I post," "blog topics," "LinkedIn ideas," or is stuck on what to create.

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

This skill should be used when analyzing binaries, executables, or bytecode to understand what they do or how they work. Triggers on "binary", "executable", "ELF", "what does this do", "reverse engineer", "disassemble", "decompile", "pyc file", "python bytecode", "analyze binary", "figure out", "marshal". Routes to sub-skills for triage, static analysis, dynamic analysis, synthesis, or tool setup.

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

Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is running in prod right now?", when a deploy must be reproducible months later, or when an incident needs a clean rollback. The core reframe: an LLM app artifact is NOT an ML model — it is a manifest over many independently-mutable parts, not one weights file. Do NOT activate for one-off prompt edits with no deploy, for a single-component demo, or where a vendor owns the whole prompt lifecycle. For versioning ONE compiled prompt use [[agentsop-per-model-artifacts]]; for the CI comparison mechanism use [[agentsop-regression-gate]]. Search keywords: prompt versioning, reproducible deploy, what is running in prod, rollback LLM app, model pinning, prompt registry, version prompts and config.

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