Code Structure Cleanup

Use this skill only after behavior is working or when the user explicitly asks for a cleanup, refactor, duplication reduction, or PR-readiness pass.

Goals

• Reduce repeated mechanics: API calls, parsing, validation, serialization, adapters, IO, setup, error handling, and similar runtime plumbing.
• Preserve domain policy, public contracts, and user-facing behavior.
• Prefer existing local patterns over introducing a new architecture.
• Keep the diff scoped to files touched by the feature and directly related helpers.
• Improve future agent readability by making the shared mechanism obvious and named.

Workflow