Skip to content

Claude Code Projects: 20 Ideas for Non-Developers (2026)

Claude Code projects for non-developers: 20 ideas from one-hour wins to weekend builds, each with the outcome, the difficulty and the first prompt to send.

By Yotam DahanUpdated 11 min readClaude Code

On this page
  1. How to pick your first project
  2. One-hour projects
  3. Half-day projects
  4. Weekend projects
  5. What to do next

The best Claude Code projects for non-developers produce one thing you can see and use, such as a web page, a spreadsheet or a small tool, within a single sitting. Below are 20 ideas sorted by time, from one-hour wins to weekend builds, each with the outcome, the difficulty and the exact first prompt to send. Pick one you will use this week, because a project with a real use is much easier to finish.

How to pick your first project

  • Pick something you will use this week. A link page for your profile beats an app you might need someday.
  • Choose one thing you can see. A page, a file or a table makes it obvious whether Claude got it right.
  • Start in an empty folder. Make a new folder for each project and open Claude Code there, so nothing else gets touched.

New to the tool? Do the walkthrough in how to use Claude Code first, then come back for your second project.

#ProjectTimeDifficultyNeeds beyond Claude Code
1Personal link page1 hourEasyA browser
2Printable customer guide1 hourEasyA browser
3Team email signature1 hourEasyYour email app
4Meeting notes to action list1 hourEasyA transcript
5Family recipe page1 hourEasyA browser
6Reading digest1 hourEasyArticle links
7Service price calculatorHalf dayMediumA browser
8Product recommendation quizHalf dayMediumA browser
9Flashcards from notesHalf dayMediumA browser
10Habit trackerHalf dayMediumA browser
11Event page with calendar fileHalf dayMediumA browser
12Chrome extensionHalf dayMediumGoogle Chrome
13Application tracker boardHalf dayMediumA browser
14Four-page business websiteWeekendHarderA hosting account
15Morning industry digestWeekendMediumThe Claude desktop app
16Your own skill packWeekendMediumNothing extra
17Notion weekly reviewWeekendMediumA Notion connection
18Dashboard from a Google SheetWeekendHarderA Google Sheet
19Browser game or quiz nightWeekendEasyA browser
20Team onboarding hubWeekendMediumYour documents

Every project, whatever its size, runs through the same loop:

How a project session goes
  1. Describe

    Say what you want and what "done" means

  2. Plan

    For bigger builds, read the plan before anything is created

  3. Build small

    Get the simplest working version first

  4. Look at it

    Open the result and react like a client would

  5. Improve

    One change per message until it is right

One-hour projects

You get: one web page with your name, a short bio and buttons for your links, ready to publish. Difficulty: easy.

First prompt
Build a personal link page as a single index.html: my name [NAME], a one-line bio [BIO], a round photo from @[PHOTO FILE], and buttons for these links: [LINKS]. Mobile first, large buttons, colors [COLORS]. Done means it opens from the folder and looks right at phone width.

2. A printable guide for your customers

You get: a one-page handout, such as care instructions or a how-to, that prints cleanly and saves as a PDF from your browser. Difficulty: easy.

First prompt
Turn @[NOTES FILE] into a one-page printable guide for my customers about [TOPIC]. Make it an HTML page that fits on one sheet of A4 or US Letter paper, with clear headings and generous spacing. Then tell me how to save it as a PDF from my browser.

3. An email signature for your team

You get: a signature with name, role, phone and logo that you copy from the browser into your email app's settings. Difficulty: easy.

First prompt
Create an email signature as signature.html for [NAMES AND ROLES]: name, role, phone, website and our logo from @[LOGO FILE]. Keep it under 600 pixels wide with standard fonts. Then explain how to copy it into [EMAIL APP].

4. Meeting notes to an action list

You get: decisions and action items, with owners and due dates, pulled out of a messy transcript. Difficulty: easy.

First prompt
Read @[TRANSCRIPT FILE] from today's meeting. Make actions.md with two tables: decisions made, and action items with owner, due date and the sentence each came from. If an owner or date wasn't said, write "not set" instead of guessing.

