integra-generate-type-repository

Generate a TypeScript types repository scaffold with NPM dependencies and CI workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Integra-Beauty/integra-conventions --skill integra-generate-type-repository
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integra-generate-type-repository
Source: https://github.com/Integra-Beauty/integra-conventions/tree/main/skills/integra-generate-type-repository
Command: npx skills add https://github.com/Integra-Beauty/integra-conventions --skill integra-generate-type-repository

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates bootstrapping a private, production-ready TypeScript types repository by generating a standard project scaffold and wiring up dependencies.

Core Features & Use Cases

  • Quick bootstrap of package.json, tsconfig.json, .gitignore, .npmignore, LICENSE, and CI workflows for a TypeScript types library.
  • Configures editor tooling and linting (eslint + TypeScript) to enforce consistent development standards.
  • Supports vendor name substitution to customize templates for Integra Beauty's private NPM organization.

Quick Start

Provide the vendor name and run this skill to scaffold a private TypeScript types repository ready for publishing.

Frequently Asked Questions about integra-generate-type-repository

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

FAQPage Schema
How do I scaffold a private TypeScript types repository?▼

Scaffolding a private TypeScript types repository is done by generating a complete project structure including package.json, tsconfig, .gitignore, .npmignore, LICENSE, and CI workflows. This creates a ready-to-publish package with consistent tooling and linting setup.

What do I need to bootstrap a TypeScript types library with CI and linting?▼

Bootstrapping a TypeScript types library with CI and linting requires providing a vendor name to customize templates. The skill generates editor configurations, eslint with TypeScript support, and CI workflows to enforce consistent development standards for a production-ready package.

Can I customize the vendor name when generating a TypeScript types package?▼

Customizing the vendor name when generating a TypeScript types package is supported through vendor name substitution. This feature customizes templates for a private NPM organization, ensuring the package.json, LICENSE, and CI workflows reflect the correct vendor.

What's the best way to automate TypeScript types repo creation for private publishing?▼

Automating TypeScript types repo creation for private publishing is best handled by generating a standard project scaffold and wiring up dependencies. This approach yields a ready-to-publish package with consistent tooling, linting, and build setup without manual configuration.

Does this TypeScript scaffold work for new repository creation workflows only?▼

This TypeScript scaffold applies specifically to new repository creation workflows. It generates package.json, tsconfig, .gitignore, .npmignore, LICENSE, and CI workflows, enforcing vendor replacement to yield a ready-to-publish package for a TypeScript types library.