diff --git a/assets/beyond-vibe-coding/images/comic/cdn-urls.md b/assets/beyond-vibe-coding/images/comic/cdn-urls.md
index 05c149b..ab2944b 100644
--- a/assets/beyond-vibe-coding/images/comic/cdn-urls.md
+++ b/assets/beyond-vibe-coding/images/comic/cdn-urls.md
@@ -11,5 +11,5 @@
 | understand-code-first-dialog.jpeg | https://cdn.banatie.app/blog/henry-devto/img/c0c3ad3d-13ee-4dbf-9f4a-5db3bf64b378 | ✓ |
 | works-but-dont-understand.jpeg | https://cdn.banatie.app/blog/henry-devto/img/25589837-6cf0-4ee9-bb2f-121ee3edac7d | |
 | infographic/Generated Image January 31, 2026 - 11_11PM.jpeg | https://cdn.banatie.app/blog/henry-devto/img/1175042e-1e41-4675-8fb3-25febe7cedea | ✓ |
-| **DO-DONT-vibe-coding-infographic** | нужно создать | |
+| infographic/DO-DONT-vibe-coding.jpeg | https://cdn.banatie.app/blog/henry-devto/img/c5735016-326f-48f6-b8b7-cb35890739a8 | ✓ |
 | **robots-flesh-bag-comic** | нужно создать | |
diff --git a/assets/beyond-vibe-coding/images/infographic/Generated Image February 01, 2026 - 11_43PM.jpeg b/assets/beyond-vibe-coding/images/infographic/Generated Image February 01, 2026 - 11_43PM.jpeg
new file mode 100644
index 0000000..449ac49
Binary files /dev/null and b/assets/beyond-vibe-coding/images/infographic/Generated Image February 01, 2026 - 11_43PM.jpeg differ
diff --git a/assets/beyond-vibe-coding/text-p1.md b/assets/beyond-vibe-coding/text-p1.md
index cb30ebe..dc8450f 100644
--- a/assets/beyond-vibe-coding/text-p1.md
+++ b/assets/beyond-vibe-coding/text-p1.md
@@ -50,6 +50,8 @@ On the other hand, there are pitfalls. 27% of companies have banned AI tools at
 
 Be careful with security. Don't use vibe coding on critical infrastructure. Especially where you can't easily roll back changes.
 
+![Infographic: Vibe Coding DO and DON'T - when to use and when to avoid](https://cdn.banatie.app/blog/henry-devto/img/c5735016-326f-48f6-b8b7-cb35890739a8)
+
 You might ask — is it even legitimate to use vibe coding at work? Absolutely! First, you save significant energy on simple things. Your brain resources are limited — delegate simple tasks and routine to AI. It'll do it faster, and you can spend your focus on more important stuff. Second, techniques exist beyond vibe coding that significantly improve development quality and reliability.
 
 So what are these methods?
diff --git a/assets/beyond-vibe-coding/text.md b/assets/beyond-vibe-coding/text.md
index 09ea679..a7a092e 100644
--- a/assets/beyond-vibe-coding/text.md
+++ b/assets/beyond-vibe-coding/text.md
@@ -47,7 +47,7 @@ Does it produce bad code? Maybe, but there are simple ways to improve quality:
 
 On the other hand, there are pitfalls. 27% of companies have banned AI tools at least temporarily over privacy and security concerns. Apple restricted ChatGPT and Copilot. Amazon banned ChatGPT after discovering responses resembling internal data. Samsung had an employee leak confidential information through ChatGPT. Be careful with security. Don't use vibe coding on critical infrastructure. Especially where you can't easily roll back changes.
 
-[IMAGE: simple DO and DON'T infographic for vibe coding]
+![Infographic: Vibe Coding DO and DON'T - when to use and when to avoid](https://cdn.banatie.app/blog/henry-devto/img/c5735016-326f-48f6-b8b7-cb35890739a8)
 
 You might ask — is it even legitimate to use vibe coding at work? Absolutely! First, you save significant energy on simple things. Your brain resources are limited — delegate simple tasks and routine to AI. It'll do it faster, and you can spend your focus on more important stuff. Second, techniques exist beyond vibe coding that significantly improve development quality and reliability.