Typescript Monorepo
Developmenttypescript-monorepoTypescript Monorepo is an Agent Skill for development published in the pierrecomputer/pierre repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/pierrecomputer/pierre/blob/HEAD/.agents/skills/typescript-monorepo/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/typescript-monorepo, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
TypeScript Monorepo
TypeScript
Use TypeScript everywhere practical. Compiler settings are intentionally fairly strict.
- Shared compiler options live in
tsconfig.options.json. - Root
tsconfig.jsonmanages project references across the monorepo. - Typechecking uses
tsgoand 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.jsonreferences. - Ensure its local
tsconfig.jsonfollows existing package/app patterns. - Give it a
moon.yml(language, layer, tags, and any project-specific tasks); shared tasks come from.moon/tasks/*.ymlvia 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
referencesblock 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.