Vibe Coding — The How-To Guide.
Objective
Learn the mechanics of getting AI to write code for your projects — safely, with guardrails, and with developer review. Everything a non-developer needs to know before their first vibe coding session.
Watch the Session
Dhwani RIS members only
Pre-Reading Checklist
Access to platform.dhwaniris.in (Deploy Control)
Your repo name confirmed with a developer
CLAUDE.md set up in your repo (or ask a dev to create it)
Security_DRIS.md ready to attach to your session
Working on a feature branch — never on main or develop
Key Concepts
Getting a GitHub Token
Tokens let AI push code to a repo. For org repos, use Deploy Control. For personal repos, use GitHub Settings.
- Log in at
platform.dhwaniris.in - Click the GitHub Token tab
- Enter the exact repo name — confirm with your developer first
- Click Generate Scoped Token
- Copy immediately — it expires in 1 hour
Lifetime1 hourScopeSingle repo onlyPermissionsRead + WriteThe Two Key Files
CLAUDE.md — The AI's memory for your project. Lives in the root of your repo. Update at the end of every session. No CLAUDE.md = AI starts from scratch.
Security_DRIS.md — Dhwani RIS security rules for AI-generated code. Attach to every session — no exceptions. Without it, AI has no guardrails.
When to Use Which Tool
Claude CodeBuilding features, multi-file tasks, Frappe work. Pushes code directly.Claude UIDrafting, planning, reviewing logic. Hand off to dev for code changes.CodexQuick scripts, Python utilities, second opinions.Walkthrough — Writing Better Prompts
Be specific. Not "add a field" but "add a Currency field called sanctioned_amount to the Grant doctype, visible in the main form, not mandatory."
Provide context. Paste error messages. Describe what already exists. Mention the doctype or module.
One task at a time. Break large requests into smaller steps. Review output before asking for the next step.
Always reference CLAUDE.md. It gives AI project context without you explaining everything each time.
Ask the AI to explain. You don't need to understand the code — but you should understand the intent.
Common Mistakes
Wrong repo name for token — no validation. Fails silently or pushes to the wrong place.
Reusing expired tokens — always generate fresh. They last 1 hour.
Skipping Security_DRIS.md — AI won't follow Dhwani security standards without it.
Not updating CLAUDE.md — next session starts from scratch.
Pushing to main or develop — always feature branch. Always raise a PR.
The Golden Rule
All AI-produced code must go through a pull request. A developer reviews and merges — never push directly. Pair with a developer for your first 2-3 sessions.
Further Reading
Official guide on writing better prompts for Claude.
What "vibe coding" really means. A balanced take for non-developers.