143 件 ・ 関連度順
概要と使いどころ
Modern TypeScript project architecture guide for 2025. Use when creating new TS projects, setting up configurations, or designing project structure. Covers tech stack selection, layered architecture, and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Dermatologist. Use when a task calls for Dermatologist judgment. Clinical-research dermatologist: layered skin anatomy, inflammatory dermatoses and trial endpoints, dermoscopy vs clinical ABCDE, biopsy/pathology, patch testing, telederm, AAD guidelines, and topical steroid potency.
日本語の概要は準備中です。原文の説明を表示しています。
Production guidance for reusable layered 2D character rigs in browser-rendered and video media. Use for SVG hierarchies, pivots and constraints, FK/IK planning, pose and facial libraries, acting, cycles, deterministic handoff, crop variants, and rig QA; not for character concept continuity, 3D armatures, or motion-capture solving.
日本語の概要は準備中です。原文の説明を表示しています。
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources. Use when the user needs thorough investigation, market research, technical deep-dives, due diligence, or comprehensive analysis on any subject.
日本語の概要は準備中です。原文の説明を表示しています。
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
日本語の概要は準備中です。原文の説明を表示しています。
Develop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.
日本語の概要は準備中です。原文の説明を表示しています。
Develop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or extending a Java service with Quarkus - layered architecture, JAX-RS resources, CDI beans, Panache persistence, and native-friendly patterns
日本語の概要は準備中です。原文の説明を表示しています。
Creates FastAPI endpoints with layered architecture (Router → Service → Repository). Use when creating new API endpoints, CRUD operations, or scaffolding a new domain module in a FastAPI project.
日本語の概要は準備中です。原文の説明を表示しています。
Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting a new Spring Boot 4 project — scaffolding a service, REST API, or modular backend; picking an architecture (layered, package-by-module, modular-monolith, tomato, DDD-hexagonal); selecting Spring Boot 4 features; or applying the bundled templates and references in this skill. Not for migrating existing projects or for isolated JPA/repository work without broader project-creation context.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for defending AI applications against prompt injection, jailbreak attacks, indirect injection via tool outputs, and data exfiltration through tool calls — input sanitization, output filtering, canary token detection, and layered defense architecture / Panduan ahli pertahanan aplikasi AI terhadap prompt injection, serangan jailbreak, injeksi tidak langsung via output tool, dan eksfiltrasi data melalui tool calls — sanitasi input, filtering output, deteksi canary token, dan arsitektur pertahanan berlapis.
日本語の概要は準備中です。原文の説明を表示しています。
Batch download academic paper full-text (PDF/XML) from a list of DOIs. Handles 25 DOI prefixes across 19 publisher families via three layered routes: (1) publisher TDM APIs requiring institutional subscription (Elsevier ScienceDirect, Wiley Online, Springer Nature), (2) Open Access sources (Crossref, Unpaywall, OpenAlex), and (3) a browser-based fallback for paywalled publishers without TDM access (ACS, RSC, IEEE, AIP, IOP, APS, Annual Reviews, T&F, Chinese journals). Browser fallback offers two routes — Route A drives the user's logged-in Chrome via the OpenClaw `browser` tool with `profile="user"` (best for interactive sessions), Route B uses the standalone `auto-paper-harvester` CLI with its built-in Playwright (best for unattended bulk runs). Use when the user wants to harvest, scrape, fetch, or bulk-download papers from a DOI list, savedrecs export, or Excel; or wants to fill missing full-text PDFs for an existing literature collection. Triggers on phrases like "批量下载文献", "下载全文", "harvest papers", "scrape full text", "TDM API", "下载 Elsevier 全文", "Wiley 批量下载", "下载 PDF".
日本語の概要は準備中です。原文の説明を表示しています。
Software design principles, patterns, and architecture from SOLID through distributed systems. Covers the five SOLID principles with violations and fixes, DRY/KISS/YAGNI heuristics, separation of concerns, 12 GoF design patterns organized by intent (creational, structural, behavioral), architectural patterns (MVC, MVP, MVVM, layered, hexagonal, microservices, event-driven), coupling and cohesion metrics, dependency injection, and the design decision framework for choosing between competing approaches. Use when making design decisions, reviewing architecture, refactoring code, or teaching software engineering principles.
日本語の概要は準備中です。原文の説明を表示しています。
Shared Python 3.11+ development rules — type safety and the boundary policy for `Any` (ty, native generics, Protocol, TypeIs, Pydantic), layered architecture and SOLID, error handling, security, performance, identifier naming, PEP 723 script dependencies, Rich/Typer output, tooling defaults (uv, ruff, ty, hatchling, pytest), and testing requirements (behavioral coverage, TDD). Activates when any Python skill or agent needs the shared rules for implementation, code review, refactoring, or test authoring.
日本語の概要は準備中です。原文の説明を表示しています。
Convert Chinese provinces, municipalities, autonomous regions, cities, counties, ancient cities, and cultural regions into restrained contemporary posters led by one culturally transformed Chinese character. Supports direct one-shot final image generation and layered production. Use when the user asks for a 中国省域文化海报、城市文化海报、地域文化视觉、极简大字海报、地区系列海报、展览主视觉、出版或社交封面，requests 直接生成、一次成图、不合成、不要后期、direct generation, or wants cultural analysis, art direction, image prompts, rendered poster images, or a coherent batch series for places such as 北京、广东、福建、江南、岭南、巴蜀 or 关中.
日本語の概要は準備中です。原文の説明を表示しています。
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
日本語の概要は準備中です。原文の説明を表示しています。
List, get, set, or delete the layered ASE configuration values across the user/project/task/session scope chain. Use when the user wants to "configure" ASE, or to inspect or change a configuration key like `agent.persona`, `agent.guidance`, `project.boxing`, or `project.task.lifecycle`.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates mezzanine structures with PIK toggle, equity kickers, and intercreditor subordination mechanics. Use when analyzing mezzanine financing, comparing subordinated debt terms, or modeling layered capital structures.
日本語の概要は準備中です。原文の説明を表示しています。
Add or refine depth through elevation systems, raised and inset surfaces, layered overlap, and meaningful shadow behavior so interfaces feel structured instead of flat. Use when the user mentions depth, elevation, shadows, layering, flat cards, pressed states, drag feedback, or inset controls.
日本語の概要は準備中です。原文の説明を表示しています。