Skip to content
Agentic Levels
Start hereLevelsTracksPromptsAbout
Get my levelGet my level

  • Start hereYour first useful task with AI.
  • Level quiz8 questions. No AI needed.
  • Fluency ScoreYour Level and a score, from your own AI.

  • LevelsThe 11 levels, in order.
  • LessonsShort lessons, filter by level.
  • TracksGuided paths by tool, role or goal.
  • Set up your AI tool
  • Starter packFree files that help AI remember.

  • PromptsReady prompts to copy and adapt.
  • ChatGPT vs Claude vs GeminiPick the right one for the job.
  • How-tos
  • ReferenceCommands for Claude Code, Codex, Antigravity.
  • ResourcesHand-picked reading and tools.

  • Your progress
  • Your next moveAn interview that picks your next skill.
  • Your next lessonsThe next lessons at your level.
  • Updates

  • Pricing
  • About
  • FAQ & Feedback
  • Work with us
  • How we handle your data
Sign inPreferences
AboutPricingHow-tosPromptsStarter packMy stackHow we handle your data

© 2026 Fuentes Studio

PrivacyTermsRefundsAccessibilityAI content policyCredits
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

←How-to guides
  1. Resources
  2. ›How-to guides

How to use Day-One Prompt Pack

Ten copy-paste prompts for your first week with Claude Code. Each one paired with a success criterion so 'done' is not subjective.

Levels 1 to 2On GitHub

Most beginner prompt lists are vague enough that you build something and have no way to tell if it worked. This pack ships ten concrete prompts (portfolio site, to-do app, landing page, file automation, Chrome extension, habit tracker, screenshot-to-code, email automation, REST API, bug fix) in AL voice. Two of them touch real files or real credentials and carry blast-radius caveats so you do not melt anything on day one.

Before you start

Install Claude Code first. On Mac, Linux, or WSL: curl -fsSL https://claude.ai/install.sh | bash. On Windows PowerShell: irm https://claude.ai/install.ps1 | iex. Alternatives: brew install --cask claude-code (Mac) or winget install Anthropic.ClaudeCode (Windows). Requires a Claude paid plan (Pro or higher). Full setup walkthrough lives in the Claude Code how-to.

  1. 1Confirm Claude Code is installed and you are in a project folder
  2. 21. Personal portfolio site
  3. 32. To-do app with a saved database
  4. 43. Business landing page
  5. 54. Automate a file task (with mandatory dry-run)
  6. 65. Chrome extension that saves highlighted text
  7. 76. Mobile habit tracker
  8. 87. Screenshot to code
  9. 98. Email and notification automation (with credential safety)
  10. 109. REST API backend for a blog
  11. 1110. Fix a bug end to end

Steps

01

Confirm Claude Code is installed and you are in a project folder

Run `claude --version` to confirm install. Then `cd` into the folder where you want today's work to live (a new empty folder is fine). Each prompt below assumes a fresh project unless noted.

02

1. Personal portfolio site

A four-page personal site with a working contact form, in a dark color scheme, mobile-ready. The prompt asks Claude to start it locally and tell you the exact command and URL, so beginners do not get a built site they cannot find. Success: open the site, click between all four pages, resize to phone width without breaking.

Paste into Claude Code
Build a personal portfolio website with four pages: a home page with my name and a one-line bio, an About page, a Projects page showing four project cards as placeholders, and a Contact page with a working form. Use a dark color scheme. Make the layout adjust cleanly on a phone screen. When the site is built, start it locally and tell me the exact command and URL to open it.
03

2. To-do app with a saved database

React frontend, local SQLite so tasks persist between sessions. Four actions plus a status filter and a small completion animation. Success: add a task, mark it done, close the app, reopen, and the task is still there with its status saved (the SQLite part is the actual test).

Paste into Claude Code
Build a to-do list app. Use React for the interface and a local SQLite database so the tasks are saved between sessions. The app needs four actions: add a task, mark a task complete, delete a task, and filter the list by status (all, active, done). Add a small animation when a task is marked complete. When it is built, run it locally and tell me how to open it.
04

3. Business landing page

One-page landing for any business name and what it does. Claude asks for those first so it does not invent a brand. Five sections in order: hero, features, testimonials, pricing, footer. Success: all five sections in order, signup button clickable, three distinct pricing tiers.

Paste into Claude Code
Build a one-page landing page for a business. I will give you the business name and what it does; ask me for those first if I have not said them. The page has five sections in this order: a hero with a headline and a signup button, a features section with three features each with an icon, a testimonials section with three sample reviews, a pricing table with three tiers, and a footer. Use a clear, colorful style. When done, run it locally and tell me how to open it.
05

4. Automate a file task (with mandatory dry-run)

A Python script that organizes a photo folder by year and month from EXIF data. The AL version adds a mandatory preview step before any real move, and a blast-radius caveat (the script moves files on your computer). Success: the preview lists real photo filenames with correct year/month, and after you confirm, photos land in the right subfolders.

Paste into Claude Code
Write a Python script that organizes a folder of photos. For each photo, read the date it was taken from the file's metadata, then move it into a subfolder by year and month, like Photos/2025/March/. First, run it in preview mode: print what it would move, where, without actually moving anything. Show me that output. Only move files after I confirm. Run the preview against my Downloads folder. Blast radius: this script moves files on my computer. Preview first, every time, before any real run. Never point it at a folder I cannot afford to have reorganized.
06

5. Chrome extension that saves highlighted text

