2,581 件 ・ 関連度順
概要と使いどころ
AAA hard surface modeling for sci-fi, industrial, military, vehicles, weapons, robotics, and mechanical props. Use for boolean/bevel workflows, panel lines, greebles, chamfers, and manufacturing-accurate surfaces in Blender via MCP.
日本語の概要は準備中です。原文の説明を表示しています。
Dreamcore, weirdcore, and traumacore-inspired art direction for Blender with nostalgic wrongness, liminal nostalgia, and surreal childhood spaces.
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for action, hack-and-slash, beat 'em up, and fighting-game readable combat spaces and prop language in Blender.
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for card games, deck builders, party games, idle/incremental, educational, and rhythm game presentational spaces in Blender.
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for visual novel, interactive movie, walking simulator, and story-driven presentation spaces in Blender.
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for soulslike games in Blender with monumental melancholy spaces, fog gates, bonfire landmarks, and lethal readability.
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for stealth-game spaces in Blender with shadow volumes, patrol-friendly layouts, and concealment materials.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the complete Spring Boot 4 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients.
日本語の概要は準備中です。原文の説明を表示しています。
Use when calling external HTTP APIs from Spring Boot 3 / Spring Framework 6 with declarative HttpExchange interfaces. Covers manual proxy registration, RestClient versus WebClient, and timeout and error handling conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the project follows API-first / OpenAPI-first approach: generating controller interfaces, DTOs, and clients from an OpenAPI spec. Use when you see openapi.yaml, openapi-generator-maven-plugin, or ApiDelegate pattern in the project.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the complete Spring Boot 3 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients.
日本語の概要は準備中です。原文の説明を表示しています。
Use when calling external HTTP APIs from Spring Boot 4 / Spring Framework 7 with declarative HttpExchange interfaces. Covers ImportHttpServices, grouped base URLs and timeouts, and RestClient versus WebClient selection.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent, harness, gateway, MCP workflow, or multi-step automation claims completion and the available traces, checkpoints, approvals, tool calls, or deployment records must be judged without trusting self-reported success.
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
日本語の概要は準備中です。原文の説明を表示しています。
Mathematical visualization skill for equations, proofs, and geometric concepts. **Triggers when:** - User mentions equations, formulas, or mathematical expressions - Request involves mathematical proofs or derivations - Content includes geometric relationships - User mentions LaTeX, calculus, algebra, geometry, trigonometry - Patterns: "equation", "formula", "prove", "derive", "graph", "plot" **Capabilities:** - LaTeX equation rendering with color-coded components - Function graphing and transformations - Geometric constructions and proofs - 3D mathematical surfaces - Step-by-step derivations with highlights
日本語の概要は準備中です。原文の説明を表示しています。
OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.
日本語の概要は準備中です。原文の説明を表示しています。
Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.
日本語の概要は準備中です。原文の説明を表示しています。
Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.
日本語の概要は準備中です。原文の説明を表示しています。
Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy. Use when a prose-producing skill needs the shared readability standard available in context before it drafts. Governs the shape of a written deliverable, where explanation-guidance governs what a run says to a person in a turn. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Does not run the adversarial rewrite pass — dispatch the readability-editor agent for that, or use edit-for-readability to rewrite an existing target. Does not cover explaining technical work to a reader who will not implement it — use explanation-guidance for that.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping contested ownership and responsibility. The entire repository is a valid scope; no module or directory must be named first. Does not assess architectural coupling, cohesion, or technical debt — use architectural-analysis. Does not design service communication, integration patterns, or deployment topology — use architectural-analysis or plan-a-feature. Does not refactor code, diagnose bugs, or review code quality — use refactor, investigate, or code-review.
日本語の概要は準備中です。原文の説明を表示しています。
Owns platform splits for Compose Multiplatform apps: places declarations in commonMain, chooses expect/actual vs interface plus DI, wires host adapters and ports, and validates iOS/Swift interop, desktop and web targets, and platform lifecycle. Use when touching commonMain, expect, actual, iosMain, Swift, SKIE, Flow to Swift, desktop, wasm, web target, or platform-specific code. Do NOT use for routing or architecture (compose-architecture), feature slices (compose-feature), composables or resources (compose-ui), repositories or persistence (compose-data), or Gradle target setup (compose-project).
日本語の概要は準備中です。原文の説明を表示しています。
Create original short videos using the 角色登场｜细节到全身揭晓 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.
日本語の概要は準備中です。原文の説明を表示しています。