# Ipollowork Maintainable Code

Mandatory iPolloWork code-change gate for modern, minimal, performant, reuse-first...

- Repository: https://github.com/Devin-AXIS/iPolloWork (7348 stars)
- Category: Design
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -g -a claude-code -y`
Codex: `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -g -a codex -y`
Cursor: `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -g -a cursor -y`
Gemini CLI: `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

The rest: https://github.com/Devin-AXIS/iPolloWork/blob/HEAD/.codex/skills/ipollowork-maintainable-code/SKILL.md