7,992 件 ・ 関連度順
Evaluate a single retort experiment run. Score the generated code against the task's TASK.md requirements, run its build and tests, compute metrics, and emit a structured evaluation report plus a machine-readable findings file.
日本語の概要は準備中です。原文の説明を表示しています。
Determine the TRUE cause of a failed retort run before attributing it. Ground-truth every failure (run its tests, read its agent logs, inspect its workspace) and classify it as an infrastructure false-fail, a genuine model miss, or an environment issue — never trust the gate verdict or a log signature alone. Use whenever a run is recorded failed (test_coverage=0 / gate fail), a pass rate looks low, or you're deciding whether a "failure" is real before reporting or proceeding.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize the architecture of code generated by a single retort run. Produces module-level structure, interfaces, and control flow in a form suitable for cross-run comparison — not a full codebase-summary.
日本語の概要は準備中です。原文の説明を表示しています。
Options price action strategy, volatility-aware entries, options structure selection by market regime, delta and gamma positioning, options overlay on directional views, expiry selection
日本語の概要は準備中です。原文の説明を表示しています。
Technical execution timing, entry exit signals, price action analysis, volume profile, market structure, support resistance levels, trend identification, Wyckoff method, auction market theory, trade management timing, position entry exit optimization
日本語の概要は準備中です。原文の説明を表示しています。
Price action market structure analysis, trend vs trading range classification, Always In directional framework, buying/selling pressure analysis, market cycle phase identification, the price action methodology
日本語の概要は準備中です。原文の説明を表示しています。
The research-domain clarification skill — find underspecified items in a thesis spec.md (prose wrong_if, universe rows without rationale, missing budget/expiry/pins, ambiguous pillars), ask the human structured questions WITH options (max 5 per round), encode the answers back into spec.md's Clarifications section, and re-evaluate checklists/thesis-quality.md after every write (Q32 bidirectional maintenance).
日本語の概要は準備中です。原文の説明を表示しています。
Trading as a business, performance review process, trade journaling, capital allocation discipline, business infrastructure for traders, KPI tracking for trading operations
日本語の概要は準備中です。原文の説明を表示しています。
Sector overview, TAM estimation, competitive concentration HHI, regulatory landscape, industry analysis, market size analysis, sector trends, industry structure, market growth rate, sector profitability
日本語の概要は準備中です。原文の説明を表示しています。
Medicines pipeline analysis over structured universes: Phase I-III assets with probability-of-success discipline (unadjusted peak x POS = modeled value; POS changes logged with reasons), trial status-diff tracking, and mechanism/competitor mapping via drug-knowledge lookups.
日本語の概要は準備中です。原文の説明を表示しています。
Generate persistent, explorable 3D worlds/environments with Marble by World Labs — from text, a single image, multiple images, video, or a 360 panorama, plus coarse-structure blocking with Chisel. Use this skill when a task needs a navigable 3D scene, VR/immersive backdrop, virtual-production environment, previz set, game-blockout, or web/engine-ready Gaussian splat or mesh, and you must choose an input mode, a Marble model, an export format, and a plan/API route, then review world quality. Covers the Marble web app and the World API, editing/expansion, output formats and what each supports downstream, import into Unity/Unreal/Blender/Houdini/web, pricing/credits, capability limits, and rights/licensing. Not for flat text-to-image, text-to-video clips, or real-time on-the-fly world models (Marble outputs are downloadable, static 3D environments).
日本語の概要は準備中です。原文の説明を表示しています。
Generate, remix, edit, inpaint, reframe, background-process, describe, layerize, and upscale images with the Ideogram Developer API. Use when Codex must integrate Ideogram 4.0 or 3.0, render reliable typography or structured layouts, use style or character references, build synchronous or webhook workflows, migrate legacy Ideogram endpoints, or reason about Ideogram API pricing, safety, privacy, and production QA.
日本語の概要は準備中です。原文の説明を表示しています。
Use Adobe Firefly Services to generate, edit, expand, fill, match, composite, and upscale still images through the current REST APIs. Apply when selecting Firefly Image 5 versus Image 3/4 or custom models, implementing authenticated asynchronous image workflows, using style or structure references, building product composites, handling provenance and enterprise rights, or diagnosing Firefly image jobs in production. Exclude Firefly video, audio, and unrelated Creative Cloud APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Build and operate rights-aware Bria FIBO and FIBO Lite image-generation workflows with structured prompts, reference images, asynchronous status handling, webhooks, cost gates, and safe artifact downloads. Use when a user asks for Bria/FIBO generation, refinement, inspiration, reproducibility, hosted API integration, or a licensed-data image workflow; do not use for FIBO Edit, video, generic image editing, or third-party FIBO gateways.
日本語の概要は準備中です。原文の説明を表示しています。
Produce audio-first podcast episodes with generative tools — design the show and episode format (interview, narrative, news brief, two-host conversational), write scripts for the ear, decide between fully-synthetic and hybrid (recorded human + synthetic) production and meet the disclosure duty each triggers, cast and direct multi-voice TTS for consistency and chemistry, build episode structure (cold open, intro/outro, segments, ad slots), assemble and edit, clear music and SFX rights, hit podcast loudness and delivery standards, ship metadata/chapters/transcripts through RSS, and pass platform AI-content policy and QA before publishing. Use this skill whenever the deliverable is a podcast episode or a podcast show bible, or when an agent must make production, rights, disclosure, or delivery decisions for spoken-word audio. Not for music tracks, single-voice notification prompts, or video where picture leads (route audio-for-video to a video skill).
日本語の概要は準備中です。原文の説明を表示しています。
Provider-independent cinematic trailer production for AI agents creating movie-style trailers, teaser trailers, launch trailers, game trailers, documentary trailers, series promos, and high-impact generated-media previews. Use for trailer strategy, structure, shot planning, voiceover/title-card copy, music and sound-design direction, generated-video prompt translation, edit pacing, platform/runtime choices, delivery handoff, rights/claims caveats, and trailer QA.
日本語の概要は準備中です。原文の説明を表示しています。
Provider-independent editing and montage direction for AI agents producing generated videos, ads, trailers, social clips, explainers, product videos, documentary-style pieces, and music- or beat-driven cuts. Use when planning, revising, QAing, or handing off an edit: story structure, shot selection, continuity, montage theory, rhythm and pacing, J/L cuts, match cuts, cutaways, transitions, beat sync, platform timing, source/generated asset management, revision workflow, and composition handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when the user asks to 'review this', 'code review', 'quality check', 'validate the code', 'check my code', 'review the delta', or 'review this PR'.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use when the user says 'assess my codebase architecture', 'what direction should my codebase go', 'architecture compass', 'understand my architecture', 'audit architecture drift', 'architectural assessment', or 'help me understand what is wrong with my codebase'.
日本語の概要は準備中です。原文の説明を表示しています。
Guide structured design thinking through 5 progressive levels before any code is written. Levels: Capabilities, Components, Interactions, Contracts, Implementation. Use when building new features, refactoring significant code, designing modules, or when the user says 'design this', 'architect this', 'let's think before coding', 'walk me through the design', or 'whiteboard this'. For simple utilities enter at Level 4 (Contracts), for single-component tasks at Level 2 — see Complexity Calibration. Do not use for quick bug patches.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new Lattice skill — atom, molecule, or refiner — following all framework conventions. Writing skill files manually almost always produces convention violations: wrong section order, missing confirmation gates, defaults.md without the right structure. This skill knows all of that and guides you through it. Use whenever adding any new atom, molecule, or refiner to Lattice, or when the user says 'create a new skill', 'add an atom', 'add a molecule', 'add a refiner', 'build X for Lattice', 'new lattice skill', or 'skill forge'. Does not validate, align docs, or deploy — those are separate skills you run after.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate a structured conversation to define DDD guardrails for domain design within a repository. Produces a formal ddd-principles.md document that the domain-driven-design atom will use as its override. Use when setting up domain design principles, defining aggregate rules, or when the user says 'setup DDD', 'define domain rules', 'DDD principles', or 'help me define my domain patterns'.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate a structured conversation to define language-specific idioms and patterns for a repository. Produces a language-idioms.md document consumed by multiple atoms to adapt pseudocode defaults to the project's language. Use when setting up a new project, switching languages, or when the user says 'setup language', 'define language idioms', 'configure language', 'language patterns', or 'adapt for Go/Rust/Python'.
日本語の概要は準備中です。原文の説明を表示しています。
Apply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user mentions 'validate this spec', 'check this feature', 'requirement quality', 'is this spec complete', or 'requirement-quality'. This skill governs the craft of writing individual feature specifications — not technical design (see design-blueprint), not implementation (see code-forge).
日本語の概要は準備中です。原文の説明を表示しています。