5. A family recipe page

You get: scattered recipe notes turned into one tidy page with a search box. Difficulty: easy.

First prompt
Turn the recipes in @[RECIPES FILE] into recipes.html: one card per recipe with ingredients and steps, a search box that filters by name or ingredient, and a print button. Keep my wording and only fix obvious typos.

6. A reading digest

You get: one page summarizing articles you meant to read, with the key points and a link to each. Difficulty: easy.

First prompt
Read these articles: [LINKS]. For each, give the main point in one sentence, three key details, and anything I should act on. Save it as digest.md with the link under each summary.

Half-day projects

7. A price calculator for your service

You get: a page where visitors pick options and see an estimate based on your real prices. Difficulty: medium.

First prompt
Build a price calculator as calculator.html for my [SERVICE]. Options and prices: [OPTIONS AND PRICES]. Update the total as options change, and add a line saying it's an estimate. Include three test cases with known totals and show me they pass.

The second message is where it becomes yours. A typical follow-up:

  1. You:

    Round the total up to the nearest 5 and show the price per person below it.

  2. Claude Code:

    Done. The total now rounds up to the nearest 5, a new line shows the price per person, and all three test cases still pass.

8. A quiz that recommends a product

You get: a short quiz that suggests the right product or package from the visitor's answers. Difficulty: medium.

First prompt
Build a five-question quiz as quiz.html that recommends one of these: [PRODUCTS OR PACKAGES]. Who each one suits: [DESCRIPTIONS]. Show the result with a short reason and a link to [PAGE]. Before building, show me the questions and the scoring rules to approve.

9. Flashcards from your study notes

You get: a flashcard app in your browser that remembers which cards you knew. Difficulty: medium.

First prompt
Turn @[NOTES FILE] into flashcards.html: one question per card, flip on click, "knew it" and "didn't know" buttons, and progress saved in the browser so it's still there tomorrow. Show me the first ten cards before you build the app.

10. A habit tracker

You get: a monthly grid for your habits that saves your ticks in the browser. Difficulty: medium.

First prompt
Build habits.html: a monthly grid for [HABITS] with one tick per day, a streak count for each habit, and data saved in the browser. Add a button that downloads my data as a CSV file.

11. An event page with a calendar file

You get: one page with the date, a countdown, the schedule, directions and an add-to-calendar file for guests. Difficulty: medium.

First prompt
Build event.html for [EVENT] on [DATE] at [PLACE]: a countdown, the schedule [SCHEDULE], directions, and a button that downloads an .ics file so guests can add the event to their calendar. Tell me how to test the .ics file.

12. A Chrome extension for one small job

You get: a browser extension that does one thing you repeat, such as counting the words in selected text. Difficulty: medium.

First prompt
Build a Chrome extension in a folder called word-counter: when I select text on any page and click the extension icon, it shows the word and character count. Use Manifest V3, then give me the exact steps to load it.

To try it, Chrome's getting started guide has you open chrome://extensions, turn on Developer mode and click Load unpacked.

13. An application tracker board

You get: a board with columns such as Applied, Interview and Offer, where you drag cards and keep notes. Difficulty: medium.

First prompt
Build tracker.html, a board with the columns [COLUMN NAMES]. Each card has a name, a date, a link and notes. I can drag cards between columns, everything is saved in the browser, and there's an export to CSV.

Weekend projects

14. A four-page business website, live

You get: home, services, about and contact pages, published on the web. Difficulty: harder.

First prompt
Interview me one question at a time about my business, then plan a four-page website: home, services, about and contact. Show me the page outline and wait for my OK before building anything.

For design, building and publishing, follow how to build a website with AI.

15. A morning industry digest that runs itself

You get: a daily file summarizing new posts from sites you follow. Difficulty: medium.

First prompt
Read the RSS feeds listed in @feeds.txt, pick up to ten items published since yesterday, and write digest/[DATE].md with one line and a link per item. Run it once now so I can check the format, then set it up as a scheduled task every morning at [TIME].

