package-scaffolding

Scaffold new packages in the Fluid Framework monorepo with required configuration files.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/tylerbutler/repo-overlays --skill package-scaffolding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-scaffolding
Source: https://github.com/tylerbutler/repo-overlays/tree/main/tylerbutler/FluidFramework/package-scaffolding/.claude/skills/package-scaffolding
Command: npx skills add https://github.com/tylerbutler/repo-overlays --skill package-scaffolding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new packages within the Fluid Framework monorepo, ensuring adherence to all established conventions and best practices.

Core Features & Use Cases

  • Monorepo Package Creation: Generates a new package directory with the correct structure and boilerplate files.
  • Convention Enforcement: Automatically includes necessary configuration files for TypeScript, ESLint, API Extractor, and testing.
  • Use Case: When starting a new Distributed Data Structure (DDS) or a shared utility library, use this Skill to quickly set up a compliant package.

Quick Start

Use the package-scaffolding skill to create a new package named 'my-new-dds' in the 'packages/dds/' directory.

Frequently Asked Questions about package-scaffolding

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

FAQPage Schema
How do I create a new package in a monorepo with compliant TypeScript and ESLint configurations?

To create a compliant package in a monorepo, you need to generate the correct directory structure and boilerplate files that enforce standards for TypeScript, ESLint, API Extractor, and testing setups.

What is the best way to scaffold a Fluid Framework DDS or shared library?

Scaffolding a Fluid Framework DDS or shared library is best handled by automatically generating required directory structures and configuration files that adhere to established monorepo conventions and best practices.

Can I use automated scaffolding to enforce API Extractor and testing setups in a new monorepo package?

Yes, you can use automated scaffolding to enforce API Extractor and testing setups in a new monorepo package by automatically including the necessary configuration files during package creation.

Does package scaffolding support adding new directories within an existing Fluid Framework monorepo?

Package scaffolding supports adding new directories within an existing Fluid Framework monorepo by generating the required boilerplate and configuration files directly into the established project structure.

Why does setting up a new Distributed Data Structure in a monorepo require specific configuration files?

Setting up a new Distributed Data Structure requires specific configuration files to ensure compliance with monorepo standards for TypeScript, ESLint, API Extractor, and testing setups across the entire project.