Two files, one repository
0xwilliamortiz/ponytail-improved ships 5 formats across 5 indexed files. The question worth asking is whether the second one says anything the first does not.
CompareAGENTS.md ↔ Cline rulesAGENTS.md ↔ Copilot instructionsAGENTS.md ↔ Cursor rulesAGENTS.md ↔ Windsurf rulesCline rules ↔ Copilot instructionsCline rules ↔ Cursor rulesCline rules ↔ Windsurf rulesCopilot instructions ↔ Cursor rulesCopilot instructions ↔ Windsurf rulesCursor rules ↔ Windsurf rules
| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 0 | 0 | 100% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 0 | — |
What each file covers
Sections
1 shared · 0 only in A · 0 only in B- Ponytail, lazy senior dev mode
Commands
neither file has anySection tags
neither file has anyLine diff
0xwilliamortiz/ponytail-improved · AGENTS.md
@@ −29 @@
29
30Not lazy about: understanding the problem (read it fully and trace the real flow before picking a rung, a small diff you don't understand is just laziness dressed up as efficiency), input validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs (the platform is never the spec ideal, a clock drifts, a sensor reads off), anything explicitly requested. Lazy code without its check is unfinished: non-trivial logic leaves ONE runnable check behind, the smallest thing that fails if the logic breaks (an assert-based demo/self-check or one small test file; no frameworks, no fixtures). Trivial one-liners need no test.
31
32(Yes, this file also applies to agents working on the ponytail repo itself. Especially to them.)
33
0xwilliamortiz/ponytail-improved · .clinerules/ponytail.md
@@ +29 @@
29
30Not lazy about: understanding the problem (read it fully and trace the real flow before picking a rung, a small diff you don't understand is just laziness dressed up as efficiency), input validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs (the platform is never the spec ideal, a clock drifts, a sensor reads off), anything explicitly requested. Lazy code without its check is unfinished: non-trivial logic leaves ONE runnable check behind, the smallest thing that fails if the logic breaks (an assert-based demo/self-check or one small test file; no frameworks, no fixtures). Trivial one-liners need no test.
31
@@ −29 +29 @@
2929
3030 Not lazy about: understanding the problem (read it fully and trace the real flow before picking a rung, a small diff you don't understand is just laziness dressed up as efficiency), input validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs (the platform is never the spec ideal, a clock drifts, a sensor reads off), anything explicitly requested. Lazy code without its check is unfinished: non-trivial logic leaves ONE runnable check behind, the smallest thing that fails if the logic breaks (an assert-based demo/self-check or one small test file; no frameworks, no fixtures). Trivial one-liners need no test.
3131
32−(Yes, this file also applies to agents working on the ponytail repo itself. Especially to them.)
33−
