「orm」の検索結果

任務卡的必要調整。Use when ATM task cards contain proposal-style notes or dated additive acceptance sections such as 識別/行為/狀態機提案、不重啟驗收、ATM 演進規劃書 v2、連鎖影響、治理補丁, and those notes must be re-analyzed into the formal task-card sections.

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

UI brief 生成 SKILL — 從 docs/keep.summary.md、正式規格書、task shard、cross-reference-index 與參考圖整理成可執行的 UI brief 或 task-ready brief。USE FOR: 新 UI 畫面開工前、既有畫面補 task shard 欄位、需要收斂 family / proof / normalized recipe / content_contract / smoke_route。DO NOT USE FOR: 直接修改 ui-spec JSON、直接做視覺 QA。

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

Design, build, validate, and ship cross-platform agent skills. Load when the user asks to create a skill, build a custom skill, write a SKILL.md, package a workflow as reusable agent capability, improve or audit a skill, publish a skill, or build a planned skill suite.

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

Create handcrafted static SVG graphics and performant SVG animations — icons, illustrations, loaders, path-draw effects, morphing shapes, and motion paths. Load when the user asks to create SVG, draw an SVG icon, animate an SVG, make an SVG loader, path animation, shape morph, animated logo, line drawing effect, or improve trashy AI-generated SVG. Also triggers on "SVG animation", "SMIL", "stroke-dashoffset", "vector illustration", or "self-contained animated SVG".

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

Break a stuck or complex problem into the smallest sub-question that, if answered, unlocks the next step — then answer it and repeat until the path forward is clear. Load when a problem feels genuinely stuck, when reasoning keeps circling, or when deep-thinking diagnoses a Socratic frame. Also triggers on "I keep going in circles", "what is the real question here", "help me reason through this step by step", "unstick my thinking", "recursive questioning", "what is the root question". Based on the recursive Socratic questioning method (EMNLP 2023) which outperforms CoT and Tree-of-Thought on complex reasoning tasks.

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

Generate 5–10 business idea candidates from a blank page or a founder's domain context — using pain mining, jobs-to-be-done, trend × capability mapping, constraint relaxation, adjacency search, and founder-market-fit prompts. Each candidate is a structured idea card (segment, JTBD, current alternative, why-now, distribution wedge, monetisation, "feels like"). Load when the user asks to generate business ideas, brainstorm startup ideas, find ideas to work on, says "what business should I start", "give me startup ideas", "I don't know what to build", "ideate ventures", "blank-page idea generation", "find me a startup idea", "explore business opportunities". Sub-skill of `venture-exploration`. Hard-bans "Uber for X" / "AI for X" with no specific JTBD, "everyone" segments, and idea cards missing any of the 7 required fields. Does NOT design or evaluate ideas generated — for that use `idea-evaluation`.

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

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

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

Delete, redact, or archive project and global memories when the user says forget this, delete memory, remove that preference, do not remember, redact sensitive information, or retire stale memory.

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

Orchestrator for the experimentation skill suite — turn assumptions and product questions into rigorous, well-instrumented experiments and decision-grade readouts. Routes through backlog → spec → runbook → readout based on user need and existing artefacts. Platform-agnostic with PostHog as the primary binding. Load when the user asks to design an experiment, A/B test something, set up an experiment, run a holdout, test a hypothesis, decide what to test next, read out experiment results, analyse a test, or says "should we A/B test this", "experiment on the landing page", "is this lift real", "ship or kill this test", "what should we test next", "build an experiment backlog", "test the pricing page", "validate this with an experiment".

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

Turn a chosen design direction into a canonical DESIGN.md plus production tokens that don't look vibecoded — state-level colors (8-step neutral ramp, rest/hover/active/ disabled, focus ring), APCA-checked contrast, typography, spacing/radius/motion/elevation, an icon strategy, and component contracts for the core atoms. Emits tokens in the project's stack format (shadcn HSL vars or Tailwind v4 @theme). Load when the user asks to build a design system, generate design tokens, create a DESIGN.md, set up a theme, design a color or type system, pick icons, or when frontend-design routes here. Replaces design-tokens-craft and icon-craft. Sub-skill of frontend-design. Reads DIRECTION.md first.

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

Internal skill. Called by setup-evaluation after a PASS. Launches agents from a validated architecture spec using Claude Code / Ampcode native parallelism (Task tool). Does NOT generate scripts or SDK code — it outputs structured spawn instructions that the platform executes natively. Never invoked directly by the user. Never launches without a setup-evaluation PASS.

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

Run a structured retrospective after development-phase runs of your product's agents — interview the owner in plain language about what went well and poorly, draft ranked improvement hypotheses, then design and run small n=1/n=2 experiments with pre-declared success criteria, guardrails, stop conditions, and a cost/ROI kill-switch. Load when the user says how did that run go, retro this run, the agent output was bad, what should we improve, draft hypotheses, run a small experiment, or after repeated dev runs of an agentic system produce uneven quality. Priority: output quality over performance over cost, each with diminishing-returns stops. NOT a product A/B test (experimentation), NOT coding-agent harness repair (harness-evolution), NOT production-scale learning (runtime-learning-loop).

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

Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".

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

Write a rigorous, decision-grade experiment spec — falsifiable hypothesis, primary metric, guardrails, randomisation unit, exposure definition, method (A/B, holdout, switchback, quasi-experiment, MAB), MDE/duration plan, peek policy, validity threats, and pre-committed decision rule. Platform-agnostic. Load when the user has a candidate experiment and needs to spec it before launch, or says "spec this experiment", "write the test plan", "design this A/B test", "what's the hypothesis", "how big a sample do we need", "how long should we run this", "define the metrics for this test", or when the experimentation orchestrator routes here.

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

Compress an oversized SKILL.md to under 200 lines without losing effectiveness. Load when a skill exceeds 200 lines, when AGENTS.md triggers compression after a skill edit, or when the user asks to compress, shrink, slim down, or optimize a skill. Also triggers on "this skill is too long", "reduce skill size", "make this skill shorter". Applies to all skills including meta skills — the 200-line rule has no exceptions. Preserves hard gates, gotchas, output format, routing triggers, and at least one example. When genuinely CORE content cannot be compressed away, invokes split-skill instead of degrading the skill.

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

Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".

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

Build and deploy applications when the user selects or invokes the Prisma plugin, including requests like "Build a simple Todo app and deploy it" that do not name a stack. Use Prisma Composer for new apps and Prisma Compute for deployment. Also use for explicit Composer/Compute requests, deployment diagnostics, and recovering Composer deployments. Does not cover unrelated ORM or database administration.

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

Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.

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

Create branch, atomic commits, push, and open a pull request with terse, exact messages. Conventional branch + commit format. PR title ≤70 chars, body says "why", not "what". Use when the user says "create pr", "create pullrequest", "create pull request", "make pr", "open pr", "open pullrequest", "open pull request", "submit pr", "raise pr", "/create-pr", or asks to ship/send changes as a pull request (PR/pullrequest/pull-request, any spelling).

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

Automate Cloudinary media management including folder organization, upload presets, asset lookup, transformations, and usage monitoring through natural language commands

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

Automate SEO research with Ahrefs -- analyze backlink profiles, research keywords, track domain metrics history, audit organic rankings, and perform batch URL analysis through the Composio Ahrefs integration.

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

Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.

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

Use this skill when the user requests to generate, create, write, or draft a newsletter, email digest, weekly roundup, industry briefing, or curated content summary. Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution. Trigger on requests like "create a newsletter about X", "write a weekly digest", "generate a tech roundup", or "curate news about Y".

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

Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.

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