1,707 件 ・ 関連度順
概要と使いどころ
Guide for writing Rust doc comments that produce accurate generated contract documentation. Use when editing Instantiate/Execute/Query/Response types or any public schema-facing API.
日本語の概要は準備中です。原文の説明を表示しています。
Repository quality gates for Rust and generated artifacts. Use when validating changes locally or before committing Rust, schema, or documentation updates.
日本語の概要は準備中です。原文の説明を表示しています。
Axone deployment workflows with cargo-make, cw-orch, and Abstract. Use when publishing modules, installing them on accounts, running local chain tasks, or inspecting deployments.
日本語の概要は準備中です。原文の説明を表示しています。
Take screenshots and interact with web pages using a headed Playwright browser. Use when you need to visually inspect a URL, capture a screenshot, interact with a page (click, type, scroll), or verify what a page looks like rendered. **Triggers — use this skill when:** - You need to screenshot a URL (Penpot share link, localhost, public site) - User says "show me", "how does it look", "take a screenshot" - You want to visually verify your own work (e.g. after creating Penpot designs) - User asks to review a live page or prototype - You need to interact with a page (click buttons, fill forms, trigger states)
日本語の概要は準備中です。原文の説明を表示しています。
AAMP (Agent-to-Agent Mail Protocol) via aamp-cli. Use this skill when the agent needs to register a mailbox, listen for incoming AAMP mail, inspect a task thread, complete a pairing URL, dispatch a task, or reply with task.result / task.help_needed. Prefer the CLI over hand-written HTTP requests.
日本語の概要は準備中です。原文の説明を表示しています。
AAMP (Agent-to-Agent Mail Protocol) — gives this agent an email identity and lets it exchange structured tasks with other AAMP nodes via email. Use this skill to register an identity, check for incoming tasks, and reply with results or help requests.
日本語の概要は準備中です。原文の説明を表示しています。
Generate targeted clarifying questions (2-3 max) that challenge vague requirements and extract missing context. Use after request-analyzer identifies clarification needs, before routing to specialist agents. Helps cto-orchestrator avoid delegating unclear requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing Node.js or TypeScript server code - Express/Fastify/Nest handlers, Next.js server actions and route handlers, child_process, ORM raw queries, prototype pollution, template engines, JWT and outbound HTTP clients
日本語の概要は準備中です。原文の説明を表示しています。
Use when an analiz question needs the human, not the code, to decide - recording it with record_open_questions, judging blocking vs non-blocking, and resuming the report after an answer
日本語の概要は準備中です。原文の説明を表示しています。
Design REST/GraphQL APIs with OpenAPI 3.1, error handling, pagination, rate limiting, webhooks, and idempotency. Use when user asks to design an API, create endpoints, define REST/GraphQL schema, or generate OpenAPI spec. Do NOT use for database schema design, frontend API integration, or non-HTTP protocols (gRPC, WebSocket, MQTT).
日本語の概要は準備中です。原文の説明を表示しています。
Generate, validate, and explain `auth.md` files — the open protocol for AI agent registration. Use when making apps agent-ready, generating Protected Resource Metadata (RFC 9728), validating auth.md files, or implementing agent registration endpoints. Triggers on "auth.md", "agent registration", "agent auth", "make my app agent-ready", "ID-JAG", "identity_assertion", "service_auth", "protected resource metadata", "agentic registration".
日本語の概要は準備中です。原文の説明を表示しています。
Sub-skill de agent-ready-cloudflare: Implement Universal Commerce Protocol (UCP)
日本語の概要は準備中です。原文の説明を表示しています。
Sub-skill de agent-ready-cloudflare: Implement x402 Payment Protocol
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous engineering orchestrator ported from Lauren Tan's pstack (poteto-mode): reads your task, picks one of 23 playbooks (bug fix, feature, refactoring, perf, investigation, prototype, babysit, shipping, autonomous run, orchestrate, and more), routes to bundled procedures (how, why, architect, arena, swarm, interrogate, unslop, technical-writing, show-me-your-work, tdd, and others), and applies 24 engineering principles. Self-contained: no plugin install, no sibling skills required, works with any agent that reads skills.sh-format SKILL.md files. Use whenever a task needs rigor: nontrivial code changes, architecture decisions, debugging, reviews, PRs, long autonomous runs, or "work like poteto", "poteto-mode", "pstack".
日本語の概要は準備中です。原文の説明を表示しています。
Sub-skill: Implement MPP Payment Discovery. Publish OpenAPI with x-payment-info extensions so AI agents discover payable endpoints via Machine Payment Protocol (mpp.dev).
日本語の概要は準備中です。原文の説明を表示しています。
Anti-AI-generic design guidelines. Use when creating UI prototypes, reviewing designs for generic AI patterns, or setting up a project design system.
日本語の概要は準備中です。原文の説明を表示しています。
Show images in terminal using the Kitty image protocol. TRIGGER when show/view images in terminal, display plot results, or after saving any plot or image file to disk.
日本語の概要は準備中です。原文の説明を表示しています。
Show images in terminal using the Kitty image protocol. TRIGGER when show/view images in terminal, display plot results.
日本語の概要は準備中です。原文の説明を表示しています。
Safe testing practices to prevent real-world side-effects. TRIGGER when user asks to "run tests", "test this", "write tests", "debug", "mock", "fixture", "integration test", "unit test", or when testing code that touches network, database, filesystem, or external services. Use BEFORE executing any test that could affect production systems.
日本語の概要は準備中です。原文の説明を表示しています。
ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware, device flashing, Arduino conversion, alarm_control_panel, lock, valve, media_player, microphone, speaker, audio DAC, event entities, datetime entities, Z-Wave proxy, MIPI DSI displays, and DLMS smart meters. Also covers designing new ESPHome-based products: hardware selection, component sourcing, PCB design (KiCad), enclosures, 3D printing, CE/FCC certification, BOM optimization, and manufacturing from prototype to production scale.
日本語の概要は準備中です。原文の説明を表示しています。
The Execution Trader's procedure for turning an approved ticket into one Hyperliquid action and reconciling it - the pre-send checklist, order construction rules, single-send discipline, unknown-result handling and the execution report. Use before and after every send, cancel, modify, leverage change or close.
日本語の概要は準備中です。原文の説明を表示しています。
Create, redesign, repair, validate, preview, and package lightweight standalone HTML deliverables. Use for marketing experiences, product prototypes, infographics, motion narratives, documents, browser tools, dashboards, guided workflows, knowledge interfaces, mini-games, presentations, reusable style and brand systems, and local-model text, vision, image, or code tools that must run without a build chain or hosted service.
日本語の概要は準備中です。原文の説明を表示しています。
Use when optimizing, auditing, or preparing to ship web animations or rendering performance work: frame loops, scroll/viewport reveals, mount/unmount transitions, canvas/WebGL lifecycles, reduced motion, lazy rendering, and deferred off-screen work. Use for jank, per-frame allocations, forced reflows, render loops, animations that do not pause off-screen, content-visibility, requestIdleCallback, analyzing Chrome DevTools performance traces for animation or rendering issues, or choosing between browser-driven CSS/WAAPI, minimal JS, phase, and Motion/GSAP. Use when the user explicitly asks about phase APIs or behavior. Do not use during exploratory animation ideation, prototyping, visual iteration, or trying variants, even when the code already imports phase; wait until the user asks for performance guidance, an audit, production implementation, ship-readiness review, or about phase itself.
日本語の概要は準備中です。原文の説明を表示しています。
Implements behavior changes with a test-first red-green-refactor loop: write one meaningful failing test, watch it fail for the intended reason, make the smallest change, then refactor while green. Use for new behavior, bug fixes, refactors with preserved contracts, and regression tests. Not required for disposable prototypes, generated files, or documentation-only edits.
日本語の概要は準備中です。原文の説明を表示しています。