creating-subpackages

Automate creation and standardization of AWS service subpackages in a monorepo.

6|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/crmagz/cdk-constructs-library --skill creating-subpackages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-subpackages
Source: https://github.com/crmagz/cdk-constructs-library/tree/main/.claude/skills/creating-subpackages
Command: npx skills add https://github.com/crmagz/cdk-constructs-library --skill creating-subpackages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patterns and standards to ensure consistent creation of new AWS service subpackages in the monorepo, reducing duplication and misconfiguration.

Core Features & Use Cases

  • Establishes a standard package layout for new services (e.g., packages/<service>/ with package.json, tsconfig.json, src/, test/, docs/).
  • Provides guidance on exports, typings, tests, and documentation to align with root project conventions.
  • Facilitates scalable onboarding for teams when adding services like Lambda, DynamoDB, or Step Functions.

Quick Start

Follow this guide whenever you add a new service package to ensure a consistent structure and compliance with monorepo standards.

Frequently Asked Questions about creating-subpackages

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

FAQPage Schema
How do I standardize AWS service subpackages in a TypeScript monorepo?

Establish a standard package layout under packages/<service>/ containing package.json, tsconfig.json, src, test, and docs to ensure new AWS service packages align with root monorepo conventions and reduce misconfiguration.

What is the correct package structure for adding Lambda or DynamoDB services to a monorepo?

The correct package structure for adding Lambda or DynamoDB services is packages/<service>/ with required package.json, tsconfig.json, src/, test/, and docs/ directories. This layout ensures scalable onboarding and consistent exports across the monorepo.

How do I configure typings and exports for new CDK subpackages?

Configure typings and exports for new CDK subpackages by following established root project conventions for TypeScript typings and export patterns. This ensures consistent module resolution and automated validation via the central checklist.

Does this monorepo subpackage standardization work with AWS Step Functions and Lambda?

Yes, subpackage standardization works with AWS Step Functions, Lambda, and DynamoDB. It applies a standardized directory structure, exports, tests, and documentation whenever you add new service packages to the monorepo.

What's the best way to validate new AWS subpackages against monorepo standards?

The best way to validate new AWS subpackages is through the central checklist, which automates validation of directory structure, typings, exports, and documentation to ensure compliance with root project conventions before merging.