ipollowork-maintainable-code

Enforce reuse-first implementation and repository boundaries in the iPolloWork monorepo. Use whenever AI creates, edits, or refactors React/TypeScript frontend code, server routes or services, shared packages, generated-file workflows, or features spanning apps/app and apps/server. Prevent duplicate components, helpers, types, routes, and runtime files; place new code and generated artifacts in the correct project-owned directories; and audit only the current change before completion.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, actionable overview: a sequenced workflow with a real validation feedback loop, concrete commands and paths, and well-signaled one-level-deep references to an existing reference and script. No dimension is weak.

Dimension	Reasoning	Score
Conciseness	The body is lean — tables and tight bullet directives with concrete paths — and never explains concepts Claude already knows, fitting the 'every token earns its place' anchor rather than the padded anchor at 2.	3 / 3
Actionability	Provides executable guidance: an exact audit command ('node .codex/skills/ipollowork-maintainable-code/scripts/audit-changes.mjs'), specific directories, path guards from 'apps/server/src/paths.ts', and a situation→action Reuse Decision table, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	The 'Required Workflow' is a clear 1–8 sequence with an explicit validation step (run the audit) and an error-recovery loop ('Resolve errors. Inspect every warning and either fix it or explain...'), satisfying the feedback-loop requirement rather than the checkpoint-missing anchor at 2.	3 / 3
Progressive Disclosure	The body is an overview that signals one-level-deep references to a real references/repository-boundaries.md (placement map, search checklist) and a real scripts/audit-changes.mjs, with content appropriately split and easy to navigate.	3 / 3
	Total	12 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete actions, an explicit 'Use whenever...' trigger, and a distinctive monorepo-scoped niche. Its only weakness is trigger-term naturalness, which relies on internal project jargon over phrasings a user would naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Prevent duplicate components, helpers, types, routes, and runtime files; place new code and generated artifacts in the correct project-owned directories; and audit only the current change' — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both 'what' ('Enforce reuse-first implementation and repository boundaries... Prevent duplicate... place new code...') and 'when' ('Use whenever AI creates, edits, or refactors...'), matching the explicit what-and-when anchor.	3 / 3
Trigger Term Quality	Includes some natural triggers ('creates, edits, or refactors React/TypeScript frontend code, server routes or services, shared packages') but leans on internal jargon ('apps/app and apps/server', 'generated-file workflows', 'reuse-first implementation') and misses common user phrasings, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped tightly to the iPolloWork monorepo with app/server/package ownership and reuse-first discipline, giving it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Devin-AXIS/iPolloWork
Path: .codex/skills/ipollowork-maintainable-code/SKILL.md
Commit: bd5caef

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.