メニュー
Runs and scopes automated tests for this Turborepo (unit, package filters, Medusa stress, E2E, release gate). Use when the user asks to run tests, verify CI locally, debug failing tests, or choose the right test command for a changed package.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Plug-and-play orchestration skill. User states a goal in natural language; the model runs commands/agent-hub.md (dispatcher), classifies work via agent/operating-model.md, then opens only the matching command or architecture doc (map, architect, memory, recovery, verify, next-pass, or one NN-layer). Layered docs for intent, policy, context, planning, routing, delegation, execution, MCP/tool boundaries, verification, memory, recovery, observability, human gates, release. Use for repo orchestration reviews, boundary work, memory/recovery design, permission-sensitive refactors.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
CO-STAR UI Creator for React/Next.js: structured prompting to build or integrate UI (components, pages, design systems) or to create custom CO-STAR prompts. Use when the user wants to add hero sections, dashboards, design tokens, shadcn/Magic UI/Aceternity integration, Newsprint design system, or to draft their own CO-STAR prompt (Context, Objective, Style, Tone, Audience, Response). Always run discovery questions first, then plan, then implementation.
Context Engineering patterns for AI development and prompting. Use when the user wants to reduce tokens, avoid lost-in-the-middle, and structure prompts using Skeleton-of-Thought, token-efficient diff updates, XML tagging, symbolic variables, negative constraints, or LLMBundle-style context packaging.
Object-oriented design and Core Engineering principles for AI agents and developers. Use when the user asks about OOP (four pillars), SOLID, encapsulation, abstraction, inheritance, polymorphism, Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion, composition over inheritance, DRY, KISS, YAGNI, Law of Demeter, or association vs aggregation vs composition. Includes how each principle looks and example code.
Apply the "Family Values" design philosophy to every UI you build. Use this skill whenever creating frontends, components, apps, landing pages, dashboards, or any user-facing interface. Enforces three core principles (Simplicity, gradual revelation; Fluidity, seamless transitions; Delight, selective emphasis) so that every output feels crafted, intentional, and alive. Prevents generic, static, lifeless UI. Works alongside other skills like frontend-design, web-animation-design, and more.
| name | test |
| description | Runs and scopes automated tests for this Turborepo (unit, package filters, Medusa stress, E2E, release gate). Use when the user asks to run tests, verify CI locally, debug failing tests, or choose the right test command for a changed package. |
| Goal | Command |
|---|---|
| Full unit + package test suite (long) | pnpm test |
| Stress / gate without full E2E details | pnpm stress-test:quick |
| Full stress pipeline | pnpm stress-test |
| Playwright E2E | pnpm test:e2e (UI: pnpm test:e2e:ui) |
| Pre-deploy style check | pnpm predeploy |
pnpm test runs packages in a fixed order (platform-data, UI build, sdk, validation, rate-limits, api, database, admin, storefront, Medusa unit + Medusa stress). Prefer scoped runs when the user only touched one area.
Use pnpm --filter <package-name> test (or the script defined in that package, e.g. test:unit, test:stress).
Common filters (from workspace package.json names):
@apparel-commerce/platform-data@apparel-commerce/sdk@apparel-commerce/validation@apparel-commerce/rate-limits@apparel-commerce/api@apparel-commerce/database@apparel-commerce/admin@apparel-commerce/storefrontmedusa (see apps/medusa/package.json for test:unit, test:stress)Example: only SDK tests:
pnpm --filter @apparel-commerce/sdk test
E2E often needs services and seed data. From root:
pnpm e2e:prep (Medusa prep + staff ensure)pnpm test:e2e or targeted specs via node stress-test/scripts/run-e2e.js <path-or-pattern>Read playwright.config.ts and stress-test/scripts/run-e2e.js when the user needs custom projects or grep.
pnpm test).For stress-test flags and dogfood flows, see .cursor/commands/stress.md if present in the repo.