chore: sync content to repo (#10023)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
2026-05-27 12:50:02 +02:00
1 parent 56d14faa28
commit c812044859
@@ -2,7 +2,7 @@

 You don't need to memorize Git commands. Ask AI to write commit messages, create branches, push code, and manage your repository for you. This removes one of the biggest barriers beginners face with version control and keeps the workflow moving smoothly.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@AI Coding Best Practices for Modern Development - GitHub](https://github.com/kurdin/ai-coding-best-practices-for-modern-development)
 - [@article@Automatic Commit Message Generation in Cursor IDE - Cursor Forum](https://forum.cursor.com/t/feature-request-integration-of-automatic-commit-message-generation-in-cursor-ide/1654)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Vibe Coding Principles: Modularity and Coupling Principles](https://blog.synapticlabs.ai/what-is-modular-programming-loose-coupling)
 - [@article@Clean Code: What Is Refactoring and Why It Matters - Refactoring.Guru](https://refactoring.guru/refactoring/what-is-refactoring)
- [@article@Modular Code - Quality Assurance of Code for Analysis and Research - Gov.UK](https://best-practice-and-impact.github.io/qa-of-code-guidance/modular_code.html)
+- [@article@Modular Code - Quality Assurance of Code for Analysis and Research - Gov.UK](https://best-practice-and-impact.github.io/qa-of-code-guidance/modular_code.html)
@@ -2,7 +2,7 @@

 Every time AI builds a feature, ask it to write tests for that feature right away. End-to-end tests are especially useful because they simulate a real user going through your app and catch bugs that affect the experience before they reach real users.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@AI-Driven Testing Best Practices - Foojay.io](https://foojay.io/today/ai-driven-testing-best-practices/)
 - [@article@AI-Powered E2E Testing: How Cursor and Release Make Quality at Speed - Release](https://release.com/blog/ai-powered-e2e-testing)
@@ -2,7 +2,7 @@

 Keep your prompts focused. Ask AI to do one thing, review the result, and then move on to the next. When you stack multiple requests into one prompt, the AI loses focus and mistakes pile up across all of them at once.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@The Productivity Paradox of AI Coding Assistants - Cerbos](https://www.cerbos.dev/blog/productivity-paradox-of-ai-coding-assistants)
 - [@article@Vibe Coding: Best Practices for Prompting - Supabase](https://supabase.com/blog/vibe-coding-best-practices-for-prompting)
@@ -1,8 +1,10 @@
 # Tell AI what NOT to do

-Keep track of the mistakes AI keeps repeating and include them in your prompts. Telling AI what to avoid is just as important as telling it what to do. A simple line like "do not add placeholder data" can prevent a lot of unnecessary back and forth.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@Negative Prompting and How to Tell AI What NOT to Do - Vibe Coder](https://blog.vibecoder.me/negative-prompting-telling-ai-what-not-to-do)
 - [@article@Case Study: "Negative Prompting" for Code Review. Hype or Real? - Trilogy AI](https://trilogyai.substack.com/p/case-study-i-tested-the-negative)
- [@article@Using Negative AI Prompts Effectively - Virtualization Review](https://virtualizationreview.com/articles/2025/12/08/using-negative-ai-prompts-effectively.aspx)
+- [@article@Using Negative AI Prompts Effectively - Virtualization Review](https://virtualizationreview.com/articles/2025/12/08/using-negative-ai-prompts-effectively.aspx)
@@ -2,7 +2,7 @@

 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.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Prompt Engineering Best Practices: Tutorial & Examples - LaunchDarkly](https://launchdarkly.com/blog/prompt-engineering-best-practices/)
 - [@article@The Prompt Engineering Playbook for Programmers - Addy Osmani](https://addyo.substack.com/p/the-prompt-engineering-playbook-for)
@@ -1,9 +1,8 @@
 # Codex

-Codex is OpenAI's code-focused model, integrated into tools like GitHub Copilot and available through the API. It is strong at translating a clearly defined requirement into working code; describe the specific behavior you want and it generates the implementation. It works best for contained, well-defined tasks rather than open-ended architectural decisions.
+Codex is an AI model developed by OpenAI that translates natural language instructions into functional code. It acts as the engine behind many modern programming assistants, allowing developers to describe what they want to build in plain English and receiving the corresponding code snippets in return.

 Visit the following resources to learn more:

- [@official@Codex - Official Website](https://chatgpt.com/codex)
- [@video@Getting started with Codex](https://www.youtube.com/watch?v=px7XlbYgk7I)
- [@official@Best practices - Codex](https://developers.openai.com/codex/learn/best-practices)
+- [@official@Codex Docs](https://developers.openai.com/codex)
+- [@video@Codex Crash Course](https://www.youtube.com/playlist?list=PL4cUxeGkcC9iDBeA8IyR1IE1kl4w5IDEG)
@@ -5,5 +5,5 @@ With TDD, you write the test before the code. Ask AI to first write a test that
 Visit the following resources to learn more:

 - [@article@TDD in the Age of Vibe Coding: Pairing Red-Green-Refactor with AI](https://medium.com/@rupeshit/tdd-in-the-age-of-vibe-coding-pairing-red-green-refactor-with-ai-65af8ed32ae8)
- [@video@Claude Code Agents TDD Vibe Coding Test + Research](https://www.youtube.com/watch?v=6kt6Lhz4yJU)
- [@article@Test-First Prompting: Using TDD for Secure AI-Generated Code - Endor Labs](https://www.endorlabs.com/learn/test-first-prompting-using-tdd-for-secure-ai-generated-code)
+- [@article@Test-First Prompting: Using TDD for Secure AI-Generated Code - Endor Labs](https://www.endorlabs.com/learn/test-first-prompting-using-tdd-for-secure-ai-generated-code)
+- [@video@Claude Code Agents TDD Vibe Coding Test + Research](https://www.youtube.com/watch?v=6kt6Lhz4yJU)
@@ -4,6 +4,6 @@ AI is very good at fixing errors when you give it the right information. Paste t

 Visit the following resources to learn more:

- [@video@Vibe Coding Debugging: The Only Tutorial You Need for 10X Fast Debugging](https://www.youtube.com/watch?v=2h8WSChA1-o)
 - [@article@10 Debugging Techniques and How AI Is Changing the Game - WeAreBrain](https://wearebrain.com/blog/10-effective-debugging-techniques-for-developers/)
- [@article@AI-First Debugging: Tools and Techniques for Faster Root Cause Analysis - LogRocket](https://blog.logrocket.com/ai-debugging/)
+- [@article@AI-First Debugging: Tools and Techniques for Faster Root Cause Analysis - LogRocket](https://blog.logrocket.com/ai-debugging/)
+- [@video@Vibe Coding Debugging: The Only Tutorial You Need for 10X Fast Debugging](https://www.youtube.com/watch?v=2h8WSChA1-o)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Teaching AI to "Think" Before Answering](https://medium.com/@21joshishubham/teaching-ai-to-think-before-answering-1bf8c6bb16c4)
 - [@article@What is Chain of Thought (CoT) Prompting? - IBM](https://www.ibm.com/think/topics/chain-of-thoughts)
- [@article@Chain-of-Thought (CoT) Prompting Guide](https://www.promptingguide.ai/techniques/cot)
+- [@article@Chain-of-Thought (CoT) Prompting Guide](https://www.promptingguide.ai/techniques/cot)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Want Better AI Outputs? Try Context Engineering - GitHub Blog](https://github.blog/ai-and-ml/generative-ai/want-better-ai-outputs-try-context-engineering/)
 - [@article@Context Engineering: Managing AI-Generated Code Complexity - INNOQ](https://www.innoq.com/en/blog/2025/10/ai-context-management/)
- [@article@What Is the WHISK Framework? AI Coding Context Management](https://www.mindstudio.ai/blog/what-is-whisk-framework-ai-coding-context-management/)
+- [@article@What Is the WHISK Framework? AI Coding Context Management](https://www.mindstudio.ai/blog/what-is-whisk-framework-ai-coding-context-management/)
@@ -1,8 +1,10 @@
 # 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.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@Mastering Project Context Files for AI Coding Agents - EclipseSource](https://eclipsesource.com/blogs/2025/11/20/mastering-project-context-files-for-ai-coding-agents/)
 - [@article@Context Engineering for Coding Agents - Martin Fowler](https://martinfowler.com/articles/exploring-gen-ai/context-engineering-coding-agents.html)
- [@article@Set up a Context Engineering Flow in VS Code - VS Code Docs](https://code.visualstudio.com/docs/copilot/guides/context-engineering-guide)
+- [@article@Set up a Context Engineering Flow in VS Code - VS Code Docs](https://code.visualstudio.com/docs/copilot/guides/context-engineering-guide)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Context Degradation Syndrome: When Large Language Models Lose the Plot](https://jameshoward.us/2024/11/26/context-degradation-syndrome-when-large-language-models-lose-the-plot)
 - [@article@Context Rot: Why AI Gets Worse the Longer You Chat](https://www.producttalk.org/context-rot/)
- [@article@Best Practices for Context Management in Long AI Chats](https://community.openai.com/t/best-practices-for-cost-efficient-high-quality-context-management-in-long-ai-chats/1373996)
+- [@article@Best Practices for Context Management in Long AI Chats](https://community.openai.com/t/best-practices-for-cost-efficient-high-quality-context-management-in-long-ai-chats/1373996)
@@ -1,8 +1,10 @@
 # Ask Al to create a list of possible causes

-If a bug keeps coming back after fixes, ask AI to step back and list all the possible reasons it could be happening. This forces a more systematic approach and often surfaces the real root cause instead of just patching symptoms.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@The Developer's Guide to Debugging AI-Generated Code - Speedscale](https://speedscale.com/blog/the-developers-guide-to-debugging-ai-generated-code/)
 - [@article@Debugging AI-Generated Code: 8 Failure Patterns & Fixes - Augment Code](https://www.augmentcode.com/guides/debugging-ai-generated-code-8-failure-patterns-and-fixes)
- [@article@AI Debugging Tools - CREATEQ](https://www.createq.com/en/software-engineering-hub/ai-debugging-tools)
+- [@article@AI Debugging Tools - CREATEQ](https://www.createq.com/en/software-engineering-hub/ai-debugging-tools)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Building Shared Coding Guidelines for AI (and People Too) - Stack Overflow Blog](https://stackoverflow.blog/2026/03/26/coding-guidelines-for-ai-agents-and-people-too/)
 - [@article@The Renaissance of Written Coding Conventions: Because AI Reads Them Too](https://www.brokenrobot.xyz/blog/the-renaissance-of-written-coding-conventions/)
- [@article@How to Write a Good CLAUDE.md File - Builder.io](https://www.builder.io/blog/claude-md-guide)
+- [@article@How to Write a Good CLAUDE.md File - Builder.io](https://www.builder.io/blog/claude-md-guide)
@@ -2,8 +2,8 @@

 Git gives you precise, reliable control over your code history. AI's built-in undo features are not always trustworthy, especially when changes span multiple files. A proper Git revert takes you back to an exact saved state with no surprises.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@article@Vibe Coding with `reset --hard` - DoltHub](https://www.dolthub.com/blog/2025-03-31-vibin-with-reset/)
+- [@article@Vibe Coding with reset --hard - DoltHub](https://www.dolthub.com/blog/2025-03-31-vibin-with-reset/)
 - [@article@Git Revert Explained: Safely Undoing Your Changes - CloudBees](https://www.cloudbees.com/blog/git-revert-explained)
 - [@article@The Art of Reverting - Runtime Revolution](https://revs.runtime-revolution.com/the-art-of-reverting-b2940dba26f0)
@@ -1,8 +1,10 @@
 # Illustrate AI with Examples

-Show AI what you want instead of just telling it. Attach a screenshot, a rough sketch, or a link to a website that looks like what you are trying to build. If you have code that you want AI to follow as a pattern, paste it in. Examples work much better than descriptions because AI doesn't have to guess what you mean. You can use tools like [excalidraw](https://excalidraw.com) for sketching.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@Cooking with Constraints: A Designer's Framework for Better AI Prompts - Figma](https://www.figma.com/blog/designer-framework-for-better-ai-prompts/)
 - [@article@4 Prompt Engineering Examples That Will Make You a Writing Maven - CodeSignal](https://codesignal.com/blog/prompt-engineering-examples/)
- [@article@Best Practices for Using AI in VS Code - VS Code Docs](https://code.visualstudio.com/docs/copilot/best-practices)
+- [@article@Best Practices for Using AI in VS Code - VS Code Docs](https://code.visualstudio.com/docs/copilot/best-practices)
@@ -5,5 +5,5 @@ Version control is the system you use to track changes to your code over time. V
 Visit the following resources to learn more:

 - [@article@Git Guardian: Why Version Control is Non-Negotiable in Vibe Coding](https://verityai.co/blog/vibe-coding-version-control)
- [@video@Vibe Coding Course 7 – Version Control Basics (Git)](https://www.youtube.com/watch?v=qUE-nVUrpq4)
- [@article@Version Control in the Age of AI - Tower Blog](https://www.git-tower.com/blog/version-control-in-the-age-of-ai)
+- [@article@Version Control in the Age of AI - Tower Blog](https://www.git-tower.com/blog/version-control-in-the-age-of-ai)
+- [@video@Vibe Coding Course 7 – Version Control Basics (Git)](https://www.youtube.com/watch?v=qUE-nVUrpq4)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Store Config in the Environment - The Twelve-Factor App](https://12factor.net/config)
 - [@article@Secrets Management Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html)
- [@article@What Are Hardcoded Secrets? Risks and Best Practices - Apiiro](https://apiiro.com/glossary/hardcoded-secrets/)
+- [@article@What Are Hardcoded Secrets? Risks and Best Practices - Apiiro](https://apiiro.com/glossary/hardcoded-secrets/)
@@ -2,7 +2,7 @@

 Good tests give you the freedom to clean up and reorganize the code without fear of breaking things. Once your test suite is in place, make refactoring a regular habit and let the tests tell you immediately if anything goes wrong.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@What is AI Code Refactoring? - Graphite](https://graphite.com/guides/what-is-ai-code-refactoring)
 - [@article@The Developer's Refactoring Safety Net - Dev.to](https://dev.to/tracygjg/the-developers-refactoring-safety-net-11nc)
@@ -1,8 +1,10 @@
 # Prompt the error message and let AI do the rest

-When something breaks, copy the full error message and paste it directly into your prompt along with a short description of what you were doing. In most cases, this is enough for AI to find the problem and suggest a fix without any back and forth.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@Debugging with AI: Can It Replace an Experienced Developer? - Developer Way](https://www.developerway.com/posts/debugging-with-ai)
 - [@article@How to Replace Stack Overflow with an AI Pair - Kinde](https://kinde.com/learn/ai-for-software-engineering/prompting/how-to-replace-stack-overflow-with-an-ai-pair-prompt-engineering-for-real-debugging/)
- [@article@Treat AI-Generated Code as a Draft - Addy Osmani](https://addyo.substack.com/p/treat-ai-generated-code-as-a-draft)
+- [@article@Treat AI-Generated Code as a Draft - Addy Osmani](https://addyo.substack.com/p/treat-ai-generated-code-as-a-draft)
@@ -2,7 +2,7 @@

 Before asking AI to build something new, make sure all your current changes are committed. This gives you a clean checkpoint so that if the new feature causes problems, you can discard the changes and start again without any risk to what you already have.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Git Feature Branch Workflow - Atlassian](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow)
 - [@article@Vibe Coding in Practice: Patterns, Pitfalls, and Prompting Strategies - AIM Consulting](https://aimconsulting.com/insights/vibe-coding-practice-patterns-pitfalls-prompting/)
@@ -8,4 +8,4 @@ Visit the following resources to learn more:

 - [@article@Web Frameworks 2026: Future-Proofing Enterprise Tech Stack - DEV Community](https://dev.to/devin-rosario/web-frameworks-2026-future-proofing-enterprise-tech-stack-4l03)
 - [@article@The 2025 Tech Stack Shake-Up: Why Next.js, Python and Postgres Are Taking Over - DEV Community](https://dev.to/usman_awan/the-2025-tech-stack-shake-up-why-nextjs-python-postgres-are-taking-over-the-world-4d6p)
- [@article@TypeScript, Python, and the AI Feedback Loop Changing Software Development - GitHub Blog](https://github.blog/news-insights/octoverse/typescript-python-and-the-ai-feedback-loop-changing-software-development/)
+- [@article@TypeScript, Python, and the AI Feedback Loop Changing Software Development - GitHub Blog](https://github.blog/news-insights/octoverse/typescript-python-and-the-ai-feedback-loop-changing-software-development/)
@@ -1,8 +1,10 @@
 # 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.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@Top 10 Debugging Techniques for Vibe Coders - EmbedAI](https://embedai.dev/blog/debugging-techniques-vibe-coders)
 - [@article@Vibe Coding Debugging: Mastering Effective Techniques - Alan Knox](https://alanknox.com/debugging-engineering-for-vibe-coders/)
- [@article@The Truth About Vibe Coding: AI Won't Save You From Debugging - dev.to](https://dev.to/mikaelsantilio/the-truth-about-vibe-coding-ai-wont-save-you-from-debugging-2i14)
+- [@article@The Truth About Vibe Coding: AI Won't Save You From Debugging - dev.to](https://dev.to/mikaelsantilio/the-truth-about-vibe-coding-ai-wont-save-you-from-debugging-2i14)
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@article@Vibe Coding Testing Gap: AI Apps Need Tests - Autonoma](https://getautonoma.com/blog/vibe-coding-testing)
 - [@article@Test-Driven Development with AI - Builder.io](https://www.builder.io/blog/test-driven-development-ai)
- [@article@Stop Vibe Coding Your Unit Tests - Andy Gallagher](https://www.andy-gallagher.com/blog/stop-vibe-coding-your-unit-tests/)
+- [@article@Stop Vibe Coding Your Unit Tests - Andy Gallagher](https://www.andy-gallagher.com/blog/stop-vibe-coding-your-unit-tests/)
@@ -1,8 +1,10 @@
 # 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.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@Role Prompting: Guide LLMs with Persona-Based Tasks - Learn Prompting](https://learnprompting.org/docs/advanced/zero_shot/role_prompting)
 - [@article@Role-Based Prompting - GeeksforGeeks](https://www.geeksforgeeks.org/artificial-intelligence/role-based-prompting/)
- [@article@Prompting Techniques | Prompt Engineering Guide - promptingguide.ai](https://www.promptingguide.ai/techniques)
+- [@article@Prompting Techniques | Prompt Engineering Guide - promptingguide.ai](https://www.promptingguide.ai/techniques)
@@ -2,7 +2,7 @@

 Every time AI completes a task, and the result looks good, make a commit. This locks in your progress so that if the next task breaks something, you can go back to the last working version without losing any of your previous work.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Best Practices for Committing AI-Generated Code - DeployHQ](https://www.deployhq.com/git/committing-ai-generated-code)
 - [@article@Git and GitHub for Vibe Coders - DeepakNess](https://deepakness.com/blog/git-for-vibe-coders/)
@@ -1,8 +1,10 @@
 # Work step by step rather than trying to build all at once

-Build one feature at a time. Ask the AI to do it, test it, make sure it works, then move to the next one. If you ask AI to build too many things at once, things will break, and you won't know why. Small steps make debugging easy because you only changed one thing, so you know exactly where the problem is.
-# Articles
+Articles
+========
+
+Visit the following resources to learn more:

 - [@article@9 Vibe Coding Best Practices - Memberstack](https://www.memberstack.com/blog/9-vibe-coding-best-practices)
 - [@article@How to Vibe Code Effectively - Replit Docs](https://docs.replit.com/tutorials/how-to-vibe-code)
- [@article@Vibe Coding Tips: Checklist to Avoid Breaking Builds - Presta](https://wearepresta.com/vibe-coding-tips-checklist-avoid-breaking-builds/)
+- [@article@Vibe Coding Tips: Checklist to Avoid Breaking Builds - Presta](https://wearepresta.com/vibe-coding-tips-checklist-avoid-breaking-builds/)