AGENT SKILL

monorepo-architect

Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,

License 许可
MIT
最近更新
2026-05-29
Stars
★ 1
Forks
0

01 前言 Front Matter

name
monorepo-architect
risk
safe
source
community
date_added
2026-02-27
description
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,

03 SKILL.md 正文

Monorepo Architect

Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.

Do not use this skill when

  • The task is unrelated to monorepo architect
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Capabilities

  • Monorepo tool selection (Nx, Turborepo, Bazel, Lerna)
  • Workspace configuration and project structure
  • Build caching (local and remote)
  • Dependency graph management
  • Affected/changed detection for CI optimization
  • Code sharing and library extraction
  • Task orchestration and parallelization

Use this skill when

  • Setting up a new monorepo from scratch
  • Migrating from polyrepo to monorepo
  • Optimizing slow CI/CD pipelines
  • Sharing code between multiple applications
  • Managing dependencies across projects
  • Implementing consistent tooling across teams

Workflow

  1. Assess codebase size and team structure
  2. Select appropriate monorepo tooling
  3. Design workspace and project structure
  4. Configure build caching strategy
  5. Set up affected/changed detection
  6. Implement task pipelines
  7. Configure remote caching for CI
  8. Document conventions and workflows

Best Practices

  • Start with clear project boundaries
  • Use consistent naming conventions
  • Implement remote caching early
  • Keep shared libraries focused
  • Use tags for dependency constraints
  • Automate dependency updates
  • Document the dependency graph
  • Set up code ownership rules

04 同仓库更多 Skills

mattonweb
mattonweb/ai-assistant-foundry

writing-clearly-and-concisely

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

内容创作者写作与文案
★ 1
mattonweb
mattonweb/ai-assistant-foundry

crafting-effective-readmes

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

★ 1
mattonweb
mattonweb/ai-assistant-foundry

wiki-architect

You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.

人力资源
★ 1
mattonweb
mattonweb/ai-assistant-foundry

readme

You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.

★ 1
mattonweb
mattonweb/ai-assistant-foundry

ubiquitous-language

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

★ 1
mattonweb
mattonweb/ai-assistant-foundry

technical-writing-style

Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing "sounds like AI", "feels robotic", "needs polish", or asks to "make it sound more natural" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.

内容创作者写作与文案
★ 1