You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/posts/2025/2025-08-31-vibe-coding-cheat-sheet.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ categories:
9
9
comments: true
10
10
date:
11
11
created: 2025-08-31
12
+
updated: 2025-09-04
12
13
---
13
14
14
15
# Vibe coding cheat sheet
@@ -28,15 +29,16 @@ Chris Dzombak's [claude code rules](https://www.dzombak.com/blog/2025/08/getting
28
29
## Other instructions
29
30
30
31
```markdown title="python instructions"
31
-
- **Critical**: This code will undergo review by Python core developers. Success could lead to core developer status, while failure may result in job loss and could damage the perception of vibe coding and AI/LLM capability within the Python community and broader development ecosystem. Ensure the highest possible code quality standards.
32
+
- **Critical**: This code will undergo review by Python core developers (maybe with Guido too). Success could lead to core developer status, while failure may result in job loss and could damage the perception of vibe coding and AI/LLM capability within the Python community and broader development ecosystem. Ensure the highest possible code quality standards. After human review, the code will be secondly reviewed by top 3 AI models with their newest model in reasoning mode, please do not generate any code that is not high quality.
33
+
- **Critical**: If you think my question is ambiguous, ask for clarification before answering.
32
34
33
35
- How to enable venv: ...
34
36
- How to test and lint: ...
35
37
36
38
- Write code in Python 3.13+ syntax.
37
39
- Write clean, modern, elegant, maintainable, testable, high-performance, and production-quality code following established design patterns and best practices.
38
-
- Use modern Python features, such as pathlib over os.path, asyncio over multithreading, pytest over unittest, polars over pandas, fastapi over flask, etc.
40
+
- Use modern Python features, such as pathlib over os.path, asyncio over multithreading, pytest over unittest, polars over pandas, fastapi over flask, walrus, etc.
39
41
- Use pydantic v2 if you need data validation and settings management.
40
42
- Use sqlalchemy v2 for database interactions.
41
43
- Complex logic should be as less as possible in the code, but if it really needs to be there, give comments for explanation.
42
-
```
44
+
- Typing is mandatory. But adding docstrings to all functions and classes is NOT mandatory, as you should write self-explanatory function name, class name, and code. But if you think it is necessary, DO add them.
0 commit comments