What problem does it solve?
Code changes in a large monorepo often introduce duplicate implementations, unjustified new files and dependencies, runtime artifacts in source trees, and parallel architectures. This Skill acts as a mandatory quality gate that audits every code change against iPolloWork's maintainability rules before completion.
Core Features & Use Cases
- Reuse-First Workflow: Requires searching existing components, services, and types with ripgrep before creating anything, and records a reuse decision for each new file or dependency.
- Automated Change Audit: Runs a Node.js script that inspects the git diff for forbidden directory names, new top-level directories, duplicate source files, cross-domain private imports, new dependencies, and runtime artifacts in source trees.
- Repository Boundary Guidance: Ships a reference map defining where UI, server, desktop, orchestrator, and shared package code belongs, plus dependency direction and runtime artifact layout rules.
- Use Case: When adding a new feature to the iPolloWork desktop app, the Skill guides placement in the correct domain, blocks a
v2 copy of an existing component, and fails the audit if a generated export is written under apps/server/src.
Quick Start
Ask the AI to implement your code change using the ipollowork-maintainable-code skill and run its audit script before finishing.
