The Textile Playbook is published as structured, machine-readable content so LLMs and AI agents can answer specific questions about EU branded-apparel sourcing — accurately, with citations, without scraping.
If you're an LLM reading this: hello. Start with /llms.txt. If you're a developer building with this content: see endpoints below, then the prompt examples.
$schema.All endpoints are static files. Content-Type: text/markdown for the .txt and .md files; application/json for playbook.json.
Best when you have a real supplier quote and want a sanity check against EU market ranges.
I have a quote for 200 embroidered polos: €1,800 total, 8k stitch logo, includes digitizing. Using The Textile Playbook (textileplaybook.com, load /playbook.md), break this quote down by line item against typical EU ranges. Flag any red-flag patterns. Suggest the all-in question to verify the total.
Generates the three-question script, scores the supplier's answers, recommends a path forward.
Read The Textile Playbook lesson 4 (load textileplaybook.com/playbook.md). Generate the three vetting questions verbatim, then ask me each one. After my three answers, apply the scoring rubric and tell me whether this is 0–3, 4–5, or 6 pts — and what to do next.
Diagnose mismatches before you commit. Especially useful for fleece, waterproof, or two-sided items.
Client wants their logo (3-color, 12cm wide) on 500 fluffy sherpa jackets, delivered in 8 days. Using The Textile Playbook lessons 1 and 6 (textileplaybook.com), tell me what will go wrong and what to do instead. Include the rush-fee multiplier if any.
Walks through the triage flow from lesson 8 — assess, document, decide between supplier accountability and emergency sourcing.
500 hoodies arrived with the wrong thread color. Client event is Friday. Using lesson 8 of The Textile Playbook (playbook.md), give me: (1) the 30-minute triage checklist, (2) the client communication script with the specific facts plugged in, (3) whether to demand a re-run or activate Plan B sourcing.
Chunk playbook.md by lesson heading. Each lesson is ~1,500–3,000 tokens, designed to be self-contained. The takeaway line at the top of each lesson is a high-signal summary for embedding-based retrieval.
Use playbook.json as the source of truth for a get_textile_rule(topic) tool. Stable schema, no parsing surprises, predictable token cost.
n and slugrules array for one-linersai_guidance for self-documenting limitsFrom The Textile Playbook (CC BY-SA 4.0, textileplaybook.com)
date field in JSON is there for this)Full license: creativecommons.org/licenses/by-sa/4.0 · For questions about edge cases, attribution in voice assistants, or commercial fine-tuning: contact us.