Goal. The landing page I designed becomes a real website I can put online.
Open. Claude Design (for the handoff) then Claude Code (Part 6), paid plan; an empty folder.
Build this design as a simple static website: one page, HTML and CSS, no frameworks, loads fast on phones. Keep the layout, colors and text exactly as designed. Replace placeholders: hours [hours], address [address], phone [phone], email [email]. Make the buttons work: Order opens [link], Menu scrolls to the menu section, Visit us opens a map link. Run it locally and give me the address to open. Then tell me, in plain words, three ways I could put it online and what each costs.
What you get · Watch out
What you get. A folder with the site, a local preview address, and hosting options explained.
Watch out. Hosting is a separate step with a small cost; decide that before building. Change the design and hand off again rather than editing the site by hand. If stuck: Chapters 3.5, 6.1.
More prompts like this
See all →Set up an online shop with products
Goal. My products listed in an online store, with descriptions, in an afternoon.
Open. Cowork with the Shopify connector (paid plan); a store account; product photos in a folder or attached. *Needs a tool outside Claude.*
I sell [what] to [who]. Brand voice: [3 words]. Here are my products: [name, price, sizes/variants, 2 facts each] and photos. 1. Write a product title, a 60-word description, and 3 bullet facts for each, in my voice. 2. Show me all of them in a table for approval. 3. After I approve, create the products in the store with the connector, in a collection called [name], as drafts (not published). 4. Tell me what is missing before I can publish (shipping, taxes, policies).
What you get · Watch out
What you get. A table to approve, then draft products in the store and a launch checklist.
Watch out. Create as drafts; publish yourself after checking prices. Facts about materials and sizes must come from you, not be invented. If stuck: Chapters 1.9, 2.10.
Build my first custom skill
Goal. Teach Claude one job I do the same way every time, so I never explain it again.
Open. Chat with /skill-creator (any plan that shows it), or Claude Code (Part 6).
/skill-creator I want a skill called [name] for [the job, e.g. writing my weekly client update]. Every time, it should: [the steps in order]. It must always: [rules, e.g. use this structure, this tone, these headings]. It must never: [list]. Here is a perfect example of the output: [paste]. Ask me anything unclear, then create the skill and show me how to call it.
What you get · Watch out
What you get. A skill you can call by name (/[name]) that produces the job in your format.
Watch out. One job per skill. Include a real example of the output; the skill copies it. If stuck: Chapters 1.11, 6.3.
