Nx Workspace Patterns

Software development skill, available on Zeplik

Nx Workspace Patterns is a ready-to-run software development skill on Zeplik. Nx workspace layout, library-type tagging, module-boundary rules, affected commands, and caching guidance. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: Nx workspace guidance (layout, library types, boundary tags, affected + caching setup).

The Nx Workspace Patterns skill loads automatically when your request matches it, or you can invoke it directly by typing /nx-workspace-patterns in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.

What the Nx Workspace Patterns skill can do

Try these prompts on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

How the Nx Workspace Patterns skill works

Nx Workspace Patterns

Production patterns for Nx monorepo management.

When to Use

  • Setting up a new Nx workspace
  • Configuring project boundaries and module rules
  • Optimizing CI with affected commands
  • Implementing remote caching
  • Managing dependencies between projects, or migrating to Nx

This is Nx-specific. For general "should we use a monorepo" strategy, use monorepo-management. For Bazel or Turborepo, use their dedicated skills.

Architecture

workspace/
  apps/              # Deployable applications (web, api)
  libs/
    shared/          # ui, utils
    feature/         # auth, dashboard
  tools/             # Custom executors/generators
  nx.json            # Nx configuration
  workspace.json     # Project configuration

Library Types

TypePurposeExample
featureSmart components, business logicfeature-auth
uiPresentational componentsui-buttons
data-accessAPI calls, state managementdata-access-users
utilPure functions, helpersutil-formatting
shellApp bootstrappingshell-web

Tag every library by type (and by scope/domain). Tags are what the module-boundary lint rule enforces -- e.g. a ui lib may not import a feature lib, and libs in one domain may not reach into another's internals.

Optimization Levers

  • Affected commands -- run build/test/lint only on projects touched by a change (against the base branch), which is the biggest CI win.
  • Computation caching -- enable local caching early, then remote caching to share results across CI runs and developer machines.
  • Module boundaries -- enforce tag-based import rules so the dependency graph stays acyclic and layered.
  • Generators -- use generators for new libs/apps to keep structure and tagging consistent.

Best Practices

Do:

  • Use tags consistently and enforce with module boundaries
  • Enable caching early for significant CI savings
  • Keep libraries focused on a single responsibility
  • Use generators to ensure consistency
  • Document boundaries to help new developers

Don't:

  • Create circular dependencies -- the graph must stay acyclic
  • Skip affected -- test only what changed
  • Ignore boundary violations -- tech debt accumulates
  • Over-granularize -- balance the number of libraries

Output

An Nx workspace plan: recommended app/lib layout, library-type tagging scheme, module-boundary rules, and an affected-commands + caching setup for CI.

How to use the Nx Workspace Patterns skill

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Nx Workspace Patterns skill right away.

  2. Describe your software development task

    Ask in plain language, or type /nx-workspace-patterns to invoke the skill directly. Zeplik recognizes the Nx Workspace Patterns skill and applies its method.

  3. Review and refine the result

    Zeplik returns a structured document you can edit, download, and reuse. Ask follow-ups to refine it.

Source and credit

Author
wshobson
License
MIT

Adapted from the open-source wshobson/agents project and tuned to run natively on Zeplik. View source on GitHub.

Frequently asked questions

What is the Nx Workspace Patterns skill?
Nx Workspace Patterns is a ready-to-run software development skill on Zeplik. Nx workspace layout, library-type tagging, module-boundary rules, affected commands, and caching guidance. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: Nx workspace guidance (layout, library types, boundary tags, affected + caching setup).
How do I use Nx Workspace Patterns on Zeplik?
Sign in to Zeplik and ask in plain language, or type /nx-workspace-patterns in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
Which AI model does the Nx Workspace Patterns skill use?
Any model you choose. Zeplik works across every model in one chat, so the Nx Workspace Patterns skill runs on your preferred model for the task.
Where does the Nx Workspace Patterns skill come from?
The Nx Workspace Patterns skill is adapted from the open-source wshobson/agents project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
How much does the Nx Workspace Patterns skill cost?
Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.

Related software development skills

More on Zeplik

Try Nx Workspace Patterns on Zeplik

Every model, one chat. Bring the Nx Workspace Patterns skill into your next conversation and let the assistant do the work.

Browse all skills
Nx Workspace Patterns - Software development skill for Zeplik AI | Zeplik Chat