Where to Go from Here

Twenty-four chapters. One website. A toolkit of skills that didn't exist for you a few weeks ago. Let's take stock of what you've actually learned. Then let's talk about what comes next. ## What You Can Do Now You went from "what's a terminal?" to building and publishing a real website. Along the way, you picked up a set of skills that extend far beyond web development: - **Communicate with an AI** that works on your actual computer and files - **Give clear instructions** that produce the results you want - **Iterate** on ideas quickly through description and feedback - **Organize** a project so it stays manageable as it grows - **Automate** tedious tasks by describing what you want done - **Debug** problems by describing symptoms and reviewing fixes - **Save and version** your work so you never lose progress - **Publish** results to the internet None of these skills require you to know how to code. They require you to know what you want and describe it clearly. That's a skill. And it's one that keeps getting more valuable. ## What to Build Next Your personal website is a starting point. A few directions to grow: **Extend your website:** - Add a blog (Claude can set up a simple blog structure) - Build a portfolio gallery with images - Create a resources page with tools you recommend - Add a newsletter signup form **Automate your work:** - Weekly report generation from spreadsheets - File organization for downloads or photos - Email template generation from a contacts list - Data cleanup for messy exports **Build a tool:** - A simple calculator or converter for something specific to your work - A dashboard that displays information from files or data sources - A template system for documents you create regularly **Help your team:** - Create CLAUDE.md files for team projects - Build custom commands for recurring tasks - Set up rule files for team standards The pattern is always the same: identify something worth building or automating, describe it to Claude Code, iterate until it works. ## Growing Your Skills Three areas where you can deepen your Claude Code practice: **Better prompting.** You'll naturally get better at giving instructions. The more you use Claude Code, the more intuitive it becomes to describe what you want precisely. Pay attention to which instructions work well and which need multiple rounds. **More sophisticated CLAUDE.md and rules.** As your projects grow, so will your instruction files. You'll develop project templates, standard rules, and command libraries that you reuse across projects. **MCP connections.** MCP (Model Context Protocol) lets Claude Code connect to external services. Databases, APIs, cloud storage. We touched on databases in Module 5. The list of available connections keeps growing. Check what new connections are available as you need them. ## claude.ai vs. Claude Code: A Reminder You now have two ways to work with Claude: **claude.ai (web chat):** Open in any browser. Great for quick questions, brainstorming, writing drafts, explaining concepts, analyzing documents you paste in. **Claude Code (terminal):** Works on your computer's files. Great for building things, automating tasks, organizing files, managing projects. Use both. Ask claude.ai "what should my about page say?" then tell Claude Code to implement it. Use claude.ai to brainstorm project ideas, then use Claude Code to build them. They complement each other. Web chat for thinking. Claude Code for doing. ## Many Ways to Access Claude Code Throughout this guide, I used Claude Code in the terminal. But that's not your only option. Claude Code is available in multiple forms: **Terminal (what I used):** The command-line interface. Most powerful and flexible. Works on Mac, Windows, and Linux. **[VS Code extension](https://claude.com/product/claude-code):** Claude Code integrated directly into VS Code. Same capabilities, but inside your code editor. **[JetBrains plugins](https://claude.com/product/claude-code):** For developers using IntelliJ, PyCharm, or other JetBrains IDEs. **[Web interface](https://claude.com/product/claude-code):** Access Claude Code through your browser without installing anything locally. Pick whatever feels most comfortable. The terminal gives you the most control, but the IDE integrations might feel more familiar if you're already using those tools. ## Alternative: Claude Cowork If the terminal still feels uncomfortable, there's another option. **[Claude Cowork](https://claude.com/product/cowork)** is a visual interface for working with files - no terminal required. You drag in files, describe what you want, and Claude works on them in a sandboxed environment. It's designed for knowledge work: organizing documents, analyzing research, creating reports, processing data. The same AI capabilities, but through a graphical interface instead of a command line. **Note:** At the time of writing this guide, Claude Cowork is only available on macOS as a research preview. Check the [product page](https://claude.com/product/cowork) for current availability. Claude Code gives you more power and flexibility. Cowork gives you more comfort. Both work. Use whatever fits your style. ## The Bigger Picture You started this guide as someone who wanted to build something but didn't know how to code. You're ending it as someone who can build things by describing them. That's not a minor shift. For decades, the ability to create digital things was gated behind programming knowledge. You either learned to code or you hired someone who could. There was no third option. Now there is. You describe what you want. An AI builds it. You review, refine, and direct. The bottleneck isn't technical skill anymore. It's clarity of thought and quality of communication. Which means the most valuable skill isn't knowing React or Python or SQL. It's knowing what should exist, for whom, and why. Product thinking. Design thinking. The kind of thinking that's always been valuable but now has a direct path to execution. ## One Last Thing The website you built in Module 4 is ready to publish. We covered the hosting options - you can put it live whenever you want. You did that by typing English into a text window. No bootcamp. No coding tutorial. No months of learning syntax and debugging semicolons. Go build something else. Something useful. Something fun. Something you've been wanting to make but didn't think you could. You can.

What You Can Do Now

What to Build Next

Sign In to Unlock

Check Your Email