What problem does it solve? Structuring a Turborepo and pnpm monorepo without clear conventions leads to broken package boundaries, duplicated configuration, slow CI, and uncacheable pipelines. This Skill provides the concrete structure, boundary rules, and pipeline standards for the iWana neXt monorepo so new apps and packages stay consistent. ## Core Features & Use Cases - Monorepo Structure Guidance: Defines the real workspace layout (apps, packages, e2e, docs) with naming and responsibility rules for each package. - Boundary and Pipeline Rules: Enforces dependency boundaries between packages and cacheable, composable turbo.json pipelines for lint, typecheck, test, and build. - Package Checklist & Anti-patterns: Provides a checklist for creating new packages and lists anti-patterns to avoid, such as cyclic dependencies or oversized shared packages. - Use Case: When adding a new shared package to the monorepo, use this Skill to verify its public API, package.json cleanliness, turbo script alignment, and boundary compliance before merging. ## Quick Start Ask the assistant to review the monorepo structure and define the pipeline and boundaries for a new package using the monorepo-architect skill.
