「strain」の検索結果

Hand-painted texture art direction for Blender with brushwork albedo, soft value transitions, and stylized PBR restraint.

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

Game-ready animation in Blender including walk/run/idle cycles, combat, mechanical animation, camera animation, constraints, Graph Editor, and NLA workflows via MCP.

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

Use when you want Codex to review its own recent history (last N days or specific period) and improve its behavior. Produces minimal, high-signal updates to AGENTS.md and tiny reusable skills. The goal is long-term fluency — Codex gradually becomes better at your specific style, constraints, and workflows.

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

Design short cinematic encounters that move from calm observation to an impossible close appearance, a readable startle response, and a restrained truce gesture for MiniMax H3 or Seedance 2.0. Use when a user wants fantasy-versus-technology contrast, cockpit or window eyelines, pursuit compressed into 4–15 seconds, non-lethal escalation, identity-reference continuity, or a tense scene that resolves through performance instead of injury or dialogue exposition.

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

Design a Seedance 2.0 science, education, or general-knowledge explainer using layered handmade papercraft, miniature diorama depth, physical paper mechanisms, clear knowledge beats, restrained miniature camera, tactile sound, and stable reference roles. Use for one 4–15 second clip or a longer multi-clip plan; not for flat vector cartoons, live action, or paper-texture-only styling.

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

Turn real product images and a verified brief into a clean Seedance 2.0 minimalist product film. Use for 4–15 second e-commerce or launch ads that require faithful product color/material/geometry, independent anchor-image roles, product-specific actions, restrained camera, readable integrated copy, sound, and a stable closing frame; not for talking-head ads or invented product features.

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

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Always stops for approval before creating any tag, because a pushed tag is never moved. Requires the gh CLI, jq, the claude CLI, and a clean git checkout. This is a repository-maintenance skill for the Han repo itself, not a general review or PR skill — use code-review for local review, post-code-review-to-pr to post a PR review, and update-pr-description for PR bodies.

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

Analyzes test suites and suggests optimal test execution order based on code change impact and project requirements. Use when optimizing CI/CD pipelines, deciding which tests to run before committing, or selecting critical tests under time constraints. Prioritizes tests by analyzing recently modified files, test dependencies, and coverage overlap. Outputs detailed rankings with priority scores and reasoning to help teams run the most impactful tests first.

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

Performs symbolic execution to detect potential errors by exploring execution paths, solving path constraints, and generating test inputs. Use when you need to analyze code for bugs like null dereferences, division by zero, buffer overflows, or assertion violations. Also use to generate test inputs that exercise different code paths, find edge cases, or explore all reachable program states. Supports Python, Java, and C/C++ through manual symbolic execution techniques and integration with tools like KLEE, angr, Z3, and Symbolic PathFinder.

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

Generate concise, structured summaries of requirements for quick team understanding. Use when analyzing requirements from text documents (MD, TXT, DOCX) or technical specifications to create bullet-point summaries that highlight core functionality and dependencies/constraints. Ideal for sprint planning, stakeholder updates, team onboarding, or any situation requiring rapid comprehension of requirement documents.

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

Automatically derives TLA+ properties (invariants, safety, liveness) from natural-language requirements or structured requirement documents. Resolves ambiguities, asks clarifying questions for underspecified requirements, and outputs TLA+-compatible property definitions with semantic explanations. Use when translating system requirements, specifications, or behavioral constraints into formal TLA+ temporal logic properties for verification with TLC model checker.

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

Iteratively enhance user requirements into clear, complete, actionable specifications through analysis and clarification. Use when: (1) Users provide initial requirements that need refinement, (2) Requirements are vague, incomplete, or ambiguous, (3) Creating formal specifications from informal descriptions, (4) Identifying missing constraints, edge cases, or acceptance criteria, (5) Clarifying assumptions and implicit dependencies, or (6) Preparing requirements for design, implementation, or verification. Operates interactively: analyze → ask clarifying questions → refine based on responses.

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

Generate targeted test inputs to reach specific code paths and hard-to-reach behaviors in Python code. Use when: (1) Targeting uncovered branches or specific execution paths, (2) Need coverage-guided test generation, (3) Want to leverage LLM understanding of code semantics for meaningful test inputs, (4) Testing boundary conditions and edge cases systematically, (5) Combining symbolic reasoning with fuzzing. Provides path analysis, constraint solving, coverage-guided strategies, and LLM-driven semantic generation for comprehensive test input creation.

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

Identifies and analyzes conflicts in software requirements including logical contradictions, technical incompatibilities, resource constraints, timeline issues, data conflicts, and stakeholder priority mismatches. Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts that could block implementation or cause rework. Provides detailed conflict analysis with resolution strategies and impact assessment.

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

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.

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

Select, build, and validate Blender deformation and motion-control systems including Simple Deform, Curve, Lattice, Mesh Deform, Shrinkwrap, Surface Deform, Armature, shape keys, hooks, constraints, and drivers. Use when an object must bend, twist, taper, follow a path, conform to a surface, deform smoothly, articulate, or move through controlled mechanical relationships.

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

Design, configure, test, bake, and validate Blender physical effects including Cloth, Soft Body, Rigid Body, collisions, constraints, Fluid, smoke, fire, Dynamic Paint, Ocean, Wave, particles, Boids, force fields, fracture, debris, and secondary effects. Use when gravity, inertia, collision, flexibility, pressure, flow, flocking, emission, or breaking causes the requested result.

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

Convert image references into spatial hypotheses, camera constraints, construction routes, material evidence, and measurable Blender reconstruction gates. Use whenever a user asks to replicate, recreate, match, clone, or reconstruct a scene, environment, object, material, lighting setup, or shot from one or more images, especially when room connectivity, hidden space, perspective, visible-frame fidelity, material identity, aging, wetness, or photographic treatment matters.

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

Turn vague or partially formed AI, computer-science, data-driven, and engineering-method research directions into evidence-grounded, falsifiable, paper-ready Research Idea Briefs through heuristic questioning, staged confirmation, literature positioning, novelty attack, and method-figure planning. Use when the user needs to clarify a research idea, formalize inputs/outputs/objectives/constraints, frame background and motivation, select 3-5 anchor papers, identify a defensible gap, derive 2-3 contributions, stress-test novelty, or design an input-to-output method framework and core-paper figure. Also trigger on requests such as 明确科研 idea、启发式梳理 idea、互动追问科研问题、梳理论文创新点、定义研究任务、找对标论文、把研究方向变成论文方案、画方法框架图. Do not use as the primary workflow for running experiments, exhaustive systematic reviews, drafting full manuscript sections, or polishing finished prose.

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

| Type-safe ORM for Cloudflare D1 databases using Drizzle. Use when: building D1 database schemas, writing type-safe SQL queries, managing migrations with Drizzle Kit, defining table relations, implementing prepared statements, using D1 batch API, or encountering D1_ERROR, transaction errors, foreign key constraint failures, or schema inference issues.

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

Idempotent API operations with idempotency keys, Redis caching, DB constraints. Use for payment systems, webhook retries, safe retries, or encountering duplicate processing, race conditions, key expiry errors.

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

Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.

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

Base template for Stage2 rebuttal refinement. Use when creating or extending conference-specific Stage2 skills so all venues share the same high-quality writing constraints, JSON output format, and normalization rules.

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

Design normalized database schemas with tables, relationships, indexes, and constraints for any application domain. Use when the user requests database schema design or provides relevant inputs for this workflow.

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