339 件 ・ 関連度順
概要と使いどころ
Apply these opinionated JavaScript conventions whenever writing or reviewing JS or Node: ESM-first packaging, choosing between Promise combinators, error handling that doesn't swallow failures, AbortController for cancellation, keeping the event loop unblocked, and reaching for platform APIs before dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
GEODE runtime context for model selection and metadata, architecture, packaging, release, docs, CI, AgenticLoop, async runtime, and plugin boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Generate multiple angles and shot types of a single product for ecommerce-ready image sets. Produces a coherent set (hero 3/4, front, side, back, detail macro, scale, packaging, in-hand) keeping product identity consistent across shots. Use when the user says "different angles", "product shots", "ecommerce image set", "shot list", "PDP gallery", or needs a multi-view set of one product. Part of the Creative Production set.
日本語の概要は準備中です。原文の説明を表示しています。
Bridge Codex to web-based AI model products by packaging local task context, scrub-checking it, sending it through an approved browser surface to ChatGPT Pro, Claude, Grok, Gemini, or another web model, waiting for the answer, and returning the model response to the user or Codex. Also guide DevSpace-like MCP Connector Mode when the user wants ChatGPT Pro or another MCP-capable web host to access approved local workspaces without relying on Codex browser automation. Use when the user asks for GPT Pro, ChatGPT Pro, Claude web, Grok, Gemini web, web model bridge, external model consult, ask another model, second opinion, use a web AI model, browserless agent access to GPT Pro, MCP connector, DevSpace-like workflow, or send local repo context to a browser-based model for planning, review, debugging, architecture discussion, or implementation guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning or upgrading an internal skill/workflow for business operations, especially when turning a messy idea into a structured skill plan, migration plan, acceptance checklist, or packaging decision. Particularly useful for Obsidian knowledge base consolidation, workspace migration, content library cleanup, and integrating multiple workbenches into one operating system.
日本語の概要は準備中です。原文の説明を表示しています。
Guides Quarkus development across REST APIs, CDI dependency injection, Hibernate ORM, Panache, configuration, OpenAPI, templates, messaging, security, observability, packaging, and tooling. Use when building Quarkus applications, adding endpoints or clients, configuring datasources or OIDC, debugging build or runtime issues, or choosing extensions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when packaging a codebase to a single AI-friendly file for LLM analysis — local or remote, XML/Markdown/JSON, token counting, gitignore filtering, peer-side `repomix` CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a JavaScript/TypeScript package is consumed by another package — exports map, peer vs. direct dependencies, files allow-list, and whether it should be built at all.
日本語の概要は準備中です。原文の説明を表示しています。
[Skill Management] Use when creating a new Claude Code skill, adding reference files or scripts to an existing skill, scanning/fixing invalid skill headers, or optimizing/packaging skills. Triggers on: create skill, new skill, add skill reference, add skill script, fix skill, validate skill, package skill.
日本語の概要は準備中です。原文の説明を表示しています。
Manage agent-skill lifecycles across local, global, project, Skill Hub, skills.sh, GitHub, plugin-cache, and system roots. Use when searching, recommending, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, or validating skills; choosing project versus global scope; verifying upstream source, stars, or installs; or working with skill-upgrade, check_upstreams.ps1, sync-pull/push, junctions, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Agent Skills across Codex, Claude Code, local/global/project roots, Skill Hubs, GitHub, skills.sh, and managed plugin caches. Use when searching, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, validating, resolving upstream sources, choosing runtime or scope, or working with skill-upgrade, check_upstreams.ps1, Claude Code plugins, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and optimize a skill system with evidence. Use for skill architecture, token or context waste, role and prompt boundaries, routing hits or misfires, plugin packaging, registry/docs/source drift, duplicate workflows, or deciding whether a reusable change belongs in a skill. Runs deterministic checks first and applies only authorized, minimal fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit compatibility adapter for repairing existing v1 Codex pets with 8x9 atlases. Not for new pets or v2/8x11 packaging; use the installed v2-capable pet skill for those tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Build, install, validate, and debug custom Exasol virtual schema adapters. Covers source-specific JDBC dialect implementation with `virtual-schema-common-jdbc` including `SqlDialect`, metadata reader behavior, type mapping, and pushdown capabilities, custom document-file adapter code boundaries, custom adapter properties, JAR packaging, BucketFS deployment, adapter script setup, `EXPLAIN VIRTUAL` validation, and adapter-side remote debugging workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Generate professional AI product photography and commercial images. Models: FLUX, Imagen 3, Grok, Seedream for product shots, lifestyle images, mockups. Capabilities: studio lighting, lifestyle scenes, packaging, e-commerce photos. Use for: e-commerce, Amazon listings, Shopify, marketing, ...
日本語の概要は準備中です。原文の説明を表示しています。
Reviews marketing, packaging, web or sustainability text against the environmental-claim rules the user supplies (house policy, regulator guidance extract, industry code) and returns a DRAFT claims review: every environmental claim quoted verbatim with location and family, the evidence the text or evidence pack offers for it with date and scope, the supplied rule passages that bear on each claim, observations as read, and separate question lists for legal and for marketing. No compliance, greenwashing or substantiation verdict. Use when the user asks to "review these green claims", "check this copy against our environmental claims policy", "what evidence do we have for carbon neutral here", "list the sustainability claims in this brochure" or "prepare questions for legal on this eco campaign". Do not use for mapping general factual claims to evidence, use claims-evidence-map instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
当用户在设计促销、定价或折扣策略，需要让"省钱"感知最大化时调用此 skill。核心信号：用户在纠结"怎么呈现折扣更有吸引力""消费者会不会觉得划算""原价和折扣价该怎么标"。不适用于：纯成本核算、B2B大额复杂定价谈判、品牌溢价策略（与折扣无关）。关键触发：涉及"打折""促销""优惠""划算"等定价呈现决策的场景。
日本語の概要は準備中です。原文の説明を表示しています。
UI stack, build, and test conventions for NV oOS React SPA addons (toolkit-shell, chat-spa, schedule-anything-spa, saas-controller) — three sanctioned build patterns plus the standalone Pro SPA Vite app (examples/nvoos-pro-spa-vite), dual-React guard, headless component rules, NDS tokens, Tailwind v4, @xyflow/react v12, vitest/jsdom gotchas, the full-JS-rebuild map, and the TS-shadows-JS webpack gotcha. Use when building or modifying SPA addon UI, writing SPA JS tests, upgrading SPA deps, or rebuilding JS for packaging.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for WordPress.org submission readiness of NV oOS standalone plugins (nvoos-docs-hub live at 0.5.3; nvoos-content-graph live at 1.0.10 in the re-submission loop; nvoos-design-system next in the pipeline — issue #6811). Covers the 18 wp.org guidelines, the Plugin Check (PCP) gate in CI and Docker, PCP finding triage, the reviewer-reply loop (findings taxonomy from the real 0.4.3 review, related-issue sweep checklist, reply-email template), packaging exclusion tri-sync, readme.txt standards, .wordpress-org listing assets, and the NV oOS Complete checkout-flow disclosure discipline (docs-hub 0.5.3, content-graph). Use when preparing a wp.org submission, responding to a reviewer email, fixing the plugin-check CI job, triaging PCP findings, or capturing listing screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
Design or evaluate pricing and packaging using customer value, willingness-to-pay evidence, competitive context, unit economics and experiment design.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.
日本語の概要は準備中です。原文の説明を表示しています。
Draft hooks, the outline, and the packaging promise. Use at the outline stage, or when the user says "outline this", "write the outline", or "what is the hook".
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, editing, reviewing, packaging, or organizing AI-agent skills and deciding whether a skill should be text-only, script-backed, or backed by an ML/specialist pipeline.
日本語の概要は準備中です。原文の説明を表示しています。