菜单
NX workspace architecture — monorepo structure, generators, plugins, boundaries, Effect v4 isolation, dependency constraints, and workspace-map navigation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | nx-workspace |
| description | NX workspace architecture — monorepo structure, generators, plugins, boundaries, Effect v4 isolation, dependency constraints, and workspace-map navigation. |
prereqs: none provides: monorepo-orchestration, build-system, module-boundaries children: TEMPLATE.md, GRAPH.md, CHANGELOG.md, references/INDEX.md meta-refs: TEMPLATE.md (how to write docs), GRAPH.md (topology), CHANGELOG.md (history)
NX 22.x · Bun workspaces · 8 plugins · NX Cloud enabled
What are you doing?
│
├─ Running a target ────────────────── § Commands (below)
│
├─ Creating a new package ──────────── § Scaffold (below)
│ then → references/generators/INDEX.md
│
├─ Understanding registered plugins
│ ├─ Which plugins exist & what
│ │ targets they infer ───────────── references/plugins/INDEX.md
│ ├─ Specific plugin detail ───────── references/plugins/<name>.md
│ │ (js-typescript, vite, eslint, next, playwright, jest, rollup, nx-effect)
│ └─ How createNodesV2 works ──────── references/plugins/createNodesV2.md
│
├─ Writing a plugin or generator
│ ├─ Generator registration ───────── references/generators/registration.md
│ ├─ Generator schema.json ────────── references/generators/schema.md
│ ├─ Tree API & utilities ─────────── references/generators/tree-api.md
│ └─ Local plugin structure ───────── references/plugins/local-plugin.md
│
├─ Enforcing module boundaries
│ ├─ Current rules ────────────────── references/boundaries/INDEX.md
│ ├─ depConstraints full API ──────── references/boundaries/dep-constraints.md
│ └─ Migrating a package v3→v4 ────── references/boundaries/migration-pattern.md
│ prereqs → references/effect-v4/INDEX.md
│
├─ Effect v4 alias / isolation
│ ├─ Strategy & install commands ──── references/effect-v4/INDEX.md
│ ├─ Why not alternatives ─────────── references/effect-v4/why-not-alternatives.md
│ ├─ GA migration plan ────────────── references/effect-v4/ga-migration.md
│ └─ Bumping beta version ─────────── references/effect-v4/version-bumping.md
│
├─ Modifying this skill
│ ├─ Doc shapes & frontmatter ─────── TEMPLATE.md
│ ├─ Full topology map ────────────── GRAPH.md
│ └─ Change history ──────────────── CHANGELOG.md
│
└─ Debugging project graph ─────────── § Diagnostics (below)
bunx nx — always. Never npx, never bare nx.
bunx nx <target> <project> # one target, one project
bunx nx run-many -t build test # multiple targets, all projects
bunx nx affected -t <target> # only changed projects
bunx nx graph # visual dependency graph
bunx nx show project @tmnl/stx # full config + metadata
bunx nx list ./tools/nx-effect # plugin capabilities
bunx nx g ./tools/nx-effect:effect-v4-lib <name> --domain=<domain> [--withReact] [--withXState]
bunx nx g ./tools/nx-effect:effect-v4-lib <name> --dry-run
| Tag | Purpose |
|---|---|
scope:tmnl / scope:gbg | Ownership |
type:lib / type:app | Package type |
domain:state / ui / data / canvas | Domain |
effect:v4 | Uses Effect v4 via alias — boundary-enforced |
bunx nx show project @tmnl/stx # inspect config + inferred metadata
bunx nx show projects --with-target build # all projects with a target
bunx nx report # workspace health
NX_DAEMON=false bunx nx <cmd> # bypass daemon for debug output
| File | What |
|---|---|
nx.json | Plugin list, target defaults, NX Cloud |
eslint.config.mjs | Module boundary depConstraints |
tsconfig.base.json | @tmnl/* path aliases |
tools/nx-effect/ | Local plugin source |
packages/*/project.json | Per-project config |
| File | Purpose | When to read |
|---|---|---|
TEMPLATE.md | Entity shapes + frontmatter protocol | Before writing/modifying any doc in this skill |
GRAPH.md | Full topology with typed edges | Planning traversal, or after adding/removing nodes |
CHANGELOG.md | Structural change history | After modifying the skill, to log changes |
references/INDEX.md | Entry to all reference docs | When the router above doesn't have a direct match |
Meta-skill for @tmnl/effect-sui development: Effect v4/effect-smol patterns, Sui ontology, PTB/Flow/Query/package modules, localnet testing, Move publishing, diagnostics, and Nix mission-control tooling.
Effect v4 Atom patterns — reactive state management with effect-atom. Atom.make, Atom.family, Registry, runtime atoms, and React integration via useAtomValue.
Effect v4 Schema patterns — defining, validating, transforming, and serializing data with Schema. Covers v4 API, v3→v4 migration, classes, structs, unions, collections, transformations.
Effect v4 Service patterns — Context.Service, Layer composition, ManagedRuntime, dependency injection, and service testing with @effect/vitest.
GetByShell desktop shell — niri WM integration, panel system, calendar widget, popover components, modal patterns, and Nix-based configuration.
Skill governance codemod — create, inspect, update, delete, adopt, and dogfood skills. The meta-skill that governs all skills with CRUD protocols, verification utils, and self-referential governance.