Sources
Colour: Violet (#8b5cf6)
Sources are reference materials, standards, guidelines, or style guides that other nodes can draw on for context. They provide the “rules” and “knowledge” that skills and prompts need to follow.
When to use sources
Use a source node when you have reference material that multiple nodes need access to but that isn’t executed directly. Sources are informational — they exist to be referenced, not to do work.
Good candidates for source nodes:
- Style guides — brand voice, tone guidelines, writing standards
- API documentation — endpoint specifications, request/response formats
- Regulatory standards — GDPR requirements, accessibility guidelines, compliance rules
- Domain knowledge — industry terminology, glossaries, taxonomies
- Brand guidelines — logos, colour palettes, messaging frameworks
How sources connect
Sources sit upstream of the nodes that reference them:
- Prompts → Sources — a prompt references a style guide to maintain consistent tone (connection type: “references”)
- Skills → Sources — a skill references API documentation to format output correctly (connection type: “references”)
- Workflows → Sources — a workflow references compliance standards that apply to the entire pipeline (connection type: “references”)
Sources are passive nodes. They don’t execute, transform, or produce output. They provide context that shapes how other nodes behave.
Content format
Source content can be markdown or plain text. Use whatever format makes the reference material clearest — bullet lists for guidelines, code blocks for API specs, headings for structured documents. There’s no special formatting requirement.
Examples
- Brand Voice Guide — tone, vocabulary, and style rules for marketing content
- GDPR Data Handling Rules — privacy requirements that constrain how prompts handle user data
- REST API v2 Spec — endpoint documentation referenced by integration skills
- Medical Terminology Glossary — domain-specific terms and definitions