Build Apps with Claude Code (No Coding Skills Required)
Summary of the video “Claude Code Tutorial for Non-Coders” by Kevin Stratvert.
Claude Code is an AI agent that writes code for non-developers. Pick a small, useful project, describe it in plain English, use plan mode to review before building, and leverage features like file visibility and cross-folder access that Cowork lacks. Main tradeoff: Claude Code has fewer guardrails than Cowork, so only use it if you trust the AI with broad machine access.
Core Misconception & What Claude Code Actually Is
Claude Code is not just for developers
Claude Code is a general AI agent that happens to write code. You pick a folder, describe what you want in plain English, and it builds it for you. It runs on the same engine as Claude Cowork but with fewer guardrails.
No terminal or command prompt required
Claude Code runs inside Visual Studio Code or as a desktop app, eliminating the need to use scary-looking terminal windows or command prompts.
How to Pick the Right Project
Three rules for choosing what to build
Keep it small, keep it focused, and make sure it will actually be useful to someone. If you can't say out loud why it's worth building, don't build it. Look for spreadsheet-based tools at work that could become real software.
Step-by-Step Setup & First Build
Initial setup in Visual Studio Code
Open an empty folder using the open folder link, then install the Claude Code extension by clicking Extensions, typing Claude, and installing the official Anthropic version. Open the secondary sidebar to access Claude Code.
Use the @ symbol to reference files
When writing your prompt, use the @ symbol followed by the filename (e.g., @sales-pipeline.xlsx) to tell Claude Code which files to work with. This helps Claude understand your data structure.
Always start in plan mode
Click the hand icon in the bottom right to enable plan mode before running any prompt. This makes Claude show its plan before making changes, allowing you to catch mistakes before it wastes time building the wrong thing.
Interview technique for gathering requirements
In your initial prompt, ask Claude to interview you about anything else it needs to know. This prompting trick ensures Claude asks clarifying questions rather than making assumptions about your needs.
Claude Code Operating Modes
Four different operating modes
Manual mode asks for approval before making changes. Edit automatically handles file changes but asks permission for custom tools. Plan mode shows the plan before building. Auto mode auto-approves actions Claude deems safe.
Switch modes with keyboard shortcut
Hold Shift and press Tab repeatedly to cycle through operating modes without using the menu, making it faster to switch between plan mode and auto mode.
Reviewing Plans & Asking for Clarification
Use the tell Claude what to do box to ask questions
If Claude uses jargon you don't understand in its plan, quote the term and ask what it means. Claude will explain and offer to remove jargon from the plan. You can also request changes before approving.
Teaching Claude to keep things non-technical
When you tell Claude upfront that you're not a developer, it learns to explain things in simpler terms and avoid unnecessary technical jargon in its plans.
Three Reasons to Use Claude Code Over Cowork
Reason 1: File visibility during building
While Claude Code builds, you can see every file it creates in real time in the file explorer. Cowork does not offer this level of visibility inside the app.
Reason 2: Cross-folder access without permission lists
Claude Code can reach across your entire machine to different folders without requiring you to add them to a permission list first. In Cowork, you must explicitly grant folder access, which slows down workflows.
Reason 3: Better environment with advanced commands
Claude Code offers a superior harness with commands like /rewind to roll back code and conversation, /goal to keep prompting until a goal is met, and /stickers. Cowork lacks an explicit plan mode and these advanced commands.
Deployment & Sharing
Apps live on your machine initially
The app you build with Claude Code lives on your local machine and can be opened with a double-click. To share with teammates, copy all created files to their machines.
Team deployment requires IT involvement
If the whole team needs the app, it becomes an IT conversation. The problem to avoid is having to fix issues on every machine individually, which is why better deployment methods exist.
The Big Red Flag: When NOT to Use Claude Code
Claude Code has far fewer guardrails than Cowork
Claude Code runs with close to full access to your machine, unlike Cowork which has extensive safety guardrails. If you're nervous about permanent deletion questions and can't assess whether an action is safe, Claude Code is not for you.
Security and trust are the deciding factors
Only use Claude Code if you trust the AI with broad machine access. If you need the safety net of guardrails, Cowork is the better choice.
Practical Example: Sales Pipeline App
Real-world use case: automating spreadsheet workflows
The example app tracks a sales pipeline, automatically reorganizing folders on a shared drive, gathering documents, and researching accounts when a deal changes stage. This converts manual spreadsheet work into an automated application.
Extending the app with folder management
After building the basic app, Claude Code can be extended to move account folders between prospect and active directories on a shared drive and create required subfolders automatically when deals change stages.
Notable quotes
Claude Code is a general AI agent that happens to write code. — David DeWinter
If you can't say out loud why it's worth building, don't build it. — David DeWinter
Claude runs with close to full access to your machine and far fewer guardrails than Cowork. — David DeWinter
Action items
- Download Claude Code from the link in the description and install the extension in Visual Studio Code
- Open an empty folder in VS Code and install the official Anthropic Claude Code extension
- Identify a small, focused project from your work (ideally a spreadsheet-based tool) that would benefit from automation
- Write your initial prompt using the @ symbol to reference relevant files and ask Claude to interview you about requirements
- Enable plan mode before running any prompt to review Claude's approach before it builds
- Use the tell Claude what to do box to ask for clarification on any jargon or request changes to the plan
- After approval, switch to auto mode to let Claude complete the build without interruptions
- Test the app by interacting with it and verifying that it correctly updates your source files
- Use /rewind command if you want to roll back changes and try a different approach