aws-dynamodb

Teach single-table DynamoDB design with PK/SK and GSI patterns.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill aws-dynamodb-aberrantcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-dynamodb
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/aws-dynamodb
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill aws-dynamodb-aberrantcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DynamoDB design can be challenging when aiming for scalable, fast access patterns. This skill guides you through a single-table design approach with generic PK/SK keys and well-chosen Global Secondary Indexes to support diverse entities and queries.

Core Features & Use Cases

  • Single-table design strategy that stores multiple entity types (e.g., User, Order, OrderItem) in one table with PK/SK and optional GSIs for efficient access.
  • Practical access patterns and transaction workflows, including CRUD operations, queries, and GSIs for cross-entity access.
  • SDK v3 TypeScript and Python samples demonstrating common data modeling practices and robust error handling.

Quick Start

Install and configure a DynamoDB single-table design blueprint and implement a starter TypeScript or Python client to run common queries.

Frequently Asked Questions about aws-dynamodb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is DynamoDB single-table design and when do I need it?

DynamoDB single-table design stores multiple entity types in one table using generic PK/SK keys and GSIs to support diverse queries. You need it when building scalable apps requiring predictable queries and efficient data modeling.

How do I design Global Secondary Indexes for cross-entity access in DynamoDB?

Design Global Secondary Indexes by mapping generic PK/SK keys to support cross-entity queries. This single-table design approach allows efficient data access patterns across different entity types stored within the same DynamoDB table.

Can I use TypeScript and Python SDK v3 for DynamoDB CRUD workflows?

Yes, you can use TypeScript and Python SDK v3 for DynamoDB CRUD workflows. The single-table design approach provides code samples demonstrating common data modeling practices, queries, and robust error handling for both languages.

What's the best way to model multiple entities in a DynamoDB table?

The best way to model multiple entities is single-table design, storing types like User, Order, and OrderItem together. Using generic PK/SK keys and optional GSIs enables efficient access patterns and transaction workflows.

Does single-table design in DynamoDB support transaction workflows?

Yes, single-table design supports transaction workflows in DynamoDB. It provides practical access patterns for CRUD operations and queries, ensuring robust data modeling and consistent state transitions across multiple entities.

Why does my DynamoDB data modeling struggle with scalable access patterns?

DynamoDB data modeling struggles with scalable access when lacking single-table design and well-chosen GSIs. Implementing generic PK/SK keys resolves this challenge by enabling predictable queries and efficient cross-entity data access.