Claude Project: Build a Personal Reference Library for Your Machines and Yarn Specs

What This Builds

A Claude Project is a persistent workspace where you upload your machine notes, yarn specification sheets, and troubleshooting logs — and Claude can reference all of it every time you chat. Instead of typing context every conversation, you build a personal knowledge base once. Every conversation in the Project automatically has access to everything you've put there.

Prerequisites

• Comfortable using Claude for shift notes and documentation (Level 3)
• Claude {{tool:Claude.plan}} subscription ({{tool:Claude.price}}) — required for Projects
• 1-2 hours to set up and upload your reference materials
• Any documents you want to include: yarn specs, machine notes, troubleshooting logs, shift report templates

The Concept

A Claude Project is like a filing cabinet that Claude has already read. Normally, when you start a new Claude conversation, Claude has no memory of your last conversation or any of your documents — you start fresh every time. With a Project, Claude always has access to everything you've put in the Project's files. It's like having a coworker who has actually read and remembered your machine manuals, rather than you having to re-explain everything every time.

Build It Step by Step

Part 1: Plan your knowledge base

Decide what to include in your Project. Good candidates:

High value (definitely include):

• Your personal notes on each machine type you operate
• Yarn specification sheets for products you run (even typed from memory)
• Common fault codes and what they mean (from the manual or your experience)
• Your mill's threading sequences for each machine
• Standard shift handoff report template
• Standard maintenance request template

Optional (include if you have them):

• Pages from machine manuals (scan or photograph, then convert to text)
• Quality spec sheets for products you run
• Your personal troubleshooting log from the past 6 months

Don't include:

• Personal information, names, or anything your mill treats as confidential
• Large files that would take a long time to upload (Claude handles text best)

Part 2: Create the Project

1. Log into Claude at {{tool:Claude.url}} with your {{tool:Claude.plan}} account
2. Find Projects in the left sidebar — look for a folder icon or "Projects" label
3. Click "New Project" or the + button next to Projects
4. Give it a name: "Winding Dept Reference Library" (or your mill name + role)
5. Add a Project description (optional): "Machine specs, yarn settings, and document templates for textile machine operators at [mill name]"

Part 3: Upload your reference materials

1. Inside your new Project, look for "Project Knowledge" or "Add to project" — click it
2. Upload or paste your documents:

   • You can drag and drop text files (.txt, .md, .pdf)
   • Or click "Add content" and paste text directly
3. Start with your most important document: a text file with your machine specs and yarn settings

Here's a template to copy, fill in, and upload as your first document:

WINDING DEPARTMENT MACHINE REFERENCE
Updated: [date]

MACHINES IN MY DEPARTMENT:
- Machine 1: [Machine brand/model] — [notes]
- Machine 2: [Machine brand/model] — [notes]
[continue for all machines]

YARN SPECIFICATIONS:
Product: [Yarn name/count]
- Speed: [X] m/min
- Tension: [X-X] cN
- Known issues: [describe]
- Tips: [anything that helps]

[repeat for each yarn type]

COMMON PROBLEMS AND FIXES:
1. [Problem description]
   First check: [what to do]
   If that doesn't work: [next step]
[repeat for each common problem]

SHIFT REPORT TEMPLATE:
[paste your standard shift handoff format]

MAINTENANCE REQUEST TEMPLATE:
[paste your standard maintenance request format]

1. Upload additional documents as separate files — Claude handles multiple files in a Project

Part 4: Configure the Project Instructions

1. In the Project settings, find "Custom Instructions" or "Instructions for Claude"
2. Add instructions that tell Claude how to behave in this Project:

This is a reference library for textile machine operators. When answering questions:
- Reference the machine specs and yarn settings I've provided before giving general answers
- If the answer is in my documents, cite it specifically (e.g., "per your Machine 1 notes...")
- Give numbered checklists for troubleshooting questions
- Use simple language — I may be reading this on my phone mid-shift
- If you don't find the answer in my documents, say so and give general guidance
- Help me write shift documentation using the templates in my documents

Part 5: Test your Project

Start a conversation inside the Project (not in regular Claude) and test:

1. Spec lookup test: "What tension range do I use for [yarn type you uploaded]?"

   • Claude should reference your specific document, not give generic numbers

2. Troubleshooting test: "My yarn is breaking near the package — what should I check first?"

   • Claude should reference your troubleshooting notes if you included them

3. Document writing test: "Write a shift handoff note using the template in my reference library. Here's what happened today: [describe your shift]"

   • Claude should use your actual template

What you should see: Claude saying things like "Per your Machine Reference document, Machine 3 runs best at 850-900 m/min for this yarn type..." — referencing your specific content.

Real Example: Personal Reference Library in Action

Setup: An operator uploads: machine specs for 4 winding machines, yarn settings for 6 products, a personal troubleshooting log with 12 common problems, and shift/maintenance report templates.

Input: Types into the Project: "I'm switching from 2/30 combed cotton to 2/40 ring-spun cotton on Machine 2 today. What settings should I adjust?"

Output: "Per your yarn specification document, 2/40 ring-spun cotton should run at 820-870 m/min (slower than the 2/30 you just ran at 900 m/min) and tension should be set to 14-17 cN (lower than 2/30's 16-20 range). Your Machine 2 notes mention its tension spring tends to read 1-2 cN higher than the display shows — account for that when setting. Start at the lower end of the range and verify bobbin shape in the first 5 minutes."

Time saved: Operator gets specific, accurate guidance in 15 seconds instead of looking up specs, checking machine notes, and remembering Machine 2's quirk.

What to Do When It Breaks

• Claude doesn't reference my documents → Make sure you're chatting inside the Project (look for the Project name at the top), not in regular Claude
• Claude gives generic answers instead of using my specs → Update the Project Instructions to explicitly say "always check the uploaded documents first"
• I can't find old conversations → Claude Projects keep conversation history — scroll up in the Project or search by keyword
• My documents are too long to upload → Break them into smaller files by machine type or topic; Claude handles multiple smaller files better than one huge file

Variations

• Simpler version: Copy your machine notes into the Project Instructions text box instead of uploading files — less organized but faster to set up
• Extended version: Add a "personal log" document and update it with new problems and solutions each week — your troubleshooting knowledge compounds over time

What to Do Next

• This week: Upload your machine specs and yarn settings, then test the spec lookup
• This month: Add your troubleshooting log and all your document templates; refine based on what you actually ask it
• Advanced: Create a second Project for career development — upload your resume, performance reviews, and career goals; use it to prep for every review conversation

Advanced guide for textile machine operator professionals. Claude Projects require a {{tool:Claude.plan}} subscription ({{tool:Claude.price}}). These techniques use more sophisticated AI features that may require paid subscriptions.