# Quick Start
This walkthrough turns one code module and one local documentation folder into a reviewed knowledge package with a browsable site. You give instructions in plain language; the Agent runs the commands the workflow returns. The commands shown below are what the Agent runs on your behalf, so you can recognize them in its progress messages.
Make sure [Installation]() is done and you have restarted the Agent session so the plugin is loaded.
## 1. Create the knowledge workspace
Tell the Agent where the Context knowledge workspace should live and what it is for:
```text
/c4a:context Create a Context knowledge workspace in ./context for our component library
and its product docs. Readers are frontend developers new to the library.
```
The Agent initializes the directory and installs its dependencies:
```bash
context init ./context
cd ./context
bun install
context status --format json
```
You get this layout:
```text
context/
├── AGENTS.md # guidance for the Agent
├── src/ # source, phase and package declarations
├── sources/ # registered sources and captured evidence
├── knowledge/ # approved knowledge (empty for now)
├── dist/ # built packages (ignored by Git)
└── .tmp/ # runtime state and reports (ignored by Git)
```
## 2. Point it at your sources
Name the material and anything the Agent should skip:
```text
Use ../component-lib for code and ../docs for product documents.
Skip the deprecated v1 folder.
```
The Agent registers each boundary. Registration records what is in scope; it does not decide what to write.
```bash
context source add repo 20260901 --module component-lib --local ../component-lib --configure
context source add file 20260901 --module product-docs --local ../docs --configure
```
For a monorepo, pick the package or service your readers need. Unneeded material costs reading time and tokens, but do not exclude something just because its filename looks old.
## 3. Confirm the work-start report
The Agent reads representative material, asks about anything that would change the scope, records the reader purpose in `src/indexers.yaml`, and presents a **work-start report** with:
- the confirmed sources and scope;
- the Indexer skills it will use;
- the first pages you should expect and where they will sit in the site.
Nothing is written until you approve the report. If the plan is off, say what to change — for example "merge the two API pages" or "add a troubleshooting page" — and the Agent revises it.
## 4. Let it write, then review
After approval, the Agent writes each page with references to exact source lines and submits them for checks on coverage and stale inputs.
When writing finishes, you receive a review report showing each page's title, path, summary and content. Approve it, reject pages, or ask for revisions. Approved pages land in `knowledge/` as Markdown; rejected or revised pages go back to writing.
```mermaid
flowchart LR
write["Agent writes pages"] --> review["You review"]
review -->|revise| write
review -->|approve| kn["knowledge/"]
kn --> build["context build"]
build --> kb["dist/component-kb/"]
build --> site["dist/component-site/"]
```
## 5. Build the package and site
For a new knowledge workspace, the Agent proposes a knowledge package plus a website by default. The package declaration in `src/index.ts` looks like this:
```ts
kbPackage({
name: "component-kb",
template: "src/package-templates/kb",
site: { title: "Component knowledge", lang: "en-US", base: "/" },
});
```
`context build` then produces `dist/component-kb/` for Agents and `dist/component-site/` — a static site with article pages and local search — for people. Commit the knowledge workspace to Git so the result can be inspected, versioned and refreshed later.
## Next steps
- Ask a question against the new package with `/c4a:context-inspect-search`.
- When the code or docs change, tell `/c4a:context` what changed; it reopens only the affected pages.
- For larger scopes, read [Large Projects]().
- See every entry you can invoke, and the Skills that run on their own, in [Commands and Skills]().
---
## Sources
- [context/packages/context/docs/getting-started.md L47–L50 · 3b0ce0a]()
- [context/README.md L45–L53 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L29–L45 · 3b0ce0a]()
- [context/packages/context-cli/docs/quickstart.md L67–L72 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L47–L60 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L105–L118 · 3b0ce0a]()
- [context/README.md L87–L88 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L120–L136 · 3b0ce0a]()
- [context/README.md L29–L31 · 3b0ce0a]()
- [context/packages/context/docs/guides/package-outputs.md L33–L54 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L76–L98 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L155–L157 · 3b0ce0a]()
- [context/plugins/context/skills/context-inspect-search/SKILL.md L1–L3 · 3b0ce0a]()