3,194 件 ・ 関連度順
概要と使いどころ
Updates an existing OpenCode skill to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode skill", "fix opencode skill", "migrate skill to opencode", or wants to modernize an existing OpenCode SKILL.md file.
日本語の概要は準備中です。原文の説明を表示しています。
Updates an existing OpenCode command to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode command", "fix opencode command", "migrate command to opencode", or wants to modernize an existing OpenCode command file.
日本語の概要は準備中です。原文の説明を表示しています。
Connect a site's existing WebMCP tools to AgentLane without rebuilding them. Use when a codebase already registers document.modelContext tools — natively or through any SDK — and the developer wants them visible in AgentLane, migrated onto @nekuda/webmcp-sdk with durable stable keys and verified to behave exactly as before.
日本語の概要は準備中です。原文の説明を表示しています。
Onboarding workflow for cross-library KB query in a consulting practice. Discovers existing user-scope library registrations, prompts for additions, validates each library, helps activate the relevant ones for the current project, runs a smoke test, and reports a clear "ready" or "issues to fix" verdict. Use --verify-only to skip prompting and just validate existing setup (sub-task 23 of
日本語の概要は準備中です。原文の説明を表示しています。
Deploy, diff, bootstrap, inspect, roll back, or destroy AWS CDK applications with the community CDKD CLI while preserving safe production and state-management boundaries. Use when the user mentions cdkd or CDK Direct, asks for faster CDK deployments in development or test environments, or wants to evaluate whether an existing CDK app can use CDKD. Also use for CDKD import, export, state, events, and deployment troubleshooting. Prefer the upstream AWS CDK CLI for production and for existing CloudFormation-managed stacks unless the user explicitly approves a management migration.
日本語の概要は準備中です。原文の説明を表示しています。
Builds complete, optimized Claude prompts and Project scaffolds from task descriptions. Use when building, designing, creating, or structuring a Claude prompt or system prompt. Trigger on: "build me a prompt," "compile a prompt for," "create a system prompt," "write a Claude prompt," "design a prompt for," "help me write a prompt," "scaffold a Claude Project," "design a Project for." Uses a four-stage methodology (Parse, Select, Construct, Validate) and a tested 5-layer architecture (Identity, Objective, Context, Reasoning, Output + Quality Control). In Project Mode, the Compiler is global-layer-aware — checks User Preferences, installed Skills, and MCP Connectors to avoid redundancy and flag gaps. Do NOT use for auditing existing prompts (use rootnode-prompt-validation if available) or diagnosing existing Projects (use rootnode-project-audit if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
日本語の概要は準備中です。原文の説明を表示しています。
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when: (1) creating a new SKILL.md, (2) initializing a skill directory, (3) packaging a .skill file, (4) improving or iterating on an existing skill, (5) understanding skill best practices and design patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Create or evolve an implementation-agnostic website design system from existing-site evidence, verified brand inputs, and an optional Visual Reference Brief. Use to establish visual and restrained-motion baselines, extract an existing site's rendered system for style-preserving extensions, validate one selected baseline with a compact Design Board, or update shared rules before page/module design. Do not conduct cross-industry reference research, map Elementor settings, create page layouts, design modules, or implement production code.
日本語の概要は準備中です。原文の説明を表示しています。
Audits existing landing pages for conversion rate optimization. Scores hero section, CTA placement, social proof, objection handling, and form friction on a 1-10 scale. Use when someone says 'audit my landing page', 'improve conversions', 'why isn't my page converting', 'CRO audit', 'landing page feedback', 'optimize my signup page', 'page review', 'conversion rate', 'bounce rate is high', 'nobody is signing up', or anything about improving an existing page's performance. Even if they just share a URL and say 'what do you think' or 'how can I improve this' — if there's a page involved and conversion matters, this is the skill. Always use this over generic advice when an actual page exists to audit.
日本語の概要は準備中です。原文の説明を表示しています。
Take one piece of long-form content and atomize it into 10-20 platform-specific posts across 8 platforms (Twitter/X, LinkedIn, Instagram, Reddit, TikTok, YouTube, Threads, Bluesky). Turns blog posts, podcasts, videos, and newsletters into native social content for each platform. Use this skill whenever someone has existing content they want to distribute — even if they don't say 'atomize' explicitly. Triggers include: 'repurpose this', 'turn this into posts', 'social content from my blog', 'I wrote an article and want to promote it', 'cross-post this', 'content distribution', 'break this down for social', 'I have a podcast episode', 'turn this video into clips', 'make social posts from this', 'content calendar from this article', or any request to get more mileage from existing content.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Tip in the ai-product-dev-tips repository following the existing directory/format conventions, and register its link in the root README.md. Use this whenever the user wants to add, create, or write a new Tip in this repo — e.g. "nlp_processing に〜の Tip を追加して", "新しい Tips を作って", "〜の解説 Tip を書いて", "this repo に〜のネタを追加". It picks the right category and next sequential number, matches the README format of nearby Tips, generates code scaffolding (Dockerfile / requirements.txt / *_cpu.sh / *_gpu.sh / *.py) only when the Tip needs runnable code, and inserts the link into the correct <details> section of the root README. Trigger this even if the user doesn't say the word "skill" — any request to add a new entry to this Tips collection should use it.
Azure OpenAI画像生成CLIツール (gpt-image-1.5 / gpt-5.1)。テキストから画像生成、画像のAI編集、画像の内容説明を行う。Use when the user wants to (1) generate images using Azure OpenAI, (2) edit existing images with AI, (3) explain image contents. Triggers on "画像を生成", "画像を編集", "画像の説明", "generate an image", "edit this image", "describe this image", "imgenで".
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Quarkus + LangChain4j project against this stack's agentic conventions — a read-only conformance or gap-analysis review. Use when the user asks to audit, review, check, assess, or validate a Quarkus project against the LangChain4j agentic conventions, or wants to know whether an existing project conforms to (or is ready to adopt) this stack. User-invoked only.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold Quarkus + LangChain4j projects end-to-end and add agentic components to existing ones — AI services, tools, agents and multi-agent workflows, RAG pipelines, MCP clients and servers (Model Context Protocol), guardrails, and embedding store setups. Use this whenever the user wants a new Quarkus + LangChain4j project or module created, or an agentic component added to an existing project in this stack, including a baseline pom.xml, application.properties, project layout, or starter classes.
日本語の概要は準備中です。原文の説明を表示しています。
Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting concern like error handling, or the whole codebase. This includes requests to "review my changes", "check this code", "audit for best practices", "look for issues", "what's wrong with this", or "flag anything that could bite us". Use it even when the user doesn't say "review" explicitly but is asking you to find problems, inconsistencies, or anti-patterns in existing Rust code. Do NOT use for requests to write, fix, refactor, test, explain, or implement code — only for evaluating existing code.
日本語の概要は準備中です。原文の説明を表示しています。
Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Galyarder Framework.
日本語の概要は準備中です。原文の説明を表示しています。
Convert web articles or blog posts into slides through a content.json pipeline, translate or rebuild existing PPTX files onto a template, and edit an already-open PowerPoint deck with COM Automation (RefURL, overflow review). Use for article-to-slides conversion, deck translation, template-based rebuilds, or live COM editing of an open deck. Not for simply reading, inspecting, or lightly editing a .pptx file. Triggers on 記事をスライド化, スライド翻訳, 開いているパワポを編集, COM自動化, RefURL, content.json.
Generate a single self-contained HTML file — a horizontal slide deck, a vertical-scroll explainer document, or a fixed-canvas summary image — with zero external runtime dependencies, then verify it mechanically. Use when the user asks for HTMLスライド, 単一HTMLスライド, single-file HTML presentation, ブラウザーで開く説明資料, HTML 説明資料, HTMLサマリ画像, or self-contained HTML, or wants to hand someone a deck or explainer that opens anywhere without PowerPoint. Also use to embed images into such a file or to re-check an existing one. Does not output PPTX.
Create or review a reusable skill (SKILL.md) that packages a workflow, and decide whether the request should be a skill instead of a prompt, instruction, agent, or hook. Use when creating a new skill, extracting a workflow from a conversation, updating an existing skill, reviewing SKILL.md quality, or fixing weak skill triggering. Triggers on "create skill", "/create-skill", "new skill", "review skill", "fix skill trigger", "SKILL.md", "スキル作成".
Generate draw.io editable diagrams (.drawio, .drawio.svg) from text, images, or Excel. Orchestrates 3-agent workflow (Analysis → Manifest → SVG generation) with quality gates. Use when creating architecture diagrams, flowcharts, sequence diagrams, or converting existing images to editable format. Supports Azure/AWS cloud icons. Triggers on draw.io, drawio, ダイアグラム, アーキ図, フローチャート, シーケンス図.
Build a new-topic PPTX by reusing an existing reference deck's template (layouts / footers / fonts / palette) while replacing all content from primary sources. Use when "use this product deck's look for a different product deck", "use this deck as template for new topic", "参照デックの体裁で別内容を作る", "既存 PPTX を流用して別テーマで作り直す". Not for deck translation, from-scratch generation, or outline-only planning.