Add context
Knowledge is the curated material your agents should follow, such as your team's standards or a product spec. Save this as CLAUDE.md on your machine:
# Project Guidelines: Triage agent for customer issues
## Core Coding Standards
- **Strict Typing**: Never use `any`. Define interfaces for all API responses.
- **Functional Style**: Prefer pure functions and immutable data over classes.
## Critical Commands
- **Build**: `npm run build`
- **Lint**: `npm run lint`
- **Test**: `npm test`
- **Format**: `npm run format`
## Quality Check Workflow
After every significant code change, run `npm run format`, then `npm run lint`,
then `npm test`, and fix any regressions before reporting completion.
Now we'll upload the document to Meko:
Cloud
In the portal:
- Open Datapacks, select your datapack, and click + Add Knowledge.
- Upload the file.
Meko parses, chunks, and indexes it, which can take a few minutes. Free accounts can store up to 100 MB across knowledge files and artifacts, at 5 MB per file.
Local
Run the following command:
meko-cli upload CLAUDE.md
Meko uploads the file to your default datapack.
The command waits until the file is indexed (check Knowledge files status). It accepts PDF, text, Markdown, JSON, CSV, XML, or HTML, up to 50 MiB.
When the file is indexed, ask your agent:
What are the critical commands for the project?
The critical commands defined in your project guidelines are:
- Build: npm run build
- Lint: npm run lint
- Test: npm test
- Format: npm run format
After every significant code change, run them in this order: format, lint, test.
Meko read, chunked, and indexed the document, and your agent searched it using the MCP server.
Your agent can also upload files. See Upload from your agent.
Because you only have one datapack, Meko uses it automatically. When you have multiple datapacks, you switch between them by designating one as your active pin: the datapack where Meko saves conversations and memories. See How to change your pin.