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
+22-4Lines changed: 22 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,9 @@ Some useful patterns for Vibe coding. This blog will be regularly updated with n
18
18
19
19
<!-- more -->
20
20
21
-
## Github Copilot Instructions
21
+
## VSCode Github Copilot
22
+
23
+
### Github Copilot Instructions
22
24
23
25
[Custom instructions](https://code.visualstudio.com/docs/copilot/customization/custom-instructions?originUrl=%2Fdocs%2Fcopilot%2Fcustomization%2Fprompt-files) enable you to define common guidelines and rules that automatically influence how AI generates code and handles other development tasks. Instead of manually including context in every chat prompt, specify custom instructions in a Markdown file to ensure consistent AI responses that align with your coding practices and project requirements.
- Example to add multiple instruction files: [microsoft/vscode-jupyter: Component-Specific Instructions](https://github.com/microsoft/vscode-jupyter/blob/main/.github/copilot-instructions.md)
35
37
36
-
## Github Copilot Chat Modes
38
+
###Github Copilot Chat Modes
37
39
38
40
[VSCode chat modes](https://code.visualstudio.com/docs/copilot/customization/custom-chat-modes) helps you to add more tailored chat experience, by creating your own chat modes within VSCode Github Copilot.
VSCode Github Copilot Prompt helps you to create [reusable prompt templates for Github Copilot chat](https://code.visualstudio.com/docs/copilot/customization/prompt-files) in the `.github/prompts` folder.
We can save the [Claude instructions](https://www.anthropic.com/engineering/claude-code-best-practices) in a file named `CLAUDE.md` in many places, suppose we have a git repository at `~/git/repo`, then we can create the `CLAUDE.md` file in any of these places:
|`~/.claude/CLAUDE.md`| Home folder | Global instructions applied to all Claude sessions across all projects. |
66
+
|`~/git/repo/CLAUDE.md`| Root of your repo (most common) | Share instructions across sessions and with team. Check into git. |
67
+
|`~/git/repo/CLAUDE.local.md`| Root of your repo (local only) | Personal instructions not shared with team. Add to `.gitignore`. |
68
+
|`~/git/CLAUDE.md`| Parent directory (monorepos) | Instructions for entire monorepo, automatically pulled when working in subdirectories. |
69
+
|`~/git/repo/sub_project/CLAUDE.md`| Child directory | Specific instructions for `sub_project`, pulled on demand when working with files in that directory. |
70
+
71
+
### Claude settings.local.json file
72
+
73
+
### Claude Code rules
56
74
57
75
[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.
0 commit comments