6,396 件 ・ 関連度順
概要と使いどころ
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across PRD/spec/API/data/security/performance/release/SRE, or asks to turn an idea or repo into a production-ready engineering plan.
日本語の概要は準備中です。原文の説明を表示しています。
Agile product management, Scrum practices, and team collaboration for iterative product development.
日本語の概要は準備中です。原文の説明を表示しています。
Create comprehensive marketing content for themes, plugins, and web products. Generates organized folder structure with product descriptions, feature highlights, social media posts, email campaigns, video scripts, sales materials, and brand assets. Use when creating promotional content, announcements, or sales copy.
日本語の概要は準備中です。原文の説明を表示しています。
Plan product launches and go-to-market strategy. Use when launching products, entering new markets, or planning marketing campaigns. Covers positioning, channels, messaging, and launch execution.
日本語の概要は準備中です。原文の説明を表示しています。
Professional copywriter for SaaS and startups. Expert in landing page copy, positioning, messaging, conversion optimization, and voice-of-customer research. Use when writing compelling copy for SaaS products, landing pages, marketing materials, or when you need help with product positioning and messaging strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Before removing code that looks redundant, wasteful, or "wrong" based on log observations or code review instinct, grep the test suite for tests whose names describe the exact behavior you're about to remove. A test whose title literally describes the "weird" thing (e.g. "calls play() even when player reports playing", "retries even when first call succeeded", "skips cache even when fresh") is a load-bearing workaround, and the production log you're reacting to is probably the workaround working as designed — not a bug. Use when: (1) Tempted to remove a function call that "looks redundant" based on a production log, (2) About to "simplify" a conditional that seems to always take the same branch, (3) Reviewing code and thinking "why would anyone write this?", (4) A log line shows a state that seems impossible or contradictory (e.g. playing=true but positionMs=0 for seconds), (5) CI surfaces a failing test whose name describes exactly what your fix removed.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy funnelcake (api + relay) to ANY environment (production, staging, poc) on GKE via ArgoCD. Use when: (1) Deploying new funnelcake commits, (2) Building Docker images for GKE (amd64), (3) Running ClickHouse migrations, (4) Troubleshooting ImagePullBackOff errors, (5) Syncing staging/poc after production deployment. Covers complete workflow with PRE-FLIGHT CHECKLIST to prevent common deployment failures.
日本語の概要は準備中です。原文の説明を表示しています。
Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge. Use when: (1) Backend works locally but fails in production with "backend does not exist", (2) TLS alert received (alert_id=0) errors when calling external APIs from Fastly, (3) Backends defined in fastly.toml aren't available after deployment. The fastly.toml [[backends]] section only applies during initial service creation - existing services require backends to be added via CLI or API with proper SSL/SNI configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing product display cards for e-commerce.
日本語の概要は準備中です。原文の説明を表示しています。
Collect, normalize, and structure execution traces from instrumented programs (strace, ltrace) into JSON format for downstream analysis. Use when working with system call traces, library call traces, or execution logs that need to be analyzed for debugging, test case reproduction, or verification. Supports parsing strace/ltrace output, filtering noise, extracting debug information, and preparing traces for bug analysis or reproduction workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze reference-image illumination and build accountable Blender lighting from shadow direction, shadow length, softness, exposed faces, environment fill, bounce, practical sources, and material response. Use for reference matching, daylight, interiors, exterior environments, product scenes, atmospheric lighting, or any task where lights must be physically and visually justified instead of added as arbitrary fill or rim lights.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, build, place, and validate physically meaningful Blender object assemblies, including manufactured part boundaries, mechanical seams, mounting interfaces, pivots, hierarchy, constraints, instancing, modular grids, connector planes, and precision snapping. Use when several objects must form one product, machine, architectural module, vehicle, furniture item, mechanism, or environment structure without incorrectly welding independent parts, eyeballing alignment, or leaving continuous shells as overlapping primitives.
日本語の概要は準備中です。原文の説明を表示しています。
Build, calibrate, layer, and validate production Blender materials including bare and coated metal, brushed steel, rust, aged and wet wood planks, stone, concrete, plastic, glass, fabric, water, dirt, moss, and wetness. Use when material identity, UV direction, real-world texture scale, PBR channel handling, roughness response, anisotropy, normal/bump/displacement, transmission, volume absorption, aging, or surface layering determines realism.
日本語の概要は準備中です。原文の説明を表示しています。
Write comprehensive Product Requirements Documents with user stories, acceptance criteria, technical specifications, wireframe descriptions, and prioritization frameworks (RICE, MoSCoW). Create clear specifications for product teams.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
日本語の概要は準備中です。原文の説明を表示しています。
Creative Designer skill. Takes a post concept, a client product photo, or a real lifestyle photo and produces on-brand social media visuals using the client's brand style guide. Four modes — Generate (AI image from concept), Composite (client product photo anchored in an AI-generated scene), Brand (apply text overlay treatment to a real client photo), Stop-Motion Reel (6-frame action sequence exported as MP4). Reads brand-style.md, builds prompts, generates/edits images via Nano Banana MCP, outputs images + prompt log + creative brief.
日本語の概要は準備中です。原文の説明を表示しています。
Complete marketing pipeline for apps, dev tools, libraries, and SaaS products in 2026. Generates positioning, listing/ASO/package-SEO assets, press kit, launch plan, social calendar, email sequences, growth/referral strategy, paid playbook, retention, and community plan. Adapts automatically to app vs dev-tool vs SaaS. Trigger on: marketing, launch plan, app launch, go-to-market, ASO, press kit, product hunt launch, hacker news launch, dev tool marketing, growth strategy, launch checklist, marketing plan, distribution plan.
日本語の概要は準備中です。原文の説明を表示しています。
Audit Apple Ads measurement, AdServices and AdAttributionKit, campaign and keyword structure, Search Match, App Store placements, custom product pages, bidding, budgets, MMP reconciliation, and policy. Use for Apple Ads, Apple Search Ads, App Store ads, Search Match, custom product pages, AdServices, or Apple app-install campaigns.
日本語の概要は準備中です。原文の説明を表示しています。
A clean, calendar-software-first interface anchored on white canvas with black primary CTAs and custom Cal Sans display typography. The system reads as friendly modern SaaS — generous whitespace, soft-rounded cards (~12px), product UI fragments shown directly inside cards, and a dark navy footer that visually closes long-scroll pages. Brand voltage comes from the Cal Sans display headline (a custom geometric face) and from product UI artifacts shown in-card rather than from accent colors.
日本語の概要は準備中です。原文の説明を表示しています。
A three-surface marketing system organized around alternating black, white, and PlayStation Blue chapters that scroll past the viewer like a console launch trailer. Each section has a single editorial purpose — hero photography, console product render, PS Plus tier callout, news strip — and each owns one of three full-bleed canvas modes. The chrome is unusually quiet for a gaming brand: bright PlayStation Blue (`#0070d1`) carries every primary CTA as a fully-rounded pill, the proprietary SST face renders display copy at a signature weight 300 (light) for an airy, premium feel, and a crisp 8px-radius secondary card system carries product info on either canvas mode. The system never decorates — no gradient backgrounds on chrome, no atmospheric mesh, no drop shadows beyond a faint section-divide. Imagery does all the heavy lifting: console glamour shots, game key art, and PS Plus tier illustrations occupy 60-90% of every section, with copy compressed into a small editorial slot.
日本語の概要は準備中です。原文の説明を表示しています。
A warm-canvas editorial interface for Anthropic's Claude product. The system anchors on a tinted cream canvas with serif display headlines, warm coral CTAs, and dark navy product surfaces (code editor mockups, model showcase cards). Brand voltage comes from the cream/coral pairing — deliberately warm and humanist where most AI brands use cool blue + slate. Type voice runs a slab-serif display ("Copernicus" / Tiempos Headline) for h1/h2 and a humanist sans for body. The signature Anthropic black-radial-spike mark anchors the wordmark.
日本語の概要は準備中です。原文の説明を表示しています。
Consolidated Galyarder Framework Product intelligence bundle.
日本語の概要は準備中です。原文の説明を表示しています。