agent coding skill risk: low
Monorepo Architecture Setup Advisor
The prompt defines a role for the model to act as a monorepo architect expert that clarifies goals, applies best practices, and follows a workflow for tasks like tool selection, wo…
SKILL 1 file
SKILL.md
--- name: monorepo-architect 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," --- # 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 ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
REQUIRED CONTEXT
- task related to monorepo setup, migration, CI optimization, or dependency management
OPTIONAL CONTEXT
- codebase size
- team structure
- current tooling
ROLES & RULES
Role assignments
- Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development.
- Do not use this skill when the task is unrelated to monorepo architect
- Do not use this skill when you need a different domain or tool outside this scope
- Use this skill only when the task clearly matches the scope described above
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing
EXPECTED OUTPUT
- Format
- plain_text
- Constraints
- clarify goals and inputs first
- follow numbered workflow steps
- apply best practices
- open implementation playbook when detailed examples needed
SUCCESS CRITERIA
- Clarify goals, constraints, and required inputs
- Apply relevant best practices and validate outcomes
- Provide actionable steps and verification
FAILURE MODES
- May be invoked for tasks outside monorepo scope
- May produce output without environment-specific validation
CAVEATS
- Dependencies
- Requires `resources/implementation-playbook.md` when detailed examples are needed
- Ambiguities
- Description sentence cuts off after 'monorepo setup,'
- References external file `resources/implementation-playbook.md` without defining its location or content
QUALITY
- OVERALL
- 0.75
- CLARITY
- 0.80
- SPECIFICITY
- 0.85
- REUSABILITY
- 0.75
- COMPLETENESS
- 0.70
IMPROVEMENT SUGGESTIONS
- Complete the truncated sentence in the opening description
- Replace the external file reference with inline guidance or remove it
- Add explicit input/output format expectations to the Instructions section
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Rapid App MVP Prototyperagentcoding
- AI-First Design Handoff Specs Generatoragentcoding
- Test-Driven Development Workflow Rulesagentcoding
- Structured Autonomy Implementation Agentagentcoding
- PROGRESS.md Manager for Agentic Codingagentcoding
- Hard Bug Diagnosis Disciplineagentcoding
- Git Development Branch Finisheragentcoding
- Code Review Feedback Reception Protocolagentcoding
- Systematic Debugging Process Guideagentcoding
- Matplotlib Python Plotting Guideagentcoding
- LaTeX Paper PDF Compileragentcoding
- Full Output Enforcement for Code Generationagentcoding
- PyTorch Geometric GNN Implementation Guideagentcoding
- Premium React UI Design Architectagentcoding
- Astropy Python Astronomy Library Guideagentcoding
- Book SFT Style Transfer Pipelineagentcoding
- Event Sourcing and CQRS Architectagentcoding
- FluidSim Python CFD Simulation Guideagentcoding
- NetworkX Python Graph Analysis Toolkitagentcoding
- Phase-Gated Debugging Protocol Enforceragentcoding
- SimPy Discrete-Event Simulation Guideagentcoding
- Phase-Gated Code Debugging Protocolagentcoding
- Biopython Molecular Biology Toolkit Guideagentcoding
- Haskell Advanced Type Systems Expertagentcoding
- Anime.js Complex Animation Workflowagentcoding