5,925 件 ・ 関連度順
概要と使いどころ
Guidelines for designing tools and action spaces for AI agents. Use when building agent harnesses, designing tool interfaces, creating elicitation mechanisms, or optimizing agent-tool interactions. Covers progressive disclosure, tool design patterns, and lessons from Claude Code development.
日本語の概要は準備中です。原文の説明を表示しています。
Create and audit Claude subagents. Use when building specialized workers with isolated context. Includes frontmatter, allowed-tools, and agent patterns. Not for commands or skills.
日本語の概要は準備中です。原文の説明を表示しています。
Build production-ready AI agents using Google's Agent Development Kit with AI assistant integration, React patterns, multi-agent orchestration, and comprehensive tool libraries. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
日本語の概要は準備中です。原文の説明を表示しています。
a set of guidelines to build with Botpress's Agent Development Kit (ADK) - use these whenever you're tasked with building a feature using the ADK
日本語の概要は準備中です。原文の説明を表示しています。
Pre-release checklist for Forge — verify, version bump, changelog, docs, docker build, smoke test. Run before tagging v*.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-release checklist for Forge — runs verify, checks version bump, changelog, docs, and docker build. Use before tagging v*.
日本語の概要は準備中です。原文の説明を表示しています。
Agent-native design engine that makes AI do more useful work: route the prompt, fork a template, weave IFQ ambient craft, verify the artifact, and only install export tooling when requested. One prompt -> shippable HTML, with optional MP4 / GIF / PPTX / PDF / SVG. Triggers include prototype, hi-fi mockup, slide deck, motion demo, infographic, dashboard, whitepaper, changelog, business card, social cover, brand from scratch, design critique, mp4/gif export, 60fps, keynote, PPTX, A-vs-B benchmark. Do not use for production web apps, SEO-critical sites, backend systems, or pure copy edits.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user asks for an HTML-first visual design deliverable or design judgment: interactive prototype, slide deck, motion demo, infographic, dashboard, landing page, whitepaper, changelog, business card, social cover, brand system, design critique, multi-variant exploration, or export to MP4, GIF, PPTX, PDF, or SVG. It is optimized to make AI agents do the routing, template selection, verification, and export prep so humans spend less time prompt-engineering. Do not use for production web apps, SEO sites, backend systems, or pure copy edits.
日本語の概要は準備中です。原文の説明を表示しています。
Finish a development change safely by inspecting the final tree, verifying at the right scope, and performing only the requested Git or PR actions.
日本語の概要は準備中です。原文の説明を表示しています。
Apply risk-based test-driven development to bugs, domain logic, state transitions, parsers, contracts, migrations, and behavior where a failing test sharpens the design.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating VS Code extensions and plugins from scratch through Marketplace publication. Use when developing a VS Code extension/plugin, adding commands or keybindings, building TreeView or Webview UI, publishing to Marketplace, or troubleshooting activation and packaging issues.
日本語の概要は準備中です。原文の説明を表示しています。
Post-process exported PFC 5.0 asphalt DEM data with vedo for particle, force-chain, crack, displacement, velocity, slice, figure, and animation workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.
日本語の概要は準備中です。原文の説明を表示しています。
Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.
日本語の概要は準備中です。原文の説明を表示しています。
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
日本語の概要は準備中です。原文の説明を表示しています。
houtu-dependencies enterprise-grade Spring Cloud microservice foundational framework complete usage guide. GroupId is io.github.lujiafa, covering unified response, exception handling, parameter parsing, session authentication, permission control, signature verification, anti-replay, distributed lock, rate limiting, database field encryption, config decryption, access logging, canary routing, weighted load balancing, Feign enhancement, Sentinel circuit breaking, service discovery, Swagger documentation, crypto utilities, HTTP client, monitoring metrics, and other enterprise-grade capabilities. When the project build file (pom.xml or build.gradle/build.gradle.kts) contains io.github.lujiafa or houtu-related dependencies, or when the user mentions houtu or houtu-dependencies, this Skill must be read and code must be generated strictly following framework conventions. Even if the user is simply doing regular Spring Boot development (e.g., writing Controller, Service, Feign), as long as the project includes houtu, the houtu approach must be used instead of native Spring. When the user explicitly wants to use the houtu framework and the project has not yet included it, proactively add the BOM and required Starters; when the project already includes it, proactively identify and import required module dependencies based on business scenarios during coding, naturally integrating framework capabilities to enhance business services based on business semantics, rather than waiting for the user to specify each one.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the TPACK framework to evaluate and design technology-integrated instruction at the intersection of technological, pedagogical, and content knowledge. Use this skill when the user needs to assess teacher readiness for technology integration, design professional development for ed-tech, or evaluate whether technology use is pedagogically grounded — even if they say 'how to integrate technology in teaching', 'ed-tech evaluation', or 'teacher technology competency'.".
日本語の概要は準備中です。原文の説明を表示しています。
Live developer experience audit. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Conduct a systematic literature review following the PRISMA framework with explicit search strategy, inclusion and exclusion criteria, quality assessment, and transparent synthesis. Use this skill when the user needs to design a reproducible literature search, apply PRISMA flow documentation, develop inclusion and exclusion criteria, assess study quality, or when they ask 'how do I do a systematic review', 'what is PRISMA', or 'how do I make my literature review reproducible'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Grounded Theory (Glaser and Strauss) to build theory inductively from qualitative data through open, axial, and selective coding. Use this skill when the user needs to develop new theory from data rather than test existing hypotheses, conduct theoretical sampling and constant comparison, determine when theoretical saturation is reached, or when they ask 'what theory explains this phenomenon', 'how do I code qualitative data systematically', or 'when do I stop collecting data'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the DeLone and McLean Information Systems Success Model to evaluate IS effectiveness through six interdependent dimensions. Use this skill when the user needs to assess system quality, information quality, or service quality of an IS, diagnose why users are dissatisfied, measure net benefits of a system investment, or when they ask 'how do we measure IS success', 'why are users unhappy with this system', or 'is our system delivering value'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Smith and Lewis's paradox theory to identify and manage organizational tensions across performing, organizing, belonging, and learning dimensions. Use this skill when the user needs to diagnose persistent either/or tensions, design dynamic equilibrium strategies that embrace both poles, or when they ask 'why does solving this problem make it worse', 'how do we pursue exploration AND exploitation simultaneously', or 'why do our strategic tensions keep recurring despite resolution attempts'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Develop e-commerce strategy for Southeast Asian markets including platform selection, payment infrastructure, logistics challenges, and localization requirements. Use this skill when the user is expanding e-commerce to SEA, evaluating Shopee vs Lazada vs Tokopedia, or needs to understand SEA market differences — even if they say 'sell to Southeast Asia', 'which platform in Vietnam', 'SEA payment methods', or 'cross-border e-commerce in ASEAN'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply constructivist learning theory to design instruction based on active knowledge construction, scaffolding, and the zone of proximal development. Use this skill when the user needs to design learner-centered instruction, apply Vygotsky's ZPD or scaffolding principles, or evaluate learning environments for constructivist alignment — even if they say 'how do people really learn', 'student-centered design', or 'scaffolding for learners'.".
日本語の概要は準備中です。原文の説明を表示しています。