1,190 件 ・ 関連度順
概要と使いどころ
Use when adding or changing REST endpoints or the OpenAPI contract — deriving endpoints from the Lean commands and views, writing documents/codebase/openapi.yaml first, then regenerating the backend controller interfaces and the frontend client.
日本語の概要は準備中です。原文の説明を表示しています。
フロントエンド実装時に使用。コーディング規約準拠。コンポーネント設計。
Checks Tailwind utility class hygiene at the syntax level: arbitrary-value overuse that bypasses the theme scale, conflicting/duplicate utilities on one element, and hardcoded arbitrary colors that should use design tokens.
日本語の概要は準備中です。原文の説明を表示しています。
Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.
日本語の概要は準備中です。原文の説明を表示しています。
Detects route data fetched in useEffect instead of loaders, server/client API leaks across loader boundaries, and missing HydrateFallback in React Router v7 framework mode.
日本語の概要は準備中です。原文の説明を表示しています。
Checks React Router v7 action conventions: validation errors returned as data with 4xx status (not thrown), redirect on success, and 3-branch ErrorBoundary handling.
日本語の概要は準備中です。原文の説明を表示しています。
Schedules reactive frontend states cleanly using entangle directives in PHP and JS.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other frontends.
日本語の概要は準備中です。原文の説明を表示しています。
Creates or adds Convex to an app. Use for new Convex projects, npm create convex@latest, frontend setup, env vars, or the first npx convex dev run.
日本語の概要は準備中です。原文の説明を表示しています。
Construye o actualiza el corpus y el perfil técnico de un reviewer real a partir de sus comentarios en PRs de GitHub. Usar cuando se pida "crear el agente reviewer de X", "armar el perfil de X", "actualizar el corpus de X", "agregar el frontend al perfil de X", o "/generate-github-coder-profile <dir> <Nombre> <login>".
日本語の概要は準備中です。原文の説明を表示しています。
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.
日本語の概要は準備中です。原文の説明を表示しています。
Build premium scroll-driven web pages and product showcases inspired by high-end app, hardware, and product interaction patterns. Use for Raycast-like, Apple-like, NVIDIA-like, RTX/GPU, SaaS, AI browser, parallax, sticky scroll, pinned reveal, Three.js GLB model, Web Audio sound effect, responsive accessibility, and performance-safe frontend requests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to execute an existing pwdev-feat action plan — 'executar o plano user-crud', 'exec latest', 'rodar o plano', 'retomar a execução'. Dispatches the executor (subagent when the runtime has one, inline otherwise) in IMPLEMENT or REPORT mode, handles NEEDS_ADVICE with the advisor, and supports --resume. Do NOT use to create plans (feat-feature, feat-backend, feat-frontend, feat-test, feat-review) or for tasks without a plan (feat-quick).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a backend-only action plan — API endpoints, services, models, migrations, jobs and their tests — 'plano de backend para o endpoint X', 'plan the orders API'. Writes .planning/feat/features/{slug}/plan.md with the PWDEVIA method. Do NOT use for UI work (feat-frontend), full features spanning backend and UI (feat-feature), writing code (feat-exec) or quick 1–3 file fixes (feat-quick).
日本語の概要は準備中です。原文の説明を表示しています。
Build reusable, composable, and maintainable React/Vue/Angular components following established design patterns like compound components, render props, custom hooks, and HOCs. Use when creating component libraries, implementing component composition, building reusable UI elements, designing prop APIs, managing component state patterns, implementing controlled vs uncontrolled components, creating compound components, using render props or children as functions, building custom hooks, or establishing component architecture standards.
日本語の概要は準備中です。原文の説明を表示しています。
[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.
日本語の概要は準備中です。原文の説明を表示しています。
Route visual design, frontend art direction, motion, image generation, branding, and redesign work to focused design skills. Use when the task is primarily about how an interface or brand should look and feel.
日本語の概要は準備中です。原文の説明を表示しています。
Iterate on tasks using debug instrumentation and browser tools. Use when you need to debug web applications, verify frontend behavior, or fix issues without asking the user to manually test.
日本語の概要は準備中です。原文の説明を表示しています。
Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.
日本語の概要は準備中です。原文の説明を表示しています。
Test and debug browser UIs using Chrome DevTools MCP — DOM inspection, console errors, network requests, performance traces, and visual verification. Load when building or debugging anything that renders in a browser, verifying a UI fix, profiling Core Web Vitals in a real page, or the user asks for browser testing with DevTools. Requires chrome-devtools MCP configured. Not for backend-only or CLI work. Pairs with frontend-design and performance-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a code change end-to-end in the current worktree: identify what changed, run the relevant tests, get the app running, drive a browser over the affected areas, and report a verdict with screenshots. Generic across project types (Laravel/Herd, Node/bun, frontend, CLI, library). Use when the user wants to verify/QA/smoke-test a change, check that a PR or branch works, validate uncommitted work, or says "/flow", "verify this change", "does this PR work", "test and click through this". Optional target: PR number/URL, branch/ref, or worktree path; default is the current working changes.
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
日本語の概要は準備中です。原文の説明を表示しています。