Vibe coding glossary: useful working terms

Prompt and acceptance criteria

A prompt is the request or context you give an AI system. Acceptance criteria are observable conditions that define when a task is complete. A prompt can be long and still have unclear acceptance criteria. Prefer statements such as: a signed-in customer can see only their own requests, and a visitor cannot read the administrator list.

Full-stack application

A full-stack app includes a user interface and backend behavior, commonly with persistent data and authentication. The label does not guarantee security, scalability, or correct business rules. Evaluate the specific implementation across its entire user journey.

Authentication and authorization

Authentication establishes identity. Authorization controls access to actions and data. A login screen is not proof that another user's records are protected. Enforce and test permissions on the backend.

Preview and production

A preview is a version used for review or testing. Production is the environment intended for real users. They may have different builds, data, credentials, and operational guarantees. Test the production configuration deliberately before launch.

Static HTML and canonical URL

Static HTML is page content prepared ahead of a visitor's request. For a reference site, it lets readers and crawlers access the text without executing JavaScript. A canonical URL declares the preferred public address for a page. It should agree with internal links, the sitemap, and structured data.

Code ownership and portability

Code ownership concerns the rights granted under applicable terms. Source access concerns obtaining the files. Portability concerns reproducing the running application, including data, assets, configuration, and external dependencies. Verify these separately rather than treating one export button as a complete exit plan.

Browse individual definitions

• Vibe coding: meaning and practical checks

  Building and revising software by describing intended behavior to an AI system and checking the resulting application.

• AI app builder: meaning and practical checks

  A product that uses AI to turn a description into application code or a working app, with varying levels of infrastructure support.

• Prompt-to-app: meaning and practical checks

  A workflow that starts with a natural-language brief and turns it into an application you can review and refine.

• Full-stack application: meaning and practical checks

  An application that includes a user interface and backend behavior, commonly with persistent data and authentication.

• Backend and database: meaning and practical checks

  The backend performs trusted application operations; a database persists structured information used by the application.

• Deployment: meaning and practical checks

  Making a built version of an application available in an environment such as a preview or production service.

• Custom domain: meaning and practical checks

  A domain name selected for a site instead of the hosting platform’s default subdomain.

• Code export: meaning and practical checks

  Obtaining source files from a platform so they can be reviewed, archived, or used in another development environment.

• Agentic coding: meaning and practical checks

  AI-assisted development in which an agent can take actions such as inspecting files, editing code, running commands, and checking results.

• Authentication and authorization: meaning and practical checks

  Authentication establishes who a user is; authorization decides which actions and records that user may access.

Continue reading

Your next useful step.

• Vibe coding for beginners: the learning path
• Full-stack AI apps: architecture learning path
• Deploying AI-built apps: the launch learning path
• AI app builder costs: the buying learning path