1.8万 件 ・ 関連度順
概要と使いどころ
Review FriendlyBet quality, regression risk, test plans, release readiness, version bump discipline, scoring/locking correctness, provider fallback behavior, and dirty-worktree safety. Use before shipping app code, scoring changes, migrations, sports integrations, copy updates, PWA cache changes, or any risky user-facing flow.
日本語の概要は準備中です。原文の説明を表示しています。
Document templates for all pipeline output documents — specs, indexes, reports, and strategy docs. Use when any workflow needs to produce a structured document.
日本語の概要は準備中です。原文の説明を表示しています。
Scoring rubrics for all 5 pipeline layers (Vision, Architecture, IA, BE, FE). Use when auditing specs, running self-checks, or remediating ambiguity gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Semantically merge upstream kit changes while preserving project-specific values and recording sync state
日本語の概要は準備中です。原文の説明を表示しています。
Author and validate BE spec files, update indexes/tracker, run deepening and ambiguity gates, and enforce allowed next-step transitions
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the confirmed design direction to all visual surfaces. This skill now bridges the pipeline's placeholder system with the `impeccable` skill's PRODUCT.md and DESIGN.md files. If `{{DESIGN_DIRECTION}}` still appears as a literal placeholder, run `/impeccable teach` to establish design context.
日本語の概要は準備中です。原文の説明を表示しています。
Design direction interview methodology — SUPERSEDED. The `impeccable` skill's `/impeccable teach` command now handles design direction discovery with a more comprehensive, multi-round interview that writes PRODUCT.md and DESIGN.md. This file is kept for pipeline backward compatibility — all new design work should use `/impeccable teach` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Create decomposition directory structure, IA shard skeletons, and all required layer indexes from approved decomposition plan
日本語の概要は準備中です。原文の説明を表示しています。
Leverage concurrent terminal background processes to debug multiple independent failures simultaneously using ACH methodology. Use when you have 2+ failures across different subsystems.
日本語の概要は準備中です。原文の説明を表示しています。
Utility — fill the surface stack map in tech-stack.md and provision skills using intelligent resolution. Called by pipeline commands when tech stack info changes.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic methodology for verifying that IA, BE, and FE specification layers are mutually consistent. Covers coverage matrices, field mapping checks, error code propagation, access control consistency, and data contract drift detection.
日本語の概要は準備中です。原文の説明を表示しています。
Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new Gradle module in any Kotlin Android project. Walks the user through choosing one of three module types — library module (`com.android.library`), feature module (regular Android library that hosts a feature/UI, install-time only), or dynamic feature module (`com.android.dynamic-feature`, on-demand/conditional/instant delivery). Use whenever the user wants to add a module, modularize code, extract a util/data/ui layer, create a new feature, set up Play Feature Delivery, or asks "should this be a library or feature module?". Discovers the project's existing conventions (plugin aliases, namespaces, sibling modules, version catalog) instead of hardcoding any. Pushes back on bad combos (e.g. utility code in a dynamic feature). Stops at scaffolding; app-level wiring is out of scope.
日本語の概要は準備中です。原文の説明を表示しています。
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 for all verification: unit, component, E2E, native, and release checks. Required alongside mobile-core for every implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when adding or changing REST API calls, HTTP client config, error handling, uploads/downloads, or network behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Gang of Four design patterns to solve architectural problems in TypeScript. Use when refactoring code architecture, implementing extensible systems, decoupling components, or following SOLID principles. Covers all 22 GoF patterns: Creational (Factory Method, Abstract Factory, Builder, Prototype, Singleton), Structural (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy), and Behavioral (Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor).
日本語の概要は準備中です。原文の説明を表示しています。
Build React animations with Motion (Framer Motion) - gestures (drag, hover, tap), scroll effects, spring physics, layout animations, SVG. Bundle: 2.3 KB (mini) to 34 KB (full). Use when: drag-and-drop, scroll animations, modals, carousels, parallax. Troubleshoot: AnimatePresence exit, list performance, Tailwind conflicts, Next.js "use client".
日本語の概要は準備中です。原文の説明を表示しています。
Use Kanpeki component library in React projects. Activate when user wants to add, use, customize, or compose accessible UI components from Kanpeki (@kanpeki/*). Covers installation, component patterns, forms, theming, and dark mode with React Aria Components + Tailwind CSS 4.1 + CVA.
日本語の概要は準備中です。原文の説明を表示しています。
Bu template'in konvansiyonlarina gore degisen dosyalari denetler — Cubit+Freezed state kullanimi, servis/locator yerlesimi, view tipi secimi, dort-durum ele alinisi, tasarim token'lari (renk/tipografi/padding/radius), LocaleKeys, TypedGoRoute, zorunlu <feature>.md ve very_good_analysis kurallari. Kullanici "degisiklikleri incele", "bu PR'i review et", "projeye uygun mu", "mimari kontrol", "review my changes" dediginde kullan.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Cuts the next minor release of Prisma Composer: bumps the root package.json version, propagates it to every workspace package in lockstep, and opens a PR titled "chore(release): v<next-version>". When a maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".
日本語の概要は準備中です。原文の説明を表示しています。
Use when deploying or managing an app that uses Prisma Composer (`@prisma/composer`): wiring its services and Modules, running it locally, testing composed services, or standing up / tearing down an environment. Triggers on "prisma composer", "@prisma/composer", "prisma app", `prisma deploy`, `prisma dev`, `compute()`, `module()`, `contract()`, `service.load()`, `mockService`, `bootstrapService`.
日本語の概要は準備中です。原文の説明を表示しています。