From dcb15f5a2be468fecd9064f0c58a5e57a797b49b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 24 Feb 2026 09:19:57 +0100 Subject: [PATCH] chore: sync content to repository - vibe-coding (#9640) * chore: sync content to repo * Fix formatting of link in context document * Update if-you-have-stylecoding-preferences-document-them-for-ai@QBeh16mppfb2s4OGt4aPy.md --------- Co-authored-by: kamranahmedse <4921183+kamranahmedse@users.noreply.github.com> Co-authored-by: Javier Canales <56018501+jcanalesluna@users.noreply.github.com> --- ...-than-high-level-vague-instructions@JXtLbQ1JUQOPZorFy1ctF.md | 2 +- ...-brainstorm-before-complex-problems@17nFgML7zVjQYiHIOSLlK.md | 2 +- ...files-and-material-that-can-help-it@6kVVt2lihBW8tPGV-ll3_.md | 2 +- ...ng-preferences-document-them-for-ai@QBeh16mppfb2s4OGt4aPy.md | 2 +- ...window-when-available-and-necessary@CMnz6UFUGbxIGSH06ZdgH.md | 2 +- ...ech-stack-rather-than-newniche-ones@7mAZMKyiuZiEpKhrydp8J.md | 2 +- ...e-your-context-document-eg-claudemd@WypEm84Rr0t-IzCZiU92q.md | 2 +- ...o-add-logs-to-find-the-error-faster@vnm51qAe2C1cszHfh-o6P.md | 2 +- ...n-helpful-eg-act-as-a-ux-researcher@h2oehkZSKfMqlVBAgt46P.md | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/data/roadmaps/vibe-coding/content/be-specific-about-what-you-want-rather-than-high-level-vague-instructions@JXtLbQ1JUQOPZorFy1ctF.md b/src/data/roadmaps/vibe-coding/content/be-specific-about-what-you-want-rather-than-high-level-vague-instructions@JXtLbQ1JUQOPZorFy1ctF.md index 49b6bf904..29a65b5bf 100644 --- a/src/data/roadmaps/vibe-coding/content/be-specific-about-what-you-want-rather-than-high-level-vague-instructions@JXtLbQ1JUQOPZorFy1ctF.md +++ b/src/data/roadmaps/vibe-coding/content/be-specific-about-what-you-want-rather-than-high-level-vague-instructions@JXtLbQ1JUQOPZorFy1ctF.md @@ -1,3 +1,3 @@ -# Be specific about what you want +# Be specific about what you want Describe exactly what you want — layout, behavior, content, constraints. The more detail you give, the less the AI has to guess. Vague prompts produce vague results, and you end up spending more time correcting than if you had been specific from the start. \ No newline at end of file diff --git a/src/data/roadmaps/vibe-coding/content/explicitly-tell-ai-to-think-or-brainstorm-before-complex-problems@17nFgML7zVjQYiHIOSLlK.md b/src/data/roadmaps/vibe-coding/content/explicitly-tell-ai-to-think-or-brainstorm-before-complex-problems@17nFgML7zVjQYiHIOSLlK.md index b0697485d..3f79c7c24 100644 --- a/src/data/roadmaps/vibe-coding/content/explicitly-tell-ai-to-think-or-brainstorm-before-complex-problems@17nFgML7zVjQYiHIOSLlK.md +++ b/src/data/roadmaps/vibe-coding/content/explicitly-tell-ai-to-think-or-brainstorm-before-complex-problems@17nFgML7zVjQYiHIOSLlK.md @@ -1,4 +1,4 @@ -# Explicitly tell AI to "think" or "brainstorm" +# Explicitly tell AI to "think" or "brainstorm" For tricky problems, don't ask AI to jump straight to a solution. Tell it to think through the options first and explain its reasoning before writing any code. This simple instruction often leads to much better results on complex tasks. diff --git a/src/data/roadmaps/vibe-coding/content/give-ai-mockups-reference-files-and-material-that-can-help-it@6kVVt2lihBW8tPGV-ll3_.md b/src/data/roadmaps/vibe-coding/content/give-ai-mockups-reference-files-and-material-that-can-help-it@6kVVt2lihBW8tPGV-ll3_.md index d80fe57d1..33c934bbc 100644 --- a/src/data/roadmaps/vibe-coding/content/give-ai-mockups-reference-files-and-material-that-can-help-it@6kVVt2lihBW8tPGV-ll3_.md +++ b/src/data/roadmaps/vibe-coding/content/give-ai-mockups-reference-files-and-material-that-can-help-it@6kVVt2lihBW8tPGV-ll3_.md @@ -1,3 +1,3 @@ -# Give AI mockups, reference files, and material +# Give AI mockups, reference files, and material Always give AI something to look at, not just something to read. Paste in existing files, attach screenshots, or link to references. The more relevant material you provide, the less it has to guess and the better the output will be. \ No newline at end of file diff --git a/src/data/roadmaps/vibe-coding/content/if-you-have-stylecoding-preferences-document-them-for-ai@QBeh16mppfb2s4OGt4aPy.md b/src/data/roadmaps/vibe-coding/content/if-you-have-stylecoding-preferences-document-them-for-ai@QBeh16mppfb2s4OGt4aPy.md index b6f1e69ad..b4c69e72a 100644 --- a/src/data/roadmaps/vibe-coding/content/if-you-have-stylecoding-preferences-document-them-for-ai@QBeh16mppfb2s4OGt4aPy.md +++ b/src/data/roadmaps/vibe-coding/content/if-you-have-stylecoding-preferences-document-them-for-ai@QBeh16mppfb2s4OGt4aPy.md @@ -1,3 +1,3 @@ # If you have style/coding preferences, document them for AI -Write down your preferences — folder structure, naming conventions, coding patterns — in a dedicated file (e.g., a CLAUDE.md) and share it with AI at the start of each session. This stops you from correcting the same things over and over and keeps the code consistent throughout the project. \ No newline at end of file +Write down your preferences — folder structure, naming conventions, coding patterns — in a dedicated file (e.g., a CLAUDE.md) and share it with AI at the start of each session. This stops you from correcting the same things over and over and keeps the code consistent throughout the project. diff --git a/src/data/roadmaps/vibe-coding/content/leverage-long-context-window-when-available-and-necessary@CMnz6UFUGbxIGSH06ZdgH.md b/src/data/roadmaps/vibe-coding/content/leverage-long-context-window-when-available-and-necessary@CMnz6UFUGbxIGSH06ZdgH.md index c9b8962a1..94efadf5d 100644 --- a/src/data/roadmaps/vibe-coding/content/leverage-long-context-window-when-available-and-necessary@CMnz6UFUGbxIGSH06ZdgH.md +++ b/src/data/roadmaps/vibe-coding/content/leverage-long-context-window-when-available-and-necessary@CMnz6UFUGbxIGSH06ZdgH.md @@ -1,4 +1,4 @@ -# Leverage long context windows +# Leverage long context windows Some AI tools allow you to paste in a lot of information at once. When working on something complex, prompt AI with all the relevant files, notes, and context at once. The more the AI understands about your project upfront, the better decisions it will make throughout the session. diff --git a/src/data/roadmaps/vibe-coding/content/pick-a-popular-tech-stack-rather-than-newniche-ones@7mAZMKyiuZiEpKhrydp8J.md b/src/data/roadmaps/vibe-coding/content/pick-a-popular-tech-stack-rather-than-newniche-ones@7mAZMKyiuZiEpKhrydp8J.md index 97b8c5b95..7c3e82c0a 100644 --- a/src/data/roadmaps/vibe-coding/content/pick-a-popular-tech-stack-rather-than-newniche-ones@7mAZMKyiuZiEpKhrydp8J.md +++ b/src/data/roadmaps/vibe-coding/content/pick-a-popular-tech-stack-rather-than-newniche-ones@7mAZMKyiuZiEpKhrydp8J.md @@ -1,6 +1,6 @@ # Pick a popular tech stack rather than new/niche ones -Use popular tech stacks like React, Next.js, Tailwind, and Supabase. AI has been trained on a lot of code using these tools, so it gives better results. If you use something niche or very new, AI will make more mistakes, and you will spend more time fixing things. Popular stacks also have more tutorials and community support, which helps when you get stuck. +Use popular tech stacks like React, Next.js, Tailwind, and Supabase. AI has been trained on a lot of code using these tools, so it gives better results. For mobile, desktop, or hardware projects, the same rule applies: stick to established tools. If you use something niche or very new, AI will make more mistakes, and you will spend more time fixing things. Popular stacks also have more tutorials and community support, which helps when you get stuck. Visit the following resources to learn more: diff --git a/src/data/roadmaps/vibe-coding/content/regularly-update-your-context-document-eg-claudemd@WypEm84Rr0t-IzCZiU92q.md b/src/data/roadmaps/vibe-coding/content/regularly-update-your-context-document-eg-claudemd@WypEm84Rr0t-IzCZiU92q.md index b5d4d3654..706fe7456 100644 --- a/src/data/roadmaps/vibe-coding/content/regularly-update-your-context-document-eg-claudemd@WypEm84Rr0t-IzCZiU92q.md +++ b/src/data/roadmaps/vibe-coding/content/regularly-update-your-context-document-eg-claudemd@WypEm84Rr0t-IzCZiU92q.md @@ -5,4 +5,4 @@ Every time you make an important decision about your project, add it to your con Visit the following resources to learn more: - [@article@Writing a good CLAUDE.md](https://www.humanlayer.dev/blog/writing-a-good-claude-md) -- [@article@Rules Files for Safer Vibe Coding](https://www.wiz.io/blog/safer-vibe-coding-rules-files) \ No newline at end of file +- [@article@Rules Files for Safer Vibe Coding](https://www.wiz.io/blog/safer-vibe-coding-rules-files) diff --git a/src/data/roadmaps/vibe-coding/content/tell-ai-to-add-logs-to-find-the-error-faster@vnm51qAe2C1cszHfh-o6P.md b/src/data/roadmaps/vibe-coding/content/tell-ai-to-add-logs-to-find-the-error-faster@vnm51qAe2C1cszHfh-o6P.md index cf57c4e02..c47851cf8 100644 --- a/src/data/roadmaps/vibe-coding/content/tell-ai-to-add-logs-to-find-the-error-faster@vnm51qAe2C1cszHfh-o6P.md +++ b/src/data/roadmaps/vibe-coding/content/tell-ai-to-add-logs-to-find-the-error-faster@vnm51qAe2C1cszHfh-o6P.md @@ -1,3 +1,3 @@ -# Tell AI to add logs +# Tell AI to add logs Ask AI to add log statements to the relevant parts of the code so you can see exactly what is happening at each step when the error occurs. Once you know where things go wrong, ask it to remove the logs and apply the proper fix. \ No newline at end of file diff --git a/src/data/roadmaps/vibe-coding/content/use-act-as-framing-when-helpful-eg-act-as-a-ux-researcher@h2oehkZSKfMqlVBAgt46P.md b/src/data/roadmaps/vibe-coding/content/use-act-as-framing-when-helpful-eg-act-as-a-ux-researcher@h2oehkZSKfMqlVBAgt46P.md index 4202bdd7d..afd20b9ac 100644 --- a/src/data/roadmaps/vibe-coding/content/use-act-as-framing-when-helpful-eg-act-as-a-ux-researcher@h2oehkZSKfMqlVBAgt46P.md +++ b/src/data/roadmaps/vibe-coding/content/use-act-as-framing-when-helpful-eg-act-as-a-ux-researcher@h2oehkZSKfMqlVBAgt46P.md @@ -1,3 +1,3 @@ -# Use "act as" framing when helpful +# Use "act as" framing when helpful When you want a specific type of thinking, tell AI to take on a role. "Act as a senior developer" or "act as a UX researcher" shifts how it approaches your question and gives you more relevant, role-specific advice than a generic prompt would. \ No newline at end of file