vibecoded.fyi

About vibecoded.fyi

Tue, 14 Jul 2026 00:00:00 +1000

vibecoded.fyi is a free badge service and editorial project for software built with AI coding tools.

The badges make AI involvement visible in a README. The guides explain practical ways to direct, test, review, and disclose AI-generated software. The showcase follows the badges into public repositories and writes independent profiles from evidence.

What the badge means

“Proudly Vibe Coded” says that natural-language direction, code generation, or coding agents materially shaped a project. It is not a security certification, quality score, sponsorship, or endorsement.

AutoBS: A Vibe Coded Go CLI for GitHub and Jira Updates

Tue, 14 Jul 2026 00:00:00 +1000

AutoBS is an independently maintained Go command-line tool with a practical target: turn a developer’s daily GitHub activity into useful Jira comments or a stand-up summary. Its README also makes an unusually direct disclosure about its construction—the maintainer describes it as a deliberately AI-managed experiment and displays three vibecoded.fyi badges.

This is independent editorial coverage based on the public repository snapshot linked below. It is not an endorsement, security review, or collaboration with the maintainer.

Editorial Policy

Tue, 14 Jul 2026 00:00:00 +1000

vibecoded.fyi publishes practical guides and independent profiles of public repositories using its badges. This policy defines the evidence and disclosure expected for that work.

Repository profile eligibility

An editorial profile must cover a public repository that currently displays a vibecoded.fyi badge and provides enough documentation or history for a useful article. Badge proof is pinned to a specific commit before publication.

Evidence and attribution

Project claims must be supported by public repository material, primary documentation, a reproducible observation, or an attributed maintainer statement. Articles link to the repository and pinned badge evidence and record the review date.

How to Add a Vibe Coding Badge to a GitHub README

Tue, 14 Jul 2026 00:00:00 +1000

A README badge is a compact way to disclose that AI tools materially contributed to a project. vibecoded.fyi serves static SVG badges that work in GitHub Markdown without JavaScript or an account.

Copy a badge from the gallery

Open the badge gallery, choose a style, and use the Copy button. The copied Markdown includes the image and a link back to vibecoded.fyi so readers can understand the badge.

[![Proudly Vibe Coded](https://vibecoded.fyi/badges/flat/main/proudly-vibe-coded.svg)](https://vibecoded.fyi/)

Paste it near the top of README.md, usually alongside build, release, or license badges. Commit and push the change, then verify that GitHub renders the image.

How to Choose a Vibe Coding Tool

Tue, 14 Jul 2026 00:00:00 +1000

The best vibe coding tool is not the one with the longest feature list. It is the one whose working model matches your project, experience, and risk. Start by choosing the kind of control surface you need, then evaluate individual products against the same evidence-based criteria.

Four useful tool shapes

Conversational app builders

Browser-based builders turn a description into a hosted interface or application. They are strong for rapid visual feedback and low setup. Check how easily the generated project can be exported, whether deployment is tied to one vendor, and where user data is stored.

How to Vibe Code Without Losing Control

Tue, 14 Jul 2026 00:00:00 +1000

The fastest way to lose control of an AI-built project is to begin with a vague request, accept a large unexplained change, and postpone testing until the end. A safer workflow keeps each step observable and reversible.

1. Write the outcome before the prompt

Start with a small brief containing:

who the feature is for;
what they should be able to do;
what must not change;
privacy, security, accessibility, and platform constraints;
examples of success;
commands that prove the result works.

This is not bureaucracy. It gives the agent a target and gives you a way to recognise drift.

Vibe Coding Security Checklist

Tue, 14 Jul 2026 00:00:00 +1000

AI-generated code can be useful and still be unsafe. Models optimise for a plausible completion of the request; they do not carry accountability for your users, credentials, or production systems. Use this checklist before a vibe-coded project handles real data or real consequences.

Secrets and configuration

No API keys, passwords, tokens, private URLs, or sample credentials are committed.
Secret files are excluded from version control and build artifacts.
Browser code receives only values safe to expose publicly.
Logs and error responses redact credentials and personal data.
Deployment secrets use the host’s protected secret store.

Search both the current tree and commit history. Removing a secret from the latest file does not invalidate an exposed credential; rotate it.

Vibe Coding vs AI-Assisted Coding

Tue, 14 Jul 2026 00:00:00 +1000

“Vibe coding” and “AI-assisted coding” overlap, but they emphasise different working relationships. AI-assisted coding usually leaves the human in direct control of implementation. Vibe coding delegates more of that implementation and steers through intent, behavior, and feedback.

The practical difference

In AI-assisted coding, a developer might request a function, accept autocomplete, ask for an explanation, or generate tests while continuing to design and edit the surrounding code directly.

In vibe coding, the human more often asks for an outcome—“add account export,” “make this mobile layout work,” or “trace and fix this failure”—then evaluates a multi-file result. The conversation becomes the primary programming interface.

What Is Vibe Coding? A Practical Definition

Tue, 14 Jul 2026 00:00:00 +1000

Vibe coding is a way of building software by describing intent to an AI system, running what it produces, and steering the result through conversation. The person remains responsible for deciding what to build and whether it works, but may write little of the implementation directly.

The phrase is useful because it names a real change in interface. Instead of translating every idea into syntax, a builder can describe a feature, inspect the behavior, report what is wrong, and ask an agent to revise several files at once.