Hands-on: a Project and an Artifact, end to end

The workflow you're about to run

Here's the shape of it, so you can see where you're going before you start. You'll build a project that holds Fernway's onboarding material, give it standing instructions, then use it to produce a real deliverable (a new-starter welcome pack) as an artifact you can edit, verify and reuse. It's the same chain you'd use for any recurring piece of work: gather → set up → produce → check → reuse.

Everything below uses the Fernway sample files so you can do it safely, start to finish. Keep to the Phase 0 privacy rules throughout. If you swap in your own material later, nothing confidential goes on a tool your employer hasn't approved.

You'll need three sample files to hand: the project brief, the remote-working policy and the org chart.

Step 1: Create the Project and add knowledge

In the sidebar, create a new Project. Name it "Fernway onboarding, practitioner run" and give it a one-line description. Then open its knowledge area and add all three sample files. That's your shared context set. You won't paste these again.

Quick check before you move on: the three files should be listed in the Project's knowledge, and you should be inside the Project (its name showing), not in a general chat.

Step 2: Write the project instructions

Standing instructions shape every chat in the Project. Set them once, deliberately.

You're helping run new-starter onboarding at Fernway, a mid-size UK company. Audience: new joiners and their managers, non-technical. Always write in plain UK English: warm, clear, scannable, no corporate filler. When a fact comes from a file, name the file. If the files don't cover something, say so rather than inventing a Fernway detail. Prefer short sections with headings.

Step 3: Produce the deliverable as an artifact

Now the real work. Ask, inside the Project, for the welcome pack, and ask for it as a document you can keep.

Using the project files, build a new-starter welcome pack as a single formatted document: (1) a warm one-paragraph welcome, (2) what to expect in week one, (3) the remote-working essentials (office days and core hours) quoting the policy, (4) a 'who's who' of the people they'll deal with, from the org chart, and (5) who to contact for IT setup. Flag anything the pack should include that the files don't actually cover.

Claude opens an artifact with the pack. Notice it drew on all three files at once: the welcome from the brief, the office-days and core-hours from the policy (quoted), and the who's-who from the org chart. It flagged a gap too, such as no named IT-setup contact if the org chart doesn't list one.

Step 4: Iterate in the panel

Refine it without leaving the artifact. Two follow-ups:

Two changes: shorten the week-one section to five bullet points, and turn the 'who's who' into a small table with Name, Role and What they help with. Keep everything else.

Then make one edit by hand (click into the artifact and fix a name or a date yourself) so you've used both routes. If an edit overreaches, step back a version using the control at the edge of the panel.

Step 5: Verify before it's real

This is the step people skip and shouldn't. The pack looks finished; now check it. The instruction to quote the policy exists so you can confirm the office-days and core-hours against the source file in seconds. Do that. Confirm the names and roles match the org chart. Ask Claude to help you check its own work:

Before I use this, list every factual claim in the pack (office days, core hours, names, roles, contacts) as a table with the exact file and line each one came from. Flag anything you inferred or couldn't source directly.

Any claim without a clean source is one to check by hand or cut. A welcome pack that misstates the core hours is worse than no pack, so this step is not optional.

Step 6: Get it out and reuse

When it's right, copy or download the artifact for real use. Then prove the Project's value by spinning a second deliverable from the same knowledge, no re-pasting:

Now, from the same project files, produce a short manager's checklist artifact: what a line manager must do before, on, and in the first week of a new starter joining. Keep it to the house style and name your sources.

Your workflow checklist

Run down this before you call it done:

• The Project exists, with the three files in its knowledge and clear instructions set.
• The welcome pack was produced as an artifact, drawing on all three files.
• You iterated on it both by asking Claude and by editing the panel directly, and stepped back a version at least once.
• You verified the load-bearing facts (office days, core hours, names) against the source files.
• You produced a second deliverable from the same Project without re-pasting anything.
• You've copied or downloaded a finished output.

Try it now

Common mistakes

• Producing without verifying. The workflow isn't finished at the artifact. It's finished after the cross-check. A polished pack with a wrong core-hours line is a liability, not a deliverable.
• Treating it as one giant chat instead of a Project. If you find yourself re-pasting the files, you've skipped the setup that makes the rest easy. Put shared material in the Project once.
• Editing by copy-paste instead of in the panel. Change the artifact in place, by asking or by direct edit, so you keep one clean, versioned copy rather than three diverging pastes.
• Over-trusting the finished pack because it's polished and 'from the files'. Drawing on real project knowledge makes an answer feel authoritative, which is exactly when checking slips. Claude can still misquote a policy or blur two roles from the org chart. The verify step, every claim traced to a source, is what separates a practitioner from someone who just generated something that looked right.

Keeping current

The individual features in this workflow will keep changing; the workflow itself (gather, set up, produce, check, reuse) is durable, and it's the thing worth carrying into any future version of the tool. When the details shift, check the Projects and artifacts help articles and the Claude release notes. Accurate as of 13 July 2026.