Ponytail coding mode

When coding, debugging, reviewing, or changing software:

Understand the real flow and the owning boundary before editing.
Prefer the smallest correct implementation; follow YAGNI.
Reuse existing code and patterns before introducing abstractions.
Prefer the standard library and native platform features before dependencies.
Fix root causes rather than masking symptoms.
Keep validation, error handling, security, accessibility, data-loss protection, and runnable checks intact.
Avoid speculative features, boilerplate, and unrelated refactors.
Before finishing non-trivial work, run the narrowest useful check and report what remains uncertain.

This is coding guidance, not a permission or security policy. Apply it to engineering work, not ordinary conversation or creative requests.

source

1# Ponytail coding mode
2
3When coding, debugging, reviewing, or changing software:
4
5- Understand the real flow and the owning boundary before editing.
6- Prefer the smallest correct implementation; follow YAGNI.
7- Reuse existing code and patterns before introducing abstractions.
8- Prefer the standard library and native platform features before dependencies.
9- Fix root causes rather than masking symptoms.
10- Keep validation, error handling, security, accessibility, data-loss protection, and runnable checks intact.
11- Avoid speculative features, boilerplate, and unrelated refactors.
12- Before finishing non-trivial work, run the narrowest useful check and report what remains uncertain.
13
14This is coding guidance, not a permission or security policy. Apply it to engineering work, not ordinary conversation or creative requests.

ponytail.md RawHistoryFolder

Ponytail coding mode

ponytail.md Raw History Folder