pierrecomputer/pierre

typescript-monorepo

Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.

First seen Aug 2, 2026

Installation

$ npx skills add pierrecomputer/pierre --skill typescript-monorepo

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pierrecomputer/pierre · top by installs.

npx skills add pierrecomputer/pierre

Browse all from pierrecomputer/pierre

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6.1K
License LICENSE.md
Default branch main
Open issues 38
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,603 B
  • docs SUMMARY.md 187 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

TypeScript Monorepo

TypeScript

Use TypeScript everywhere practical. Compiler settings are intentionally fairly strict.

  • Shared compiler options live in tsconfig.options.json.
  • Root tsconfig.json manages project references across the monorepo.
  • Typechecking uses tsgo and runs through moon: moonx <project>:typecheck

(moon builds workspace dependencies first, since types resolve through each dependency's built dist).

Project References

When adding a new package or app:

  • Add it to the root tsconfig.json references.
  • Ensure its local tsconfig.json follows existing package/app patterns.
  • Give it a moon.yml (language, layer, tags, and any project-specific tasks);

shared tasks come from .moon/tasks/*.yml via tags or project language.

When one workspace package depends on another:

  • Add the dependency as workspace:* in the consuming package.
  • Add the dependency to the consuming package's TypeScript references block

when needed for accurate and fast typechecking.

Workspace Dependencies

Use the pnpm-workspace.yaml catalog rules from tooling-and-dependencies for external packages. Use workspace:* for internal package dependencies.

If a package is published, review its exports, typesVersions, files, peer dependencies, and its moon prepublish task chain before changing public entrypoints or dependency ranges.