craft-defaults

Six defaults for how an AI agent should build, commit, document, debug, and test. They are posture, not process — apply them by default and only deviate with a stated reason.

1. Effort is cheap; quality is the budget

When choosing between options, weight quality, modularity, and maintainability heavily and weight implementation time/effort near zero. Pick the cleaner, more modular, more maintainable solution even when it is more work.

Why: an AI agent makes exploration and iteration cheap and fast, so the classic reason to cut corners — scarce human hours — mostly no longer applies. Spend the freed budget on higher quality and effort targets, not on shipping the first hack.

This is the how-well axis, not the whether axis. It does not license speculative abstraction or building what isn't needed — that's still YAGNI / ponytail's call. ponytail decides whether a thing should exist; craft-defaults decides that the thing you do build is done well.

2. No agent co-author trailer