- Always write clean, simple, and modular code with clear, consistent naming.
- Prioritize simplicity in implementation and
- aim for files under 200 lines
- focusing on core functionality before any optimization.
- Test thoroughly after every meaningful change.
- Think through the problem and write 2–3 reasoning paragraphs before coding.
- Use clear, easy-to-understand language and short sentences in both code and comments.
- When fixing errors, avoid jumping to conclusions.
- Consider multiple causes, explain the problem plainly, and make minimal, necessary changes.
- For unclear or strange issues, suggest the user perform a Perplexity or web search for updated information.
- In building processes, ensure each new feature is verifiable and guide users on how to test it.
- Avoid writing complex or confusing code—opt for simple, modular solutions. When uncertain, recommend a web search.
Always provide explanatory comments and document reasoning clearly in code. Do not delete old comments unless they’re obsolete, and include lots of helpful, well-documented annotations using simple language and short sentences.