Incorrect password

Vibe

coding

A beginner's guide

How I built a real app without writing every line of code

From zero to the App Store using AI-powered development.

Visit decksense.app DeckSense app

What even is vibe coding?

Using AI tools to build real software by describing what you want, instead of writing every single line yourself.

What it is

  • Describe outcomes; AI drafts structure and boilerplate
  • You review, run, and refine in a tight loop
  • You own product decisions and integration choices

What it is not

  • Not hands-off: quality still needs your judgment
  • Not a license to skip testing or security basics
  • Not instant: real bugs and edge cases still show up

Why it works

  • Models excel at repetition, scaffolding, and refactors
  • Faster cycles mean more experiments per week
  • You learn structure by steering working code

The tools you need

You only need a few things to get started, and most are free.

Cursor AI

IDE + pair programmer

Edit code, chat in context, and apply multi-file changes quickly.

Claude

Reasoning + long context

Plan features, debug errors, and draft specs or prompts.

Expo / React Native

Cross-platform shell

One codebase for iOS and Android with sane defaults.

Firebase

Auth + data + hosting

Backends for login, sync, and serverless glue without running servers.

My project: DeckSense

A competitive Pokemon TCG app, live on the App Store.

Deck builder

Build legal lists fast with search, staples, and export.

Meta analysis

See what wins regionals and how archetypes trend.

Card pricing

Raw and graded signals to support trades and buys.

AI suggestions

Practical tweaks based on your list and format.

Find tournaments

Discover events and stay close to the competitive scene.

DeckSense screenshot DeckSense screenshot

How the process actually works

It is less like programming and more like managing a very fast intern.

01

Have an idea


Start small: one screen, one flow, one measurable outcome.

02

Describe it to AI


Write prompts like specs: inputs, outputs, constraints, and examples.

03

Run the code


Build, run on device or simulator, and collect real error messages.

04

Fix and repeat


Tighten requirements, add tests where it matters, and iterate.

Claude Code: Working Smarter

Most people burn through their token limit because of bad habits, not because they need a bigger plan.

TIER 1

/clear between tasks

Wipe conversation history between unrelated tasks. Message 30 costs 31x more than message 1 because Claude rereads the whole conversation every time.

TIER 1

Use .claudeignore

Exclude node_modules, dist, build, and log folders. If Claude cannot see it, it cannot accidentally read it or bill you for it.

TIER 1

Ask for the answer, not the explanation

Add "just give me the code, no explanation" to your prompts. A concise response can use 60-70% fewer tokens than a fully explained one.

TIER 2

/compact proactively

Run /compact after each completed feature, not when Claude warns you. Compacting on a bloated context generates a worse summary.

TIER 2

Keep CLAUDE.md lean

It gets read on every single message, not just every session. Keep it under 200 lines. Cut anything that does not change how Claude behaves.

TIER 2

Disconnect unused MCP servers

Each connected MCP server adds roughly 18,000 tokens per message silently. Run /context at the start of each session and disconnect what you are not using.

TIER 3

Spawn sub-agents for multi-file tasks

If a task needs 3 or more files analyzed, spawn a sub-agent and only return summarized insights back to your main session.

TIER 3

Reference files explicitly

Instead of "find where we handle auth," say "check src/auth/middleware.ts, specifically validateToken." Vague exploration triggers multi-file reads.

TIER 3

Rate limits are rolling, not daily

Your quota does not reset at midnight. It is a rolling window. Tokens you used 5 hours ago start becoming available again, so plan your heavy sessions accordingly.

How to Code From Your Phone

Claude Code runs in your terminal. If you can access your terminal remotely, you can code from anywhere, including your phone.

01

Install Claude Code


Open your terminal and run: npm install -g @anthropic-ai/claude-code then run claude to authenticate. Claude Code lives in your terminal and connects directly to Anthropic's API. No separate app needed.

TERMINAL
npm install -g @anthropic-ai/claude-code
claude
02

Access From Anywhere


Use a tool like SSH, Termius, or Tailscale to connect to your computer remotely from your phone. Once connected, you are in your actual terminal, and Claude Code works exactly the same way it does on your laptop.

Tailscale is the easiest option: it creates a private network between your devices. Free tier is enough. Install it on your computer and phone, then SSH in using your machine's Tailscale IP.

03

Claude Code Remote Control


Anthropic built a Remote Control feature into Claude Code specifically for mobile use. Activate it in your Claude Code session with /rc. It opens a web interface you can control from any browser, including Safari on your phone.

