Türkçe
Glossary
Key terms for vibe coding and AI-assisted development.
Short definitions. Phase 1: English definitions; we're adding translations per language over time.
- Vibe coding
- Building software with AI as your pair programmer: you describe what you want in plain language or structured prompts, and AI tools generate and refine code. You focus on flow and product; the model handles syntax and boilerplate.Learn more
- Prompt
- The text you give to an AI coding tool (e.g. Claude, Cursor, ChatGPT) that describes what you want built. Good prompts are specific about outcome and user flow, and clear about layout and style when it matters.Learn more
- Blueprint
- A tested, reusable prompt (or prompt template) that reliably produces a whole app or a clear pattern — e.g. a landing page, a blog, a dashboard. VibeShare Blueprints are sold as one-time purchases and work with major AI tools.Learn more
- AI-assisted development
- Software development where AI tools help write, edit, or suggest code. Includes vibe coding, Copilot-style completion, and using LLMs to generate full features or apps from natural language.
- Natural language to code
- Turning descriptions in plain language (e.g. “a waitlist form that saves to our CRM”) into working code via an AI model. The core of vibe coding and prompt-driven app building.
- LLM (large language model)
- An AI model trained on huge amounts of text that can understand and generate natural language and code. Claude, GPT, and similar models power vibe coding tools; they take your prompt and produce or edit code.
- AI coding tools
- Applications that let you prompt an LLM to write or edit code in your project. Examples include Cursor, Claude (Codex/Artifacts), GitHub Copilot, and ChatGPT. Blueprints are designed to work across these tools.
- Prompt engineering
- The practice of writing and refining prompts so an AI produces the result you want. For code: be specific about outcome and user flow, give one clear hero flow, and call out layout when it matters.Learn more
- Iteration
- Repeating cycles of prompt → AI output → feedback → refined prompt. In vibe coding, you often start with a minimal version and add features in small steps (“add a pricing section”) rather than one giant prompt.Learn more
- Design hints
- Structured notes in a blueprint that describe layout, typography, colors, and UX so the generated app matches a consistent look and feel. They reduce generic “AI slop” and improve ship-ready output.Learn more
- Hero flow
- The single main user path you spell out in a prompt (e.g. “Visitor signs up for the waitlist” or “User picks a template and downloads the prompt”). Defining one hero flow gives the model a clear backbone; extra features can follow.Learn more
- MVP (minimum viable product)
- The smallest version of a product that delivers real value and can be shipped. Vibe coding lets solo builders and small teams ship MVPs in hours or days instead of weeks.Learn more
- Add-on
- An optional extension to a VibeShare Blueprint (e.g. dark mode, extra integration) that you can purchase with the blueprint. Add-ons are included in the delivered prompt so the model generates the full spec.Learn more
- No-code / low-code
- Platforms that let you build apps with little or no hand-written code (e.g. drag-and-drop builders, form tools). Vibe coding is different: you still work in code and repos, but AI writes much of the code from your prompts.
- Pair programming
- Two developers working together at one screen. In vibe coding, the “pair” is you and the AI: you describe intent and review output; the model proposes and edits code. You stay in the flow; it handles syntax and boilerplate.