Skip to catalogue

How we check content

Vibe Coding 101 is a glossary for developers who ship with an agent. Each entry should explain a real engineering decision and offer a short prompt whose result you can check.

AI assistance and responsibility

AI tools help draft and revise this glossary. A fluent explanation can still be wrong. Another model's agreement is useful feedback, but it is not independent evidence or human review. We distinguish a source check, an automated example check, and a human editorial review.

What the evidence means

  • Sources on an entry link to standards, original technical explanations, or official documentation. Each source note says what it supports.
  • Before-and-after examples illustrate a specific behavior. Their runnable comparisons check the outcomes shown. They are not production benchmarks or proof that a prompt works with every model.
  • A source-check date records when those references were checked. It does not mean a human reviewed the page on that date.
  • Some short entries do not yet have the same source notes or runnable examples. A catalogue update date does not establish fresh verification of every claim.

Before publication

New or materially changed AI-assisted content needs human editorial review before publication. The editor checks material claims against the linked sources, inspects example results and limitations, and reviews titles, descriptions, image text, and structured data. Automated checks support that review; they do not replace it. We do not display a human reviewer or approval date without a recorded review.

Corrections

If an entry is inaccurate or a prompt misses an important constraint, report a correction with the term, the disputed claim, and a supporting source or reproducible example.

Policy updated . Browse the glossary.