- Language: All code, comments, variable names, function names, class names, and commit messages must be strictly in English.
- Idiomatic Style:
- Write code that adheres to the idiomatic style, conventions, and official style guides of the target language. This includes formatting, naming, and general structure.
- Assume a linter or formatter will eventually run; aim to produce code that is already close to passing common linting rules.
- Clarity and Readability:
- Prioritize clarity, readability, and maintainability over unnecessary "cleverness" or extreme brevity if it sacrifices understanding.
- Write self-documenting code.
- Follow the Principle of Least Surprise: code should behave in a way that users and other developers would naturally expect.
zeon 0xatm
ravarcheon
/ theHorse.txt
Last active
March 2, 2026 01:39
the horse that blocks your screen after a 2 minutes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // ==UserScript== | |
| // @name the horse that stands in your way | |
| // @namespace http://tampermonkey.net/ | |
| // @version 2026-03-01 | |
| // @description no more than 2 minutes of twitter. the first minute is a clear view, the second minute is where the horse slowly fades in. third minute and beyond there is nothing to see except horse | |
| // @author You | |
| // @match http*://*.x.com/* | |
| // @match http*://*.instagram.com/* | |
| // @icon https://www.google.com/s2/favicons?sz=64&domain=x.com | |
| // @grant none |
juanpabloaj
/ AGENTS.md
Last active
February 2, 2026 19:44
General guidelines and best practices for AI code generation