Scheduling needs the Claude desktop app; Anthropic's guide to Desktop scheduled tasks explains how runs work.

16. Your own skill pack

You get: three skills for tasks you repeat, each started with a slash command. Difficulty: medium.

First prompt
These are three tasks I repeat every week: [TASKS]. For each, draft a SKILL.md for ~/.claude/skills/ with a description that says when to use it. Show me all three and wait for my OK before saving.

How to create a Claude skill explains what makes a skill trigger reliably, and Anthropic's Skill Creator skill can interview you and write the files. The Claude Skills directory shows more ready-made ones.

17. A Notion weekly review

You get: a review page in Notion each week with what got done, what's open and what's stuck. Difficulty: medium.

First prompt
Using the Notion connector, read the tasks in my [DATABASE NAME] database that were completed or changed this week. Draft a page called "Weekly review [DATE]" with three sections: done, still open, blocked. Show me the draft before you create the page.

Notion runs its own hosted MCP server, listed in our Notion MCP entry; what an MCP server is shows how to connect it safely.

18. A dashboard from a Google Sheet

You get: a page of charts that reads your sheet, so it updates when the sheet does. Difficulty: harder.

First prompt
Build dashboard.html that loads this CSV link from my Google Sheet: [CSV LINK]. Show [THREE METRICS] as big numbers and one line chart of [METRIC] over time. If the link fails to load, show a clear error message instead of an empty page.

19. A browser game or quiz night

You get: a memory game for your kids or a quiz with a scoreboard for a team event. Difficulty: easy.

First prompt
Make a memory match game as game.html with [NUMBER] pairs of cards using these words or emoji: [LIST]. Add a move counter, a timer and a "play again" button, and make it work by touch on a tablet.

20. A team onboarding hub

You get: one page that walks new staff through their first week, built from your existing documents. Difficulty: medium.

First prompt
Read the documents in @[DOCS FOLDER] and build onboarding/index.html for new team members: a first-week checklist, the key policies in plain words, who to ask for what, and links to the full documents. Use only what the documents say, and list anything that looks out of date.

For the follow-up prompts that turn a first draft into a finished project, use the Claude Code prompt templates.

Quick check0 of 2 correct

Which first project gives you the quickest feedback?

What should a first prompt always include?

What to do next

Choose one project from the one-hour list, make an empty folder for it, and send its first prompt today. When the first version works, ask for one improvement at a time until you would happily show it to someone.

Then pick a half-day project that uses what you learned. If you want a guided path that ends with a live landing page, an AI video and a working agent, the Claude Code course builds each of those step by step.

Project planning card

A one-page card that turns any idea into a scoped first session: the outcome, a done-when test, the smallest version, three opening prompts and a stop list.

Enter your email and the full section opens right here. You also get a free lesson from the course.

No spam. One click to unsubscribe. We use your email to send you the course and AI tips.

Frequently asked questions

Can I share what I build with people who don't use Claude Code?

Yes. A single HTML file can be emailed or opened from a shared drive, and a website can go live on a host such as Vercel so anyone can open the link. Scripts are harder to share, because the other person needs the same tools installed.

What if Claude Code breaks a project that was working?

Press Esc twice or run /rewind to restore files from an earlier checkpoint. Rewind covers edits made with Claude's file tools but not changes made by commands it ran, so keep a Git history or a copy of bigger projects.

How much of my plan does a weekend project use?

It depends on the project's size and how long each conversation runs, so there is no fixed number. Run /usage to see where you stand, and start a fresh session with /clear between separate parts of the project.

Which project is best for learning Claude Code?

The personal link page or the price calculator. Both are a single file, you see the result straight away, and each teaches the loop of describing, reviewing and asking for changes.

Do I need to understand the code Claude writes?

No, but you do need to check the result: open the page, try every button and compare any numbers with their source. Asking Claude to explain a file in plain words is a quick way to learn what it built.

Keep reading