Libraries
Libraries group related /instructions and @knowledge so your team can organise context by project, team, or purpose. When you publish a library, every published file inside becomes available to your MCP-compatible tools. Your AI-assistant reads from these libraries when running workflows.
This page explains how to manage and structure libraries so your tools produce higher-quality outputs.
Creating and managing libraries
Section titled “Creating and managing libraries”Editors and owners can manage libraries from the Sokket sidebar.
Create a new library
Section titled “Create a new library”- In the sidebar, select the + button next to the library selector
- Enter a name for your new library
- Press Enter to create the library
Rename or delete a library
Section titled “Rename or delete a library”- Select the library using the main library dropdown
- Select the (…) menu next to its name
- Choose Rename or Delete
Library structure
Section titled “Library structure”A clear library structure improves how your AI-assistant uses context. Well-organised libraries help produce better outputs, reduce token usage, and reduce hallucinations by keeping related /instructions and @knowledge together. As your organisation grows, structure becomes essential for keeping context easy to find and maintain.
When libraries are structured deliberately:
- Tools avoid pulling unrelated files
- Prompts use fewer tokens
- Models draw from specific reference material
- Teams keep context organised as it grows
Ways to structure libraries
Section titled “Ways to structure libraries”By project
Use names like Mobile-App-Refactor or Project-Phoenix-API when context belongs to a specific codebase or feature area.
By team
Use names like Frontend-Team or Platform-SRE for discipline-specific standards, patterns, and workflows.
By purpose
Use names like Code-Generation, Debugging, or Documentation for shared utilities and reference material used across multiple teams.
Choose names that make it easy for anyone on your team to understand what the library contains.
Sample library
Section titled “Sample library”New organisations start with a Sample Library that includes example /instructions and @knowledge. It behaves like any other library: you can edit, publish, or delete it. It gives you a working example of how context fits together and helps you test tool connections immediately.
Related pages
Section titled “Related pages”Learn more about /instructions, @knowledge, or context engineering