メニュー
Deploy applications to AWS. Triggers on phrases like: deploy to AWS, host on AWS, run this on AWS, AWS architecture, estimate AWS cost, generate infrastructure. Analyzes any codebase and deploys to optimal AWS services.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Defines architectural standards, constraints, and best practices for writing high-quality unit tests using Jest in the e-micro-commerce backend (NestJS 11+ / Node.js 24+ / TypeScript). Use this skill whenever implementing or modifying unit tests for services, use cases, domain entities, value objects, guards, pipes, interceptors, utility functions, shared libraries, or Jest test utilities inside apps/backend/src. Do NOT use for integration tests (use supertest-integration-tests skill), E2E tests (use playwright-e2e-tests skill), or frontend component tests.
Defines architecture, standards, patterns, and best practices for writing backend integration tests for the e-micro-commerce NestJS application using Jest, Supertest, and a real PostgreSQL database via Prisma 7+. Use whenever implementing or modifying REST API integration tests, HTTP endpoint validation, authentication (Clerk JWT), authorization (RBAC: ADMIN / CUSTOMER), database lifecycle, or integration test helpers inside apps/backend. Do NOT use for unit tests — use the jest-unit-tests skill instead. Do NOT use for Playwright E2E browser tests — use the playwright-e2e-tests skill instead.
Review Dify frontend code for correctness, accessibility, component design, dify-ui usage, data/query boundaries, performance, and tests. Trigger for `.tsx`, `.ts`, `.js`, UI, React, Next.js, pending-change, or focused frontend review requests.
Defines architectural standards, design patterns, and best practices for building scalable, maintainable, and reliable end-to-end tests using Playwright for the e-micro-commerce frontend (Next.js 16+ / App Router / TypeScript / Vanilla CSS). Use whenever implementing or modifying Playwright tests, Page Objects, Component Objects, fixtures, or supporting test infrastructure inside apps/frontend. Do NOT use for unit tests or backend integration tests.
Ensures every implementation meets mandatory quality criteria before being considered complete in the e-micro-commerce monorepo (Next.js 16+ frontend / NestJS 11+ backend / Prisma 7+ / PostgreSQL 15+). Trigger this skill when: implementing a new feature, fixing a bug, refactoring existing code, modifying business logic, or when the user asks to "finish", "commit", "open a PR", "review", or "complete" any task. This skill is MANDATORY — never declare a task done without executing the full pipeline described here.
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
| name | deploy |
| description | Deploy applications to AWS. Triggers on phrases like: deploy to AWS, host on AWS, run this on AWS, AWS architecture, estimate AWS cost, generate infrastructure. Analyzes any codebase and deploys to optimal AWS services. |
Take any application and deploy it to AWS with minimal user decisions.
Minimize cognitive burden. User has code, wants it on AWS. Pick the most straightforward services. Don't ask questions with obvious answers.
See defaults.md for the complete service selection matrix.
Core principle: Default to dev-sized (cost-conscious: small instance sizes, minimal redundancy, and non-HA/single-AZ defaults) unless user says "production-ready".
Consult for architecture decisions. Use when choosing between AWS services or validating that a service fits the use case. Helps answer "what's the right AWS service for X?"
Key topics: general for architecture, amplify_docs for static sites/SPAs,
cdk_docs and cdk_constructs for IaC patterns.
Get cost estimates. Always present costs before generating IaC so user can adjust before committing. See cost-estimation.md for query patterns.
Consult for IaC best practices. Use when writing CDK/CloudFormation/Terraform to ensure patterns follow AWS recommendations.
