「how to」の検索結果

First-run setup. Detects configured API keys, points to the local setup-keys script for secure key entry, and shows sample prompts scaled to available tools.

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

Build, inspect, update, restore, or share Avibe Show Pages for visual explanations, diagrams, reports, or interactive prototypes. Covers the page workspace and its Git history.

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

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.

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

Use when a designer needs hands-on production direction inside a tool — Canva, Figma, or Adobe Express: which template to start from, the operating order, element-by-element mapping, grid and spacing, brand kit colors and fonts, export checklist, and the dos and do-nots. Trigger on 'Canva brief', 'Figma brief', 'production direction', 'how do I build this in Canva', 'layout direction for the designer', 'the junior designer needs step by step'. Not for — the creative concept for a static, see `42-image-brief-global`; the concept for a slide sequence, see `43-carousel-brief-global`; the brand rules being applied, see `46-brand-guideline-global`; adapting one master into every size, see `50-asset-resize-global`.

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

Use when ONE static image needs a full brief for a designer or photographer — visual objective, concept and mood, composition, overlay copy, colors and fonts read from the brand guideline, per-channel dimensions, deliverables, and approval criteria. Trigger on 'image brief', 'banner brief', 'thumbnail brief', 'brief for the designer', 'how should this graphic look', 'the design came back wrong again'. Also use when the user has a post idea and needs to explain the visual. Not for — a multi-slide sequence, see `43-carousel-brief-global`; tool-level production steps in Canva or Figma, see `45-design-tool-brief-global`; generating the image with AI, see `30-design-master-global`; an urgent same-day swap, see `48-quick-visual-brief-global`.

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

Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.

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

Helps a teacher prepare to teach an existing K-12 lesson (math / ELA / science / social studies) — a prep partner that thinks through the lesson's key student task with the teacher and leaves a short teacher-only prep note. Triggers on asks to internalize, prepare for, get ready to teach, or understand a lesson, including implicit ones ("help me get ready for tomorrow's lesson"), and right after another skill built a lesson, which it can follow. Not for building or adapting a lesson, grading, rubrics, assessment feedback, or generating quizzes or student-facing material, and not for single-fact lookups a sentence would answer ("what standard is this?", "how long is this lesson?").

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

Use when a task touches Ecto, even a how-to question: schemas, changesets, validations, queries, preloads, Multi…

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

Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.

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

Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.

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

Route ambiguous or mixed Phoenix/LiveView/Ecto requests before choosing a workflow. Use when user is unsure where to start/how to approach work, asks for the right workflow, or combines intents such as fixing and refactoring. NOT for a clear task.

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

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.

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

Route C# and .NET requests to the exact installed specialist or smallest dotnet/skills marketplace plugin. USE FOR: "which specialist should own this" or "how do I add the skill" requests involving ASP.NET Core endpoints, Blazor, MAUI binding, Windows Forms specialist selection or installation, EF Core queries, test or framework migration, runtime CPU/allocation evidence, file-based C#, editor/compiler defects, a surviving MSBuild `.binlog`, or a plugin missing from `/skills`; also use for C# semantics when no narrower specialist exists. DO NOT USE FOR: requests that already name the exact installed specialist to invoke, or work unrelated to C# or .NET.

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

Turn any source that describes how a kind of task gets done (a SKILL.md, a chat log, a runbook, plain prose) into a runnable Morph trace. Lift it into a DAG, write a contract per step, place inputs, and drive the full run lifecycle to verify it. Use whenever someone wants to make a trace from a source.

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

Reverse-engineer the hook from a viral Instagram Reel or carousel, given a URL or a pasted caption. Identifies which of the 10 canonical 2026 formulas it uses (number-first, contrarian, relatable, confession, listicle, before/after, myth-buster, framework, pattern-interrupt Reel, how-I Reel), explains why it worked, names the primary goal, and returns a blank template mapped to your topic. Use to learn from a post you admire. Not for writing your own (use ig-caption-writer or ig-carousel-planner).

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

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword, topic, or brief, and full-page rewrites. Use when asked to "write a blog post", "create a landing page", "write content about X", "content for keyword X", "draft an article", "blog post about", "landing page for", "service page", "product page copy", "rewrite this page", "how-to guide", or "listicle". NOT for analyzing/auditing existing content (seo-geo-optimizer, content-quality-auditor), title tags or meta descriptions (meta-tags-optimizer), or keyword expansion (keyword-research) — those skills own their triggers.

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

Runs a product quality review on a journey, feature, landing page, onboarding flow, or AI/agent surface and returns a friction log, a scored critical-journey review, and a taste bar your team can calibrate against. Use when someone asks is this good enough to ship, how polished should it be, why do users bounce, what is our quality bar, how do we build taste, or to review a design, prototype, onboarding, or checkout. Draws on 264 insights from 100 Lenny's Podcast guests incl. Katie Dill, Dylan Field and Stewart Butterfield.

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

Diagnoses why your product team ships slowly and produces a velocity plan with a baseline, a bottleneck map, the top 3 interventions and a stop-doing list. Use it when you say 'we're too slow', 'how do we ship faster', 'projects keep slipping', 'too many meetings', 'approvals take forever', 'our releases are scary', 'velocity', 'cycle time', 'we hired more people and nothing got faster' or 'AI made coding fast but we still ship slowly'. Draws on 226 Lenny's Podcast guests including Farhan Thawar, Nicole Forsgren and Melissa Perri.

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

Turns a career question into a decision brief the PM can act on this week - a career plan, a promotion case, a stay-or-leave verdict, a job-search system, or an offer-negotiation script. Use when someone says 'how do I get promoted', 'should I leave my job', 'job search', 'I got laid off', 'negotiate my offer', 'career plan', 'IC or manager', 'next role', 'am I stuck', 'how do I stay relevant with AI' or 'how do I break into PM'. Draws on 188 Lenny's Podcast guests including Phyl Terry, Nikhyl Singhal and Deb Liu.

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

Builds a product strategy and stress-tests your moat, then writes a one-page strategy doc (diagnosis, where to play, how to win, guiding policy, coherent actions, moat verdicts). Use for 'we need a product strategy', 'is our moat real', 'do we have a competitive advantage', 'where should we play', 'defensibility', 'should we expand into X', 'our roadmap has no strategy', or 'write a product vision'. Draws on 909 insights from 236 Lenny's Podcast guests incl. Roger Martin, Richard Rumelt and Hamilton Helmer.

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

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.

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

Diagrams and checkable docs from a codebase. Draws ERDs, C4 context/container/component views, API endpoint catalogues, lifecycle/state machines, sequence diagrams, and service-to-service call maps as a validated JSON spec plus a standalone HTML viewer, with Mermaid export. Imports OpenAPI, GraphQL SDL and Prisma; otherwise reads the code (NestJS, TypeORM, Express) and writes the spec. Use for: database diagram, ERD, data model, table relationships, C4 or architecture diagram, system context, API map, endpoint list, "show me the endpoints", status flow, state machine, allowed transitions, "what happens after X is approved", sequence diagram, request flow, how services call each other, microservice map, Mermaid diagram. Also writes documentation as a fact graph: each statement carries its source and a computed confidence, and a drift check fails CI when the code moves. Use to document a system, write architecture or onboarding docs, or explain how a system works.

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

Use when a user wants to configure and launch a WorkBuddy Bench evaluation run from scratch, or is unsure how to set one up. Walks them interactively through environment setup, model config, .env credentials, job config, and launching the run, then hands off to wbbench-report-skills for metrics and trajectory analysis.

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

How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift. Only runs when explicitly invoked; it does not trigger on its own.

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