Automated summary
Builds all packages in a Turborepo monorepo with detailed error reporting.
Strengths
- Leverages Turborepo caching for faster builds
- Reports which packages fail with specific error messages
- Supports filtering to specific packages via --filter
Limitations
- Requires Bun and Turborepo to be installed
- Assumes the project follows @topographic-studio/* naming
- Does not handle non-monorepo projects
When you need to build all packages in a Turborepo monorepo and get a clear summary of results.
When you only want to build a single package or when the project is not a monorepo.
Security analysis
SafeThe skill instructs the user to run standard build commands (bun run build, turbo run build) in a known monorepo. No destructive actions, external downloads, or data exfiltration are involved.
No concerns found
How this analysis is madeExamples
Build all packages in the monorepo using Turborepo.Build only the @topographic-studio/ui package in our monorepo.Monorepo Build Skill
Build all packages in the Topographic Studio monorepo using Turborepo.
Task
You are helping the user build all packages in the monorepo.
Instructions
- Navigate to the monorepo root directory
- Run the build command with Turborepo
- Report any build errors with specific package names and error messages
- If successful, show a summary of built packages
Commands
# Build all packages
bun run build
# Build with cache info
turbo run build --summarize
# Build specific package
turbo run build --filter=@topographic-studio/ui
Success Criteria
- All packages build without errors
- No TypeScript errors
- dist/ directories created for each package
- Build artifacts are properly generated
Error Handling
If build fails:
- Identify which package failed
- Show the specific error message
- Suggest fixes based on the error type:
- TypeScript errors → Check type definitions
- Import errors → Verify package dependencies
- Missing files → Check file paths
Output Format
Provide a clear summary:
✅ Built 4 packages successfully:
- @topographic-studio/ui
- @topographic-studio/utils
- @topographic-studio/config
- @topographic-studio/types
Build time: 3.2s
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/monorepo-build-with-turborepo-mma3js81/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/monorepo-build-with-turborepo-mma3js81' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/monorepo-build-with-turborepo-mma3js81/download' --output '.skill-downloads/monorepo-build-with-turborepo-mma3js81/SKILL.md.part' && mv '.skill-downloads/monorepo-build-with-turborepo-mma3js81/SKILL.md.part' '.skill-downloads/monorepo-build-with-turborepo-mma3js81/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/monorepo-build-with-turborepo-mma3js81/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.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.