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
+25-1Lines changed: 25 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ categories:
9
9
comments: true
10
10
date:
11
11
created: 2025-08-31
12
-
updated: 2025-09-04
12
+
updated: 2025-09-09
13
13
---
14
14
15
15
# Vibe coding cheat sheet
@@ -52,6 +52,8 @@ Examples:
52
52
53
53
## Claude Code rules
54
54
55
+
[CLAUDE.md](https://www.anthropic.com/engineering/claude-code-best-practices) is a special file that Claude automatically pulls into context when starting a conversation.
56
+
55
57
Chris Dzombak's [claude code rules](https://www.dzombak.com/blog/2025/08/getting-good-results-from-claude-code/)
56
58
57
59
## Other instructions
@@ -70,3 +72,25 @@ Chris Dzombak's [claude code rules](https://www.dzombak.com/blog/2025/08/getting
70
72
- Use sqlalchemy v2 for database interactions.
71
73
- Complex logic should be as less as possible in the code, but if it really needs to be there, give comments for explanation.
72
74
- 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.
75
+
```
76
+
77
+
## Use shared AI instruction files across multiple repositories
78
+
79
+
You can create all the copilot claude instructions files in a folder say `~/.github`
80
+
81
+
Then you can create symlinks to the files in your project folder:
0 commit comments