Skip to content

aiskillstore/marketplace / skills/92bilal26/nx-monorepo

nx-monorepo

Verified

Nx monorepo management skill for AI-native development. This skill should be used when working with Nx workspaces, project graphs, affected detection, code generation, and caching. Use when: analyzing dependencies, running affected commands, generating code, configuring Nx Cloud, or optimizing build performance. Invoke nx-mcp tools for documentation queries.

FileKindSize
SKILL.mdskill md7.7 KB
references/team-lead.mdmarkdown3.9 KB
references/workflow.mdmarkdown3.0 KB
skill-report.jsonconfig62.0 KB

references/team-lead.md

View on GitHub
# Monorepo Team Lead

> Reference doc for nx-monorepo skill. Covers team leadership and ownership structures.

## Overview

This skill provides expert-level (L4) capabilities for team management, code ownership, human-AI collaboration, and cross-team coordination in monorepo environments.

**Skill Level**: Principal (E5/L4)
**Matrix Coverage**: T.* (Team), M.* (Manager Skills)

## Code Ownership

### CODEOWNERS Template

```
# .github/CODEOWNERS

# Domain ownership
/domains/auth/           @team-auth
/domains/content/        @team-content
/domains/ai/             @team-ai

# Platform ownership
/platform/               @team-platform
/infrastructure/         @team-sre

# Critical paths (require senior)
*.lock                   @team-platform
/platform/auth/          @team-auth @security-leads

# AI layer
/.claude/                @team-ai @team-devex
```

### Ownership Principles

```
1. Every file has exactly ONE owner
2. Owners MUST approve PRs to their areas
3. Cross-cutting changes require ALL owners
4. No orphan code (everything is owned)
```

## Human-AI Task Routing

### Decision Matrix

```
HUMAN ONLY:
- Architecture decisions
- Breaking change approval
- Security-critical changes
- Cross-team coordination
- Production deployments

AI-ASSISTED (Human reviews):
- Feature implementation
- Test writing
- Documentation
- Refactoring
- Dependency updates

AI AUTONOMOUS:
- Lint fixes
- Formatting
- Type error fixes
- Simple bug fixes
```

### Routing Decision Tree

```
Task arrives:
├── Strategic? → HUMAN MANAGER
├── Needs judgment? → HUMAN ENGINEER
├── Well-defined & repeatable? → AI AGENT
├── Cross-domain? → HUMAN COORDINATES
└── Default:
    ├── Simple → AI (with review)
    ├── Complex → HUMAN (AI assists)
    └── Production → HUMAN required
```

## Onboarding

### Week 1 Checklist

```markdown
## Day 1-2: Setup
- [ ] Clone and install: pnpm install
- [ ] Verify build: pnpm build
- [ ] Understand structure: ls -la

## Day 3-4: First PR
- [ ] Find "good first issue"
- [ ] Create branch, make change
- [ ] Submit PR, respond to review

## Day 5: Learn System
- [ ] Read CODEOWNERS
- [ ] Understand CI pipeline
- [ ] Know who to ask
```

### Knowledge Transfer

```
KT CHECKLIST:
[ ] Domain architecture explained
[ ] Key files/modules identified
[ ] Common tasks demonstrated
[ ] Gotchas/pitfalls documented
[ ] Contacts for help listed
```

## RFC Process

### RFC Template

```markdown
# RFC: [Title]

## Summary
One paragraph explaining the proposal.

## Motivation
Why? What problem does it solve?

## Design
Technical details.

## Affected Packages
- @myorg/pkg-a: [changes]
- @myorg/pkg-b: [changes]

## Migration
How will existing code migrate?

## Timeline
- Week 1: Implementation
- Week 2: Migration

## Approvals
- [ ] @team-owner
- [ ] @team-affected
```

## Cross-Team Coordination

### Protocol

```
1. CREATE RFC
   - Describe change
   - List affected domains
   - Propose migration

2. GET ALIGNMENT
   - Tag all owners
   - Get written approval

3. IMPLEMENT IN PHASES
   - Add new (no breaking)
   - Migrate consumers
   - Remove old

4. COMMUNICATE
   - Announce in channels
   - Update documentation
```

## Manager Competencies

### AI Work Evaluation

```
EVALUATE AI OUTPUT:
- Does it match requirements?
- Is code subtly wrong?
- Are edge cases handled?
- Is it over-engineered?
- Did it respect boundaries?
```

### Quality Gates

| Gate | AI | Human | Manager |
|------|-----|-------|---------|
| Tests pass | Must | Must | Review |
| Breaking change | Flag | Review | Approve |
| Cross-domain | Flag | Coordinate | Approve |
| Security | Pass | Verify | Approve |

## Quick Reference

```bash
# Ownership
cat .github/CODEOWNERS | grep <path>

# RFC
gh issue create --template=rfc.md

# Onboarding
cat ONBOARDING.md

# Task routing
# Strategic → Human Manager
# Judgment → Human Engineer
# Repeatable → AI Agent
```
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall