nx-workspace-patterns
Configure Nx Monorepo Workspaces
Nx monorepos can become slow and hard to govern as projects grow. This skill provides patterns for configuration, boundaries, caching, CI, generators, and affected commands.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "nx-workspace-patterns" from https://skillstore.io/skills/wshobson-nx-workspace-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-nx-workspace-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "nx-workspace-patterns". I need an Nx workspace for web and API apps with shared UI and utilities.
Expected outcome:
- Recommended apps and library groups by responsibility.
- Suggested tags for app, feature, UI, data access, utility, and scope boundaries.
- Initial caching and target-default choices for build, lint, test, and e2e tasks.
Using "nx-workspace-patterns". Our CI runs every task on every pull request.
Expected outcome:
- Affected command plan for lint, test, build, and e2e stages.
- Cacheable target recommendations and named input checks.
- Parallelism guidance with a safer single-threaded e2e step.
Using "nx-workspace-patterns". We need consistent feature libraries across teams.
Expected outcome:
- Generator responsibilities for naming, directory placement, tags, and files.
- Boundary rules that keep feature, UI, data access, and utility layers separate.
- Review notes for adapting the pattern to non-React stacks.
Security Audit
Medium RiskAll static findings were adjudicated as false positives because they are Markdown fences, inline examples, TypeScript template literals, documentation links, or normal Nx configuration references. No prompt injection or data exfiltration intent was found. One semantic issue remains: the remote cache guidance shows token fields directly in configuration, which could lead users to commit real secrets.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (25)
🌐 Network access (3)
📁 Filesystem access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/wshobson-nx-workspace-patterns/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-nx-workspace-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-nx-workspace-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-nx-workspace-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-nx-workspace-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
wshobson. (2026). nx-workspace-patterns security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-nx-workspace-patterns/audits/8BibTeX citation
@techreport{wshobson-wshobson-nx-workspace-patterns-2026,
author = {wshobson},
title = {nx-workspace-patterns security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/wshobson-nx-workspace-patterns/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nx-workspace-patterns security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/wshobson-nx-workspace-patterns/audits/8"
identifiers:
- type: other
value: "skillstore:wshobson-nx-workspace-patterns:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-nx-workspace-patterns
2026-08-21
wshobson-nx-workspace-patterns
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a New Nx Workspace
Design app and library layout, tags, target defaults, and initial generator defaults before implementation.
Improve Monorepo CI Speed
Apply affected commands, cacheable targets, named inputs, and parallel settings to reduce redundant work.
Enforce Project Boundaries
Use tag-based dependency constraints to keep application, feature, UI, data access, and utility layers organized.
Try These Prompts
Use nx-workspace-patterns to plan an Nx workspace for two applications and shared libraries. Include tags, library types, and basic caching choices.
Use nx-workspace-patterns to review my nx.json approach. Check target defaults, named inputs, cacheable tasks, and generator defaults for missing patterns.
Use nx-workspace-patterns to design a pull request CI flow with affected lint, test, build, and e2e steps. Include caching and parallelism guidance.
Use nx-workspace-patterns to design a feature library generator strategy. Include naming, tags, file generation, formatting, and boundary alignment.
Best Practices
- Keep project tags consistent so module boundary rules remain enforceable.
- Enable cacheable targets and named inputs early to improve local and CI feedback loops.
- Store remote cache credentials in secret managers, environment variables, or CI secrets.
Avoid
- Hardcoding cache access tokens in committed workspace configuration.
- Creating many tiny libraries without clear ownership or dependency boundaries.
- Bypassing affected commands and running every workspace task for every change.