Highlight text on any page, save it with the source URL. Popup lists everything saved, with copy-all and clear buttons. The AL version makes Claude give you the exact steps to load it as an unpacked extension, which is the point most beginners get stuck. Success: load it, highlight text on two pages, both appear with correct URLs.

Paste into Claude Code
Build a Chrome extension that saves highlighted text. When I select text on any webpage and trigger the extension, it saves that text along with the page URL. Clicking the extension icon opens a popup listing every saved highlight with its source URL. The popup has two buttons: copy all highlights to the clipboard, and clear the list. When it is built, give me the exact steps to load it as an unpacked extension in Chrome so I can test it.
07

6. Mobile habit tracker

React Native app with three screens: today's habits as a checklist, add-habit screen, weekly streak calendar. The AL version makes Claude walk you through running it in a simulator or on your phone (React Native's run step is the hardest part). Success: add a habit, check it off, the streak calendar shows that day marked.

Paste into Claude Code
Build a React Native app for tracking daily habits with three screens: a home screen showing today's habits as a checklist, an add-habit screen, and a stats screen with a weekly streak calendar. Use a clean, minimal style with soft colors. When it is built, tell me exactly how to run it in a simulator or on my phone, step by step.
08

7. Screenshot to code

Share a screenshot, get a responsive HTML page that matches layout, colors, fonts, spacing. The AL version asks Claude to list anything it could not match exactly and why, turning a vague 'as close as possible' into a real gap report. Success: side by side with the screenshot, layout and colors match, every button and link responds.

Paste into Claude Code (attach a screenshot)
I am sharing a screenshot of a webpage design. Recreate it as a single responsive HTML page. Match the layout, the colors, the fonts, and the spacing as closely as you can. Make every button and link work, even if they just scroll or link to a placeholder. When done, tell me how to open it, then list anything in the screenshot you could not match exactly and why.
09

8. Email and notification automation (with credential safety)

Python script that checks URLs and emails a status summary. The AL version moves URLs and credentials to a config file (the source hardcodes them), requires a Gmail app password (never a real password), adds a blast-radius caveat, and stages 'run once, then schedule' so you verify before automating. Success: summary correctly lists at least one reachable and one unreachable URL, email arrives.

Paste into Claude Code
Write a Python script that checks a list of URLs and emails me a summary of which ones are down or returning errors. Use smtplib for the email. Read the URL list and the email settings from a separate config file, not hardcoded in the script. Include setup instructions for using it with Gmail, including how to create an app password so my real password never goes in a file. First, run it once and show me the email summary it would send. After I confirm that works, give me the steps to schedule it to run each morning. Blast radius: this script sends email on my behalf and needs an email credential. Keep the credential in the config file, never in the script, and never commit the config file anywhere.
10

9. REST API backend for a blog

Node + Express + SQLite, four endpoints (create, read, update, delete posts), real input validation (clear message on bad request), real error handling (proper status codes instead of crashes), and a README with an example request per endpoint. Success: full create-read-update-delete cycle plus a bad-request returns a clear error instead of crashing.

Paste into Claude Code
Build a REST API with Node.js and Express for a simple blog. It needs four endpoints: create a post, read posts, update a post, delete a post. Store posts in a SQLite database. Add input validation so bad requests are rejected with a clear message, and error handling so a failure returns a proper status code instead of crashing. Write a README with setup steps and an example request for each endpoint. When it is built, start it locally and show me one working example request and its response.
11

10. Fix a bug end to end

Paste your full error (including line numbers and file path), Claude does three things in order: explain in plain language, locate the file and line before touching it, fix and tell you how to verify. AL adds 'if unsure, say so' to block confident wrong guesses. Success: the app runs without the error, and you understood the plain-language explanation of what was wrong.

Paste into Claude Code (include the full error)
I am getting an error when I run my app. Here is the full error message: [paste the entire error, including the line numbers and the file path] Do three things, in order: 1. Explain in plain language what is going wrong and why. 2. Tell me which file and line you are going to change, before you change it. 3. Make the fix, then tell me how to run the app again to confirm it works. If you are not sure what is causing it, say so and tell me what extra information would help instead of guessing.

How do you know it worked?

  • Claude Code is installed and `claude --version` reports a version
  • You opened a fresh project folder and ran at least one prompt end to end
  • Three of the ten prompts ran end to end within your first week and hit their stated success criterion
  • Before running the file-mover prompt, you used the dry-run preview to verify what it would move
  • Before running the email automation prompt, your Gmail credentials lived in a config file you never committed

If something looks off

Skipping the dry-run on the file-mover prompt
The file-mover script moves files on your computer. Always run preview first, every time, before any real run. Never point it at a folder you cannot afford to have reorganized.
Hardcoding email credentials anywhere
The email automation prompt explicitly says config file, app password, never commit. If you skip those, your password ends up in plain text in a script that probably ends up in git eventually.
Getting stuck on the Chrome extension load step
The hardest part of #5 is loading the unpacked extension in Chrome, not building it. The prompt asks Claude for explicit load steps. Read those steps before clicking around the extensions page.

See also

  • Claude Code installation and orientation

What you'll do, 11 steps

  1. 1Confirm Claude Code is installed and you are in a project folder
  2. 21. Personal portfolio site
  3. 32. To-do app with a saved database
  4. 43. Business landing page
  5. 54. Automate a file task (with mandatory dry-run)
  6. 65. Chrome extension that saves highlighted text
  7. 76. Mobile habit tracker
  8. 87. Screenshot to code
  9. 98. Email and notification automation (with credential safety)
  10. 109. REST API backend for a blog
  11. 1110. Fix a bug end to end

Was this helpful?