
Dynamodb Toolbox Patterns
Apply DynamoDB Toolbox v2 table, entity, schema, and command patterns when modeling and querying DynamoDB in TypeScript/JavaScript backends.
Overview
DynamoDB Toolbox Patterns is an agent skill for the Build phase that surfaces official DynamoDB Toolbox v2 patterns for tables, entities, schemas, and queries.
Install
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill dynamodb-toolbox-patternsWhat is this skill?
- Curated Context7 and official docs map for DynamoDB-Toolbox v2
- Table .build() workflow plus KV store and scans-and-queries examples
- Schema usage: item, string, number, and parse/actions with key, default, required, transform, link
- Dedicated links for Query, Scan, and GetItemCommand operations
- Aligns solo builders to single-toolbox patterns instead of raw AWS SDK sprawl
Adoption & trust: 875 installs on skills.sh; 271 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are modeling DynamoDB with Toolbox v2 but keep reaching for wrong docs or mixing low-level SDK calls with entity schemas.
Who is it for?
Solo builders on serverless or Node backends who standardize on dynamodb-toolbox for typed items and actions.
Skip if: Teams on SQL-only stacks, one-off DynamoDB console edits, or full Terraform/CDK provisioning without application code.
When should I use this skill?
When implementing or refactoring DynamoDB access with DynamoDB Toolbox v2 tables, entities, schemas, or commands.
What do I get? / Deliverables
You implement Table.build(), entity schemas, and query/scan/get commands following linked v2 examples and schema parse rules.
- Toolbox-aligned table and entity definitions
- Query/scan/get implementations per v2 docs
Recommended Skills
Journey fit
How it compares
Pattern-and-docs skill for Toolbox v2—not a generic DynamoDB console assistant or ORM migration generator.
Common Questions / FAQ
Who is dynamodb-toolbox-patterns for?
Indie backend developers using DynamoDB Toolbox v2 who want agents to cite the right table, schema, and command docs while coding.
When should I use dynamodb-toolbox-patterns?
During Build backend work when defining entities, query keys, scans, or GetItem flows for a new or refactored DynamoDB data layer.
Is dynamodb-toolbox-patterns safe to install?
It is documentation curation without shell side effects; still review Security Audits on this page and validate AWS IAM least privilege separately.
SKILL.md
READMESKILL.md - Dynamodb Toolbox Patterns
# Context7 References: DynamoDB-Toolbox v2 Curated documentation links retrieved via Context7 for this skill. ## Core - Context7 LLM reference: https://context7.com/dynamodb-toolbox/dynamodb-toolbox/llms.txt - Getting started overview: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/1-getting-started/1-overview/index.md - KV store example (`.build()` workflow): https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/1-getting-started/4-examples/1-kv-store.md ## Table and Entity usage - Table `.build()` usage: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/2-tables/1-usage/index.md - Query action docs: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/2-tables/2-actions/2-query/index.md - Scan action docs: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/2-tables/2-actions/1-scan/index.md - Scans and queries example: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/1-getting-started/4-examples/2-scans-and-queries.md ## Schema modeling - Schema usage (`item`, `string`, `number`, etc.): https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/4-schemas/1-usage/index.md - Schema parse/actions and advanced modifiers (`key`, `default`, `required`, `transform`, `link`): https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/4-schemas/17-actions/1-parse.md ## Commands and operations - `GetItemCommand` docs: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/3-entities/4-actions/1-get-item/index.md - Batch write table action: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/2-tables/2-actions/7-batch-write/index.md - Transaction patterns: https://github.com/dynamodb-toolbox/dynamodb-toolbox/blob/main/docs/docs/3-entities/4-actions/11-transactions/index.md ## Single-table design - Access patterns and computed keys example (Context7): https://context7.com/dynamodb-toolbox/dynamodb-toolbox/llms.txt --- name: dynamodb-toolbox-patterns description: Provides TypeScript patterns for DynamoDB-Toolbox v2 including schema/table/entity modeling, .build() command workflow, query/scan access patterns, batch and transaction operations, and single-table design with computed keys. Use when implementing type-safe DynamoDB access layers with DynamoDB-Toolbox v2 in TypeScript services or serverless applications. allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- # DynamoDB-Toolbox v2 Patterns (TypeScript) ## Overview This skill provides practical TypeScript patterns for using DynamoDB-Toolbox v2 with AWS SDK v3 DocumentClient. It focuses on type-safe schema modeling, `.build()` command usage, and production-ready single-table design. ## When to Use - Defining DynamoDB tables and entities with strict TypeScript inference - Modeling schemas with `item`, `string`, `number`, `list`, `set`, `map`, and `record` - Implementing `GetItem`, `PutItem`, `UpdateItem`, `DeleteItem` via `.build()` - Building query and scan access paths with primary keys and GSIs - Handling batch and transactional operations - Designing single-table systems with computed keys and entity patterns ## Instructions 1. **Start from access patterns**: identify read/write queries first, then design keys. 2. **Create table + entity boundaries**: one table, multiple entities if using single-table design. 3. **Define schemas with constraints**: apply `.key()`, `.required()`, `.default()`, `.transform()`, `.link()`. 4. **Use `.build()` commands everywhere**: avoid ad-hoc command construction for consistency and type safety. 5. **Add query/index coverage**: validate GSI/LSI paths for each required access pattern. 6. **Use batch/transactions intentionally**: batch for throughput, transactions for atomicity. 7. **Keep items evolvable**: use optional fields, defaults, and derived attributes for schema evolution. ## Examples ### Install and Setup ```bash npm in