start here

Getting started with Claude Code

How to configure Claude Code

Model settings

For the best experience building Skape apps, we recommend using Opus with medium thinking effort. In a Claude Code session, type:

> /model (select opus)
> /effort (select medium)

These settings use more of your usage quota but produce significantly better results, especially for building complete apps from scratch. If you find you run out of Claude usage frequently, try using Claude in plan mode with Opus to create a plan, then switch the model to Sonnet to implement it.

Quick tips

Example session

Here's what a real session looks like — from first prompt to working app, including fixing bugs along the way. The prompts below are what we would suggest typing into claude.

First - tell claude to build the app. Include any details you know about what you want, but don't stress that you have to get everything right - you'll iterate with Claude as you go.

> on Skape, build me a todo app. I want to see 7 items max in the list at a time, and have a separate "plan" tab showing everything that isn't in the top 7. There should be buttons to switch items back and forth between plan and current tabs.

Claude reads the Skape instructions, asks you questions to clarify what you want, and creates an app called "my-todos", writes the HTML, CSS and JavaScript, and deploys it. You get a live URL as soon as claude finishes working. The app shows up with an input field and an add button — a clean, working todo list.

Now, let's say you want to add some features - how would you do that? Just ask claude to add those features, like so:

> add confetti when I complete a task

Claude adds a confetti animation. Check a task off and colorful confetti bursts from the checkbox.

Now, what if you find a bug? Again, just describe the bug - the steps you took that resulted in the bad behavior, and then describe what you want the correct behavior to be

> the confetti fires when I uncheck a task too — it should only fire on completion

Claude fixes the code to check whether the task is being checked (not unchecked) before triggering confetti. A quick redeploy and the bug is gone.

That's the loop: describe what you want, Claude builds it, you try it out, and you tell Claude what to fix or add next. No need to write code yourself.

Ready to start?

Head back to the build steps to sign up and connect Claude Code to Skape.

Get started