Use this skill when building, syncing Capacitor, or preparing Android/iOS releases and environment configuration.
日本語の概要は準備中です。原文の説明を表示しています。
7,538 件 ・ 関連度順
概要と使いどころ
Use this skill when building, syncing Capacitor, or preparing Android/iOS releases and environment configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when adding or changing REST API calls, HTTP client config, error handling, uploads/downloads, or network behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when working on camera, gallery, file pick/upload/download, file preview, sharing, or filesystem-backed media. For Preferences keys, use mobile-local-data.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when creating, modifying, or debugging Ionic Vue components, pages, forms, dialogs, or theme/safe-area UI behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Manage SVG icons as framework components using Denji CLI. Use when the user needs to add, remove, list, export, import, or manage SVG icons in React, Preact, Solid, Qwik, Vue, or Svelte projects. Triggers include requests to "add an icon", "set up icons", "manage SVG icons", "remove an icon", "list icons", "export icons", "import icons", "dry-run icon add", or any task involving Iconify icons as framework components.
日本語の概要は準備中です。原文の説明を表示しています。
TanStack Pacer best practices for execution control in React — debouncing, throttling, rate limiting, queuing, and batching. Use when implementing search inputs, scroll handlers, API rate limits, task queues, bulk operations, or any scenario requiring controlled execution timing with reactive state.
日本語の概要は準備中です。原文の説明を表示しています。
Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
日本語の概要は準備中です。原文の説明を表示しています。
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
日本語の概要は準備中です。原文の説明を表示しています。
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
日本語の概要は準備中です。原文の説明を表示しています。
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
日本語の概要は準備中です。原文の説明を表示しています。
How to upgrade `alchemy` and the `effect` constellation across this repo and keep them consistent for consumers: which packages pin what, why `effect` and every `@effect/*` companion move as one set, what breaks in a typical upgrade, and how to verify a standalone `npm install` still resolves a single `effect`. Use when asked to upgrade or bump alchemy or effect, when a deploy dies inside an alchemy provider with a `TypeError` naming a missing combinator, when `check:npm-effect-resolution` fails, or when deciding whether the alchemy patch is still needed.
日本語の概要は準備中です。原文の説明を表示しています。
Structured build workflow: branch, delegate to coding agent, test, screenshot, and commit. Triggers on: "$devprocess", "build this properly", "use the coding agent workflow", or any feature/refactor/infrastructure change that is too large for a direct edit. NOT for: one-line fixes, doc edits, prompt tweaks, or simple config changes — do those directly.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-source research synthesizer. Takes a question, runs 3-5 parallel web searches with varied phrasings, deduplicates, and returns a cited, concise answer. For Hebrew questions, searches in both Hebrew and English. Output is always under ~400 words.
日本語の概要は準備中です。原文の説明を表示しています。
OpenClaw API gateway proxy for authenticated SaaS calls (100+ services in references/SERVICES.md). Use ONLY when making an HTTP request to a third-party service that requires the gateway's stored credentials. NOT for direct API calls with bearer tokens already in scope, NOT for monday.com (use monday-for-agents), NOT for WhatsApp (use heleni-whatsapp). Triggers: "call the X API", "fetch from <service>", "send to Slack via gateway", "use the gateway for".
日本語の概要は準備中です。原文の説明を表示しています。
Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Cypress Deep — cypress end-to-end testing management and analysis. Covers test execution monitoring, dashboard integration, screenshot and video analysis, test report parsing, flaky test detection, and configuration auditing. Use when investigating test failures, reviewing Cypress Cloud results, or managing Cypress test suites.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Cdn — azure CDN management covering profiles, endpoints, custom domains, caching rules, origin groups, and performance analytics. Supports Microsoft, Verizon, and Akamai CDN providers within Azure. Use when managing Azure CDN endpoints, analyzing cache performance, configuring delivery rules, or troubleshooting content delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Allure Testops — allure TestOps test management and analytics platform monitoring. Covers project dashboards, launch tracking, test case management, defect clustering, environment matrix analysis, and CI/CD integration review. Use when managing test cases in Allure TestOps, reviewing launch results, analyzing flaky tests, or tracking quality trends.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Allma — allma incident management, collaboration workflows, post-incident learning, and channel orchestration. Covers incident creation via Slack, timeline tracking, stakeholder communication, automated workflows, and retrospective analysis. Use when managing active incidents, reviewing post-incident learnings, or analyzing incident patterns in Allma.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Guardduty — aWS GuardDuty finding analysis, detector management, suppression rule review, and member account oversight. Covers threat detection summary, finding severity distribution, finding type breakdown, trusted IP lists, and organization-wide security posture.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Rightsizing — analyze EC2, RDS, EBS, and Lambda resource utilization to identify right-sizing opportunities. Uses CloudWatch metrics with anti-hallucination rules for burstable instances, memory metrics, peak vs average analysis, and estimated monthly savings calculations.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
日本語の概要は準備中です。原文の説明を表示しています。
Validate at every layer data passes through to make bugs impossible
日本語の概要は準備中です。原文の説明を表示しています。