Skip to content

Resources & Next Steps

You’ve completed the starter pack. You have a portfolio with real projects, a working vocabulary, and the confidence to build things. Here’s where to go from here.


The best way to improve is to keep shipping. Here are project ideas that build on what you’ve learned:

  • A font pairing tool — similar to your palette generator but for typography
  • A design system documentation site — showcase your own components and tokens
  • A client project landing page — use your Phase 2 skills for real work
  • A blog or writing site — learn content management and dynamic pages
  • A small SaaS tool — add user accounts, databases, and payments (this is the deep end — take it slow)

  • Be specific about dimensions, spacing, and colors (you already do this naturally)
  • Reference existing patterns: “Make it look like the card component we built earlier”
  • Break complex features into smaller requests
  • When something isn’t right, describe what’s wrong rather than guessing at the fix
  • Start noticing patterns in the code your AI generates
  • HTML = structure (what’s on the page)
  • CSS = style (how it looks)
  • JavaScript = behavior (what it does)
  • You don’t need to write code from scratch — but reading it helps you give better prompts

Vibe coding gets you far, but there are moments where understanding the fundamentals helps:

  • When the AI gives you something that’s almost right and you want to tweak one line
  • When you’re debugging and need to understand an error message
  • When you want to build something more complex (user accounts, databases, APIs)

Recommended starting points:


  • Kiro — AI-powered development environment
  • Cursor — VS Code fork with AI built in
  • GitHub Copilot — AI pair programmer
  • Replit — browser-based coding with AI
  • v0 by Vercel — generate UI components from descriptions
  • Vercel — deploy frontend projects instantly
  • Netlify — similar to Vercel, great free tier
  • GitHub Pages — free hosting for static sites

  • [Designer + Developer crossover communities on Discord]
  • [Twitter/X #vibecoding hashtag]
  • Dev.to — friendly developer community with design-focused content
  • Indie Hackers — people building and shipping side projects

  • You don’t need to know everything. You need to know enough to describe what you want.
  • Errors are feedback, not failure. Every developer sees errors daily. It’s part of the process.
  • Ship imperfect things. A live project with rough edges teaches you more than a perfect project that never launches.
  • Your design skills are a superpower. Most developers struggle with the visual and UX decisions that come naturally to you.
  • Keep the loop tight. Describe → review → refine. That’s it. That’s the whole method.

Five weeks ago, you’d never written a line of code. Now you have:

  • A working tool on the internet
  • A polished landing page
  • A portfolio showcasing your work
  • The vocabulary and confidence to keep going

You’re not “learning to code.” You’re a designer who builds. There’s a difference.

Keep shipping. ✨