Managing large-scale JavaScript projects becomes complex without proper tooling. This skill provides production-ready Nx workspace patterns for efficient monorepo management with build caching and affected commands.
Die Skill-ZIP herunterladen
In Claude hochladen
Gehe zu Einstellungen → Fähigkeiten → Skills → Skill hochladen
Einschalten und loslegen
Teste es
Verwendung von "nx-workspace-patterns". Configure nx.json with caching for build, test, and lint operations
Erwartetes Ergebnis:
Provides complete nx.json configuration with tasksRunnerOptions, targetDefaults, namedInputs, and cacheable operations for optimal CI performance.
Verwendung von "nx-workspace-patterns". Set up module boundaries preventing circular dependencies
Erwartetes Ergebnis:
Generates ESLint configuration with depConstraints enforcing tag-based dependency rules between apps, features, UI libraries, and utilities.
Sicherheitsaudit
SicherStatic analysis flagged 35 patterns that are all false positives. The SKILL.md file is documentation-only content containing Nx configuration templates, CLI command examples, and best practices. External command patterns are documentation code blocks, network references are hyperlinks to official Nx documentation, and filesystem patterns are JSON schema paths in configuration templates. No executable code or security risks present.
Qualitätsbewertung
Was du bauen kannst
New Nx Workspace Setup
Configure a new Nx monorepo with proper project structure, caching, and task runner options for a team starting a large-scale React application.
CI Pipeline Optimization
Implement affected commands in GitHub Actions to reduce CI times by only testing and building changed projects.
Module Boundary Enforcement
Set up ESLint rules to enforce architectural boundaries between feature, UI, and utility libraries across the organization.
Probiere diese Prompts
Help me set up a new Nx workspace for a React application with proper caching configuration.
Generate ESLint module boundary rules for an Nx workspace with apps and libs directories, enforcing that apps can depend on features and utilities but features cannot depend on other features.
Create a GitHub Actions workflow that uses Nx affected commands to run lint, test, and build only on changed projects when pulling from main branch.
Write a custom Nx generator that creates a feature library with pre-configured tags, index exports, and barrel files for a scoped monorepo structure.
Bewährte Verfahren
- Use descriptive tags consistently and enforce them with module boundary rules
- Enable build caching early in project setup for significant CI time savings
- Keep libraries focused with single responsibility to maintain clean dependencies
Vermeiden
- Creating circular dependencies between libraries which breaks the dependency graph
- Skipping affected commands and running full test suites on every commit
- Over-granularizing with too many small libraries increasing maintenance burden
Häufig gestellte Fragen
What is the difference between Nx affected and running all tasks?
How does Nx caching work?
What are module boundaries and why use them?
Do I need Nx Cloud for caching?
How do I migrate an existing workspace to Nx?
What library types should I use in my Nx workspace?
Entwicklerdetails
Autor
sickn33Lizenz
MIT
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/nx-workspace-patternsRef
main
Dateistruktur
đź“„ SKILL.md