amazon-web-services
Core AWS services for application developers. Covers S3 (storage, presigned URLs, lifecycle), Lambda (functions, layers, cold starts), IAM (roles, policies, least privilege), DynamoDB (single-table design, GSI/LSI, streams), SQS/SNS (queues, topics, fan-out), CloudFront (CDN, caching), RDS/Aurora (Postgres/MySQL, connection pooling), ECR/ECS/Fargate (containers), Route 53 (DNS), Secrets Manager, and CDK v2 (TypeScript IaC, constructs, stacks, testing). Use when building AWS infrastructure, writing CDK stacks, configuring IAM policies, designing DynamoDB tables, setting up Lambda functions, creating S3 presigned URLs, deploying containers on ECS/Fargate, or configuring CloudFront distributions.
What this skill does
# Amazon Web Services ## Overview Amazon Web Services (AWS) provides cloud computing services for building scalable applications. The AWS SDK for JavaScript v3 uses modular packages (`@aws-sdk/client-*`) with first-class TypeScript support. AWS CDK v2 defines infrastructure as code using TypeScript constructs that synthesize to CloudFormation templates. **When to use:** Building cloud-native applications, serverless architectures, container deployments, managed databases, CDN distribution, event-driven systems, or infrastructure as code. **When NOT to use:** Simple static sites (consider Vercel/Netlify), local-only development tools, projects with no cloud deployment requirement. ## Quick Reference | Service / Pattern | API / Construct | Key Points | | ----------------- | ---------------------------------------------------------- | ------------------------------------------------------------ | | S3 upload | `PutObjectCommand` | Modular import from `@aws-sdk/client-s3` | | S3 presigned URL | `getSignedUrl()` | From `@aws-sdk/s3-request-presigner`, max 7 days | | Lambda function | `new lambda.Function()` | CDK L2 construct, set `memorySize` and `timeout` | | Lambda layers | `new lambda.LayerVersion()` | Share code/deps across functions | | IAM policy | `new iam.PolicyStatement()` | Always use least privilege, avoid `*` resources | | DynamoDB table | `new dynamodb.Table()` | Single-table design, PAY_PER_REQUEST for variable loads | | DynamoDB GSI | `table.addGlobalSecondaryIndex()` | Separate throughput, eventual consistency | | SQS queue | `new sqs.Queue()` | DLQ for failed messages, long polling with `WaitTimeSeconds` | | SNS topic | `new sns.Topic()` | Fan-out to SQS, Lambda, HTTP endpoints | | CloudFront | `new cloudfront.Distribution()` | OAC for S3 origins, cache policies | | RDS/Aurora | `new rds.DatabaseCluster()` | Use RDS Proxy for connection pooling | | ECS Fargate | `new ecs_patterns.ApplicationLoadBalancedFargateService()` | Higher-level pattern construct | | Route 53 | `new route53.ARecord()` | Alias records for AWS resources | | Secrets Manager | `secretsmanager.Secret.fromSecretNameV2()` | Automatic rotation, never hardcode secrets | | CDK stack | `new cdk.Stack(app, 'Id')` | One stack per deployment unit | | CDK testing | `Template.fromStack(stack)` | Fine-grained assertions and snapshot tests | ## Common Mistakes | Mistake | Correct Pattern | | --------------------------------------------------- | --------------------------------------------------------------- | | Using AWS SDK v2 (`aws-sdk`) | Use modular v3 (`@aws-sdk/client-*`) for smaller bundles | | IAM `Action: "*"` or `Resource: "*"` | Scope to specific actions and resource ARNs | | No DLQ on SQS queues | Always attach a dead-letter queue for failed messages | | DynamoDB scan for queries | Design access patterns first, use Query with GSI/LSI | | Hardcoding secrets in code or env vars | Use Secrets Manager or SSM Parameter Store | | Lambda bundling `node_modules` without tree-shaking | Use `NodejsFunction` with esbuild bundling | | Missing `RemovalPolicy` on stateful resources | Set `RemovalPolicy.RETAIN` for production databases and buckets | | Creating one Lambda per CRUD operation | Group related operations, use event routing | | No connection pooling for RDS | Use RDS Proxy or limit `max_connections` per Lambda | | CloudFront without cache policy | Define explicit `CachePolicy` to control TTL and headers | | CDK testing only with snapshots | Combine fine-grained assertions with snapshot tests | | Presigned URL without content-type | Include `ContentType` in `PutObjectCommand` for uploads | ## Delegation - **Infrastructure patterns**: Use `Explore` agent for AWS architecture discovery - **Security review**: Use `Task` agent for IAM policy auditing - **Cost optimization**: Use `Task` agent for resource right-sizing > If the `docker` skill is available, delegate container build patterns and Dockerfile optimization to it. > If the `github-actions` skill is available, delegate CI/CD pipeline patterns for AWS deployments to it. > If the `typescript-patterns` skill is available, delegate TypeScript strict mode and type patterns used in CDK code to it. > If the `application-security` skill is available, delegate AWS security best practices and threat modeling to it. ## References - [S3 storage, presigned URLs, and lifecycle policies](references/s3-storage.md) - [Lambda functions, layers, cold starts, and event sources](references/lambda-functions.md) - [IAM roles, policies, and least-privilege patterns](references/iam-security.md) - [DynamoDB single-table design, GSI/LSI, and streams](references/dynamodb.md) - [SQS queues, SNS topics, and fan-out messaging](references/messaging-sqs-sns.md) - [ECS/Fargate container deployment and ECR](references/containers-ecs-fargate.md) - [CloudFront CDN, Route 53 DNS, and networking](references/networking-cloudfront-route53.md) - [CDK v2 infrastructure as code, constructs, stacks, and testing](references/cdk-infrastructure.md)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.