ts-package-dev

Create and govern TypeScript packages in a monorepo with strict types and Vitest tests.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/KJ-devs/focus-shield --skill ts-package-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ts-package-dev
Source: https://github.com/KJ-devs/focus-shield/tree/main/.claude/skills/ts-package-dev
Command: npx skills add https://github.com/KJ-devs/focus-shield --skill ts-package-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams build and govern reusable TypeScript packages in a monorepo with strict typing, consistent architecture, and automated testing.

Core Features & Use Cases

  • Monorepo package governance: define and enforce patterns for shared packages like session-engine, crypto, blocker-core, storage, and shared-types with zero UI dependencies.
  • Type-safe API contracts: promote strict TypeScript usage, barrel exports, and unified interfaces across packages.
  • Quality automation: integrate Vitest-based tests, standardized tsconfig, and automated linting and CI.

Quick Start

Bootstraps a new shared package in the monorepo using the prescribed scaffolding and conventions.

Frequently Asked Questions about ts-package-dev

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

FAQPage Schema
How do I enforce strict TypeScript and barrel exports across monorepo packages?

To enforce strict TypeScript and barrel exports across monorepo packages, you can apply standardized tsconfig configurations and governance patterns that expose a unified public API while maintaining zero UI dependencies.

What is the best way to scaffold a shared TypeScript package with zero UI dependencies?

The best way to scaffold a shared TypeScript package with zero UI dependencies is to use a prescribed scaffolding convention that enforces strict types, barrel exports, and standardized project structure within your monorepo.

Does this monorepo packaging approach work with Vitest for automated testing?

Yes, this monorepo packaging approach works with Vitest for automated testing by integrating Vitest-based tests alongside standardized tsconfig tooling to enforce quality automation and type-safe API contracts.

Why do I need barrel exports for shared TypeScript modules in a monorepo?

You need barrel exports for shared TypeScript modules in a monorepo to promote type-safe API contracts and unified interfaces, ensuring consistent architecture and clean public API exposure across all packages.

Can I use this to govern packages like session-engine and crypto in a monorepo?

Yes, you can use this to govern packages like session-engine, crypto, blocker-core, and storage by defining and enforcing consistent architectural patterns, strict typing, and standardized project structure across the monorepo.