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