What you’ll make
Set up one Claude Project that can turn a new input into a familiar result.
Worked example
Weekly release notes for a planner app
A creator adds an approved release-note sample and a short glossary. The glossary defines 'Duplicate page' as the exact button label and describes which editors show it. The instructions require a heading and two sentences, plus a separate review note when a launch date is missing.
With a completed ticket about duplicate-page export, the new chat names the feature and one visible benefit. In the second chat, a ticket marked 'under review' goes into the review note instead of becoming a published change. The creator saves both test cases beside the glossary.
Before you start
- Pick a job with consistent inputs and an output you can recognize, such as turning a release ticket into customer-facing notes.
- Prepare one approved artifact, a small reference file with product vocabulary, and a complete test request. Choose a second request that deliberately leaves out one required fact.
Pick one job for the Project
Write what comes in and what should come out. Find one finished example you’d use again and a small reference that answers common questions about the work.
I have one reviewed release ticket, an approved note, and a glossary with the exact label “Duplicate page.”
I want one short customer-facing update that names the change and explains what it helps them do.
Draft the Project instructions
Copy the prompt into a Claude chat and attach your approved example and reference. Check the draft, then create a Project in Claude. Paste the reviewed block into its instructions and add the reference files.
I tell Claude to use last month’s note for format and the glossary for button labels.
The instructions might say to write a heading and two sentences, use the approved label, and ask for release status if it’s missing.
Write the instructions for one Claude Project
Draft one set of Claude Project instructions for a repeat job. Use the details I provide in this chat or in my attachments. Return a short Project name and a paste-ready instruction block. State the input I’ll give it, the result and its sections, what each reference is for, and when to ask before drafting. Use examples for shape and wording style. Take current case details from the new request and approved sources. Ask one focused question if the output or required source is unclear. Keep the instructions short enough to review before I save them.
Try it with a real-looking input
Start a new chat inside the Project. Give it one fresh ticket or request with the facts it needs. Check that the draft follows your example’s shape and uses details from the current request.
Save a test you can run again
Save the sample request and the outcome you expect with your Project notes. Run the same test with one required detail removed and see whether the instructions tell Claude how to handle the gap.
- The new chat returns the result you asked for.
- Exact labels match the approved reference.
- A missing required detail gets a focused question.
Optional: Check what happens with missing information
Start another chat in the Project and leave out a fact the result needs. See whether Claude asks for it, then update the instructions if it fills the gap by guessing.
Draft Project instructions from one good example
Give Claude your recurring job, approved example, and sources to get instructions you can paste into the Project.
Help me set up a Claude Project that turns [repeat inputs] into [specific deliverable] for [reader]. Here’s an approved example [file] and the product facts or policies it can draw from [source list with versions]. Use the example to learn the shape and voice. Pull live details from each request and the applicable reference. Here are nearby cases that need a different workflow [out-of-scope cases]. Give me a short title and paste-ready Project instructions. Spell out the required inputs, output sections in order, which source wins for each type of fact, and when to ask a question or leave a review note. Include three checks I can verify in the result. End with a small knowledge-base list showing what to upload once and what to attach only to the current chat. Flag any source precedence I haven’t decided.
Run the complete case, then try one missing input
Paste this into two new chats in the Project, replacing the case each time to see whether the rules hold.
Use the Project instructions and its references to produce [deliverable] for this case [complete or incomplete case]. Start by checking whether you have the required inputs. If a missing fact blocks the draft, ask the specific question the instructions call for. If the instructions allow a partial result, mark what needs review. Use the sample for structure and keep its case details out of this draft. After the result or question, list the reference files you used, the support for each customer-facing claim, and which checks passed or still need my review.
Troubleshooting
Why does an old feature label keep showing up?
Search the project files for the old label. Retire outdated copies and mark the current glossary with a date and precedence rule.
Why did a new chat miss something discussed last time?
Add any stable rule or reference you want every chat to use to the project itself. Reattach one-off context with the request that depends on it.