Create New Package

VerifiedSafe

Scaffolds a new package in the Topographic Studio monorepo. Creates the full file structure (package.json, tsconfig, tsup.config, README, src/index.ts) and installs dependencies. Helpful for quickly adding a library, UI component, or utility to the monorepo.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude CodeCursorWindsurf
#monorepo#package-scaffold#typescript#workspace-setup

Recommended for

Automated summary

Scaffolds a new package in the Topographic Studio monorepo with all necessary configuration (package.json, TypeScript, tsup, etc.).

Strengths

  • Automates boilerplate file creation
  • Ensures consistency with the monorepo setup
  • Integrates build and lint scripts
  • Configures exports and dependencies

Limitations

  • Specific to the Topographic Studio monorepo structure
  • Requires Bun and tsup as build tools
  • May need manual adjustments for edge cases
When to use it

When you need to add a new package (library, UI components, types, etc.) to the monorepo.

When not to use it

If your code does not require a build step or you are working outside this monorepo.

Security analysis

Safe
Quality score90/100

The skill creates a new package in a monorepo with Bun, involving standard package installation and build commands. There are no destructive, exfiltrating, or obfuscated actions; the user controls all inputs.

No concerns found

How this analysis is made

Examples

Create a hooks package
Create a new package called 'hooks' for React custom hooks in the Topographic Studio monorepo.
Create a UI components package
Scaffold a UI component package named 'buttons' with React and TypeScript dependencies.
Create a types package
Generate a new utility package called 'validation' with a description 'Shared validation utilities' and no external dependencies.

New Package Skill

Create a new package in the Topographic Studio monorepo.

Task

You are helping the user scaffold a new package in the monorepo with all necessary configuration.

Instructions

  1. Gather information from the user:

    • Package name (e.g., "hooks", "animations", "api-client")
    • Package description
    • Package type (library, UI components, utilities, types, config)
    • Dependencies needed
  2. Create package structure:

    packages/{name}/
    ├── package.json
    ├── tsconfig.json
    ├── tsup.config.ts (if applicable)
    ├── README.md
    └── src/
        └── index.ts
    
  3. Configure package.json:

    • Name: @topographic-studio/{name}
    • Version: 0.0.1
    • Exports configuration
    • Build scripts
    • Repository info
  4. Add TypeScript config:

    • Extend root tsconfig
    • Configure paths
  5. Create initial source file:

    • Basic export structure
    • Example implementation
  6. Update root package.json:

    • Ensure workspace includes the new package
  7. Install dependencies:

    bun install
    
  8. Verify setup:

    bun run build --filter=@topographic-studio/{name}
    

Package.json Template

{
  "name": "@topographic-studio/{name}",
  "version": "0.0.1",
  "description": "{description}",
  "main": "./dist/index.js",
  "module": "./dist/index.mjs",
  "types": "./dist/index.d.ts",
  "exports": {
    ".": {
      "types": "./dist/index.d.ts",
      "import": "./dist/index.mjs",
      "require": "./dist/index.js"
    }
  },
  "files": ["dist"],
  "scripts": {
    "build": "tsup",
    "dev": "tsup --watch",
    "lint": "biome check .",
    "lint:fix": "biome check --write .",
    "typecheck": "tsc --noEmit"
  },
  "keywords": [],
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/leobrival/core.git",
    "directory": "packages/{name}"
  },
  "devDependencies": {
    "tsup": "^8.3.5",
    "typescript": "^5.7.2"
  }
}

Success Criteria

  • Package builds successfully
  • TypeScript types are correct
  • Can be imported from other packages
  • Documentation is complete

Output Format

Created new package: @topographic-studio/{name}

Location: packages/{name}/
Files created:
  ✅ package.json
  ✅ tsconfig.json
  ✅ tsup.config.ts
  ✅ README.md
  ✅ src/index.ts

Next steps:
1. Implement your package logic in src/
2. Add dependencies if needed: bun add -D package-name
3. Build: bun run build --filter=@topographic-studio/{name}
4. Use in other packages: import from "@topographic-studio/{name}"

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-new-package-mm5t8bne/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-new-package-mm5t8bne' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-new-package-mm5t8bne/download' --output '.skill-downloads/create-new-package-mm5t8bne/SKILL.md.part' && mv '.skill-downloads/create-new-package-mm5t8bne/SKILL.md.part' '.skill-downloads/create-new-package-mm5t8bne/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-new-package-mm5t8bne/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills