DevOps & Infra Skill
Bash Defensive Patterns
Master defensive Bash programming techniques for production-grade scripts.
$15
Nx Workspace Patterns
Configure and optimize Nx monorepo workspaces.
Production patterns for configuring and optimizing Nx monorepos so large codebases stay fast and maintainable. It leverages the Nx project graph to run only affected projects in CI, enforces module boundaries with ESLint so architecture can't silently rot, and sets up local plus remote computation caching. Keep a multi-app monorepo from turning into a 'big ball of mud.'
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category DevOps & Infra
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Editing a spec file should never invalidate a build cache. Tuning Nx until that holds, with module boundaries enforced as lint rules, is the whole point of this loop.
- Map the workspace first: apps versus libs, then classify every library as feature, ui, data-access or util and attach type and scope tags at generation time.
- Write nx.json with intent: cacheableOperations for build, lint, test and e2e, plus namedInputs that split production inputs from test and config files, so a spec file change never invalidates the build cache.
- Lock module boundaries as lint rules: the enforce-module-boundaries ESLint rule with depConstraints (feature may use ui, data-access and util; ui never imports feature; util only imports util), then run nx graph to surface circular dependencies.
- Wire CI around affected analysis: nx-set-shas derives base and head SHAs, then nx affected with parallel lint, test and build runs only the changed subtree instead of the whole repo.
- Enable remote caching through Nx Cloud or a self-hosted S3 runner so CI and local machines pull each other's build artifacts instead of rebuilding.
- Standardize scaffolding with custom generators that assign tags and project.json config automatically, so the boundary rules survive every new library.
One power source. 6 lines out.
nx-workspace-patterns · core
core active · 6 lines
- ✓ setting up a new nx work…
Setting up a new Nx workspace with apps and shared libs
- ✓ cutting ci time with nx
Cutting CI time with nx affected build/test/lint
- ✓ enforcing module boundar…
Enforcing module boundaries between feature, ui, and util libraries
- ✓ configuring local and re…
Configuring local and remote (Nx Cloud or S3) computation caching
- ✓ standardizing library sc…
Standardizing library scaffolding with custom generators
- ✓ migrating an existing repo
Migrating an existing repo to Nx
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
CI runs only what changed instead of the whole repo
license: perpetual -
Architecture violations caught at lint time, not in review
license: perpetual -
Repeated builds pulled from cache in seconds
license: perpetual -
Consistent, error-free library creation across the team
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Annotated nx.json with cacheable operations, target defaults, and named inputs
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
For platform and DevOps teams managing large multi-app monorepos that need fast CI and enforced architectural boundaries.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We use Turborepo. Do these patterns carry over?
The ideas overlap, affected-only CI and computation caching exist in both worlds, but everything concrete here is Nx-specific: nx.json target defaults, project.json executors, the ESLint boundary rules, and the Nx Cloud or S3 remote cache setup. Treat it as an Nx playbook, not a generic monorepo one.
-
How are module boundaries enforced beyond a diagram nobody reads?
Through ESLint rules driven by type and scope tags on every library, so a feature lib importing another team's internals fails lint before it reaches review. The custom generator auto-assigns those tags at creation, which closes the usual gap of someone forgetting to tag a new library.
-
Will this speed up our small single-app repo?
Honestly, no. Affected commands and remote caching pay off when a project graph has many apps and libraries to skip; in a small repo there's little to skip and you inherit the configuration overhead. It earns its keep at multi-app, multi-team scale.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.