This is how DeckSense was built away from the desk. Start a task on your laptop, then pick it up on your phone during a commute or between classes.

A real example

CURSOR PROMPT
Build a "Meta Decks" screen for my Expo app. Fetch GET /api/meta/analysis?range=30d. Show a scrollable list sorted by usage: deck name, usage %, win rate, and up to 3 tags per row. Use my existing dark theme and loading/error states. No new dependencies.
Meta decks screen Meta decks detail or state

Full working screen
Live tournament data
Sorted by usage
Done in roughly 15 minutes

What you learn (even without writing code)

Vibe coding is not a shortcut, it is a different path to the same skills.

How apps are structured

Screens, navigation, state, and data flow start to click.

How to debug

You read stack traces, logs, and repro steps like a builder.

How to think like a developer

You break problems into smaller, testable pieces.

How to ask good questions

Clear prompts and constraints get better answers.

How to ship

You learn versioning, builds, and what good enough means.

What real products need

Auth, errors, empty states, and performance are part of the job.

Challenges and honest takeaways

It is not all smooth sailing. Here is what actually trips people up.

Hard

Context limits and drift

Long projects need discipline: summaries, files, and checkpoints.

Real talk

Overconfidence on first draft

Generated code looks done before it is verified end to end.

Lesson

Unknown unknowns

You still discover platform quirks, APIs, and store rules the hard way.

Hard

Security and secrets

Keys belong out of the client; reviews catch mistakes late if you rush.

Real talk

Design debt

Fast UI stacks up; polish takes intentional passes.

Lesson

Shipping beats perfect

Small releases teach you more than endless refactors.

How to get started this week

Three concrete steps. No excuses.

Step 1

Install the toolchain


  • Install Cursor
  • Create a free Expo project
  • Run it in the simulator

Step 2

Build one tiny feature


  • Pick a screen you can finish in one sitting
  • Prompt for UI + data shape first
  • Ship a screenshot, not a novel

Step 3

Publish a build


  • Use EAS or your host of choice
  • Fix the first real crash you see
  • Note what you would prompt next time

Go Further: Get Certified

Anthropic launched its first official technical certification in March 2026. If you are serious about building with AI, this is the credential that validates it.

Claude Certified Architect: Foundations (CCA)

FORMAT

60 scenario-based questions, 120 minutes, proctored

COST

Free for the first 5,000 Partner Network members, then $99 per attempt

LAUNCHED

March 12, 2026. Anthropic's first official technical credential

This is not a trivia quiz about API parameter names. Every question drops you into a real production scenario and asks you to make the right architectural call. Agentic loops, multi-agent orchestration, MCP tool integration: the depth is real.

What the Exam Tests

Agentic Architecture and Orchestration
27%
Claude Code Configuration and Workflows
20%
Prompt Engineering and Structured Output
20%
Tool Design and MCP Integration
18%
Context Management and Reliability
15%

How to Prepare

STEP 1

Anthropic Academy (Free)


13 free self-paced courses on Skilljar: no paywall, no subscription. Start with Claude 101 and AI Fluency, then move to Building with the Claude API (8.1 hours; this is the core material). Finish with the MCP and Claude Code courses.

STEP 2

Join the Claude Partner Network


The certification is currently available through the Claude Partner Network, which any organization can join for free. The first 5,000 partner employees get access at no cost. Joining also gets you early access to every new certification tier as Anthropic releases them through 2026.

STEP 3

Build Production Projects


The exam tests real architecture decisions, not memorized facts. Candidates who have built actual agentic systems, worked with MCP integrations, and shipped Claude Code workflows have a significant advantage. Building DeckSense is exactly the kind of experience that prepares you for this exam.

Why This Matters for Vibe Coders

Building DeckSense using Claude Code, Cursor, and Expo Router already covers Domain 3 (Claude Code) and Domain 4 (Prompt Engineering) of the exam in practice. If you go on to wire up MCP servers, design agentic suggestion pipelines, or build multi-agent workflows, you are covering Domains 1 and 2 as well. The certification is the official way to prove that work means something.

30,000+
Accenture professionals being trained on Claude
350,000
Cognizant employees with Claude access globally
$100M
Anthropic's 2026 investment in partner training

You don't need to know how to code.

You just need to know what you want to build.

Check out DeckSense at decksense.app

Aidan Lowell · decksense.app · @decksense

Questions?