Individual skill
monorepo-workflow-architect
Designs monorepo workspaces, dependency graphs, package sharing, and incremental build pipelines with Turborepo or Nx.
skills/productivity/monorepo-workflow-architect/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 563 bytesSKILL.mdcore · 1,733 bytesexamples/example.mddoc · 811 bytes
Read excerpt
## Purpose
Architect scalable monorepo structures (Turborepo, Nx, pnpm workspaces) with strict package boundary isolation, shared internal UI/config/type packages, deterministic dependency graphs, and remote build caching.
## When to Use
- Consolidating multiple standalone repositories into a single unified monorepo.
- Setting up shared UI component libraries, TypeScript configs, or ESLint rules across apps.
- Fixing slow monorepo build times using incremental build pipelines and computation caching.
## What to Analyze
1. **Workspace Topography**: `apps/*` (deployable targets) vs `packages/*` (internal shared libraries).
2. **Dependency Graph Directionality**: Ensuring apps depend on packages, and leaf packages never depend upward.