- name
- ipollowork-maintainable-code
- description
- Mandatory iPolloWork code-change gate for modern, minimal, performant, reuse-first implementation and clean repository ownership. Use whenever AI creates, edits, deletes, or refactors application code, server code, packages, scripts, tests, dependencies, schemas, routes, UI, or generated-file workflows. Reuse existing code before creating files, keep one source of truth, prevent parallel implementations and junk directories, justify every new file or dependency, and audit the current change before completion.
iPolloWork Maintainable Code
Treat this as the repository's single code-quality Skill. Implement changes with the smallest coherent diff, modern platform patterns, bounded runtime cost, and one clear owner. Search and reuse before creating anything.
Non-Negotiable Outcomes
- Modern: use the current repository stack and supported platform APIs; do not add legacy wrappers or compatibility layers without a real supported consumer.
- Minimal: solve the requested job with the fewest concepts, files, dependencies, states, and routes that remain clear.
- Performant: keep network, database, filesystem, bundle, render, and memory work bounded; optimize measured or structurally obvious hot paths.
- Reusable: extend compatible components, hooks, services, schemas, types, and utilities before creating parallel versions.
- Owned: keep one source of truth and place behavior in the narrowest existing owner.
- Clean: do not create convenience directories, one-off design notes, duplicate implementations, generated source artifacts, or abandoned replacement files.
Required Workflow
- Find the repository root. Read
AGENTS.md, the owning package manifest, the real entrypoint, and nearby implementations. - Read
references/repository-boundaries.mdbefore adding a file, directory, dependency, API, table, or cross-package import. - Define a change budget before editing: intended behavior, owning module, expected files touched, and whether any new file, directory, dependency, route, table, or persistent state is truly required. Default every category to zero.
- Search before creating anything:
- Search component names, visible labels, route names, event names, type names, and distinctive behavior with
rg. - Search
apps/app/src/components/ui,apps/app/src/components, the target domain,apps/server/src,packages/types, andpackages/uias relevant. - Inspect exports and call sites, not just filenames.
- Search component names, visible labels, route names, event names, type names, and distinctive behavior with
- State the reuse decision: reuse unchanged, extend compatibly, extract for real multiple consumers, or create as the last choice. For each new file or dependency, record why no existing owner can absorb the change.