Vibe coding blogs (Set 2)

[Veera-mulge]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• New Features
  • Published a new blog post introducing context engineering with practical guidance, common challenges and fixes, FAQs, and resource links; includes article metadata for display.
  • Published a new blog post showcasing 10 “vibe coding” examples with descriptions, tooling recommendations, FAQs, and resource links; includes article metadata for display.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request adds two new static blog post pages as Markdoc/Markdown files with YAML front-matter: src/routes/blog/post/context-engineering-intro/+page.markdoc (intro to context engineering vs. prompt engineering) and src/routes/blog/post/examples-of-vibe-coding/+page.markdoc (10 vibe coding examples). Each file includes metadata fields (layout, title, description, cover, timeToRead, date, author, callToAction, unlisted, category) and structured content (headings, lists, links, FAQs, resources). No executable code, exported declarations, or public API changes are introduced.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Validate YAML front-matter formatting and sensible metadata values
• Check Markdoc/Markdown syntax (headings, lists, links, images)
• Verify internal/external links and cover asset paths resolve
• Confirm consistency with existing blog post formatting and metadata conventions

Files to review:

• src/routes/blog/post/context-engineering-intro/+page.markdoc
• src/routes/blog/post/examples-of-vibe-coding/+page.markdoc

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Vibe coding blogs (Set 2)" is partially related to the changeset. The PR adds two new blog posts: one on "context engineering" and one on "10 best vibe coding examples." The title directly refers to the vibe coding blog post, which is a real and significant aspect of the changes, though it doesn't capture the full scope of the PR since the context engineering blog post is not mentioned in the title. The phrase "(Set 2)" appropriately indicates this is part of a series of related additions.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf5aa41 and 4e5e48d.

📒 Files selected for processing (1)

• src/routes/blog/post/examples-of-vibe-coding/+page.markdoc (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 5

🧹 Nitpick comments (3)

src/routes/blog/post/context-engineering-intro/+page.markdoc (3)

1-12: Consider title case for consistency.

The title uses lowercase "intro" which may be intentional for a casual tone, but "Context Engineering Intro" would follow more conventional title case formatting.

---

15-15: Consider punctuation for clarity.

The comma before "the natural next step" could be replaced with an em dash (—) or colon (:) for better readability: "That's where context engineering comes in—the natural next step after prompt engineering."

---

21-21: Consider a more specific heading.

The heading "Context engineering intro" echoes the page title. Consider alternatives like "What is context engineering?" or "Overview" to avoid redundancy and add clarity.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 967af34 and 09c9a79.

⛔ Files ignored due to path filters (2)

• static/images/blog/context-engineering-intro/cover.png is excluded by !**/*.png
• static/images/blog/examples-of-vibe-coding/cover.png is excluded by !**/*.png

📒 Files selected for processing (2)

• src/routes/blog/post/context-engineering-intro/+page.markdoc (1 hunks)
• src/routes/blog/post/examples-of-vibe-coding/+page.markdoc (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build
• GitHub Check: tests

🔇 Additional comments (8)

src/routes/blog/post/context-engineering-intro/+page.markdoc (3)

43-54: LGTM!

The comparison table is clear, well-structured, and effectively illustrates the differences between prompt engineering and context engineering.

---

76-111: LGTM!

The challenges section is well-structured with clear problem statements and actionable fixes. The format effectively helps readers identify and address common issues.

---

132-136: LGTM!

Concise and effective conclusion that reinforces the core message without being repetitive.

src/routes/blog/post/examples-of-vibe-coding/+page.markdoc (5)

1-12: LGTM!

Front matter is properly structured with all required metadata fields.

---

13-17: LGTM!

Strong introduction that clearly sets expectations and establishes the blog's purpose.

---

103-120: LGTM!

The FAQ section effectively addresses common questions and provides helpful context about vibe coding timelines and best practices.

---

121-125: LGTM!

Effective conclusion that reinforces the key takeaway without being repetitive.

---

19-102: Review external link that returned HTTP 429 rate-limiting response.

Verification of external URLs shows 9 out of 10 links are accessible. However, https://www.flowbound.app/ (used for "Found My Focus") returned HTTP 429 (Too Many Requests), indicating potential rate-limiting or temporary server overload.

All other links verified successfully:

• ✓ refetch.io
• ✓ mealmuse.ai
• ✓ app.thestorypot.com
• ✓ timelessmemories.me
• ✓ chores-ai.com
• ✓ mixcard.me
• ✓ stories-of-life.vercel.app
• ✓ noratutor.xyz
• ✓ careercloud.io

Manually verify flowbound.app is accessible before publishing, as the HTTP 429 response may be transient. If the site has aggressive rate-limiting, consider testing from a different network or time period.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09c9a79 and bf5aa41.

📒 Files selected for processing (2)

• src/routes/blog/post/context-engineering-intro/+page.markdoc (1 hunks)
• src/routes/blog/post/examples-of-vibe-coding/+page.markdoc (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/routes/blog/post/context-engineering-intro/+page.markdoc

🔇 Additional comments (1)

src/routes/blog/post/examples-of-vibe-coding/+page.markdoc (1)

23-23: Clarify the phrasing for better readability.

The phrase "an open-source alternative to Hacker News controlled by YC" is ambiguous. It's unclear whether "controlled by YC" modifies "Hacker News" or "alternative." Consider rephrasing for clarity.

Suggested alternatives:

-This one's interesting. [Refetch](https://refetch.io/) is an open-source alternative to Hacker News controlled by YC. Using Refetch, you can explore the latest tech discussions and news.
+This one's interesting. [Refetch](https://refetch.io/) is an open-source alternative to Hacker News (which is run by YC). Using Refetch, you can explore the latest tech discussions and news.

Or more concisely:

-This one's interesting. [Refetch](https://refetch.io/) is an open-source alternative to Hacker News controlled by YC. Using Refetch, you can explore the latest tech discussions and news.
+This one's interesting. [Refetch](https://refetch.io/) is an open-source, YC-independent alternative to Hacker News. Using Refetch, you can explore the latest tech discussions and news.

⛔ Skipped due to learnings

Learnt from: abnegate
Repo: appwrite/website PR: 2233
File: src/routes/blog/post/add-figma-oauth2-appwrite/+page.markdoc:111-116
Timestamp: 2025-08-29T11:10:36.214Z
Learning: Do not provide review comments on code examples found in documentation, tutorials, blog posts, or other educational content. These examples prioritize clarity and learning over optimization.