@neuledge/context 0.2.2 → 0.3.0

package/README.md

@@ -1,8 +1,7 @@
 <p align="center">
   <h1 align="center">Context</h1>
   <p align="center">
-    <strong>Local-first documentation for AI agents</strong><br/>
-    Give your AI assistant expert knowledge of any library—offline, instant, private.
+    <strong>Up-to-date docs for AI agents — local, instant, plug and play.</strong>
   </p>
 </p>
 
@@ -14,27 +13,23 @@
 
 ---
 
-## The Problem
+AI agents are trained on outdated docs. When libraries release new versions, your AI doesn't know — and confidently gives you wrong answers.
 
-You're building with Next.js 16, and your AI assistant confidently suggests code using the old Pages Router because that's what it learned from training data. You paste the docs. It hallucinates anyway. You paste more docs. The context window fills up. Repeat.
+```js
+// Your AI, mass-trained on AI SDK v5 docs, will suggest:
+import { Experimental_Agent as Agent, stepCountIs } from 'ai';
 
-**AI assistants are powerful, but they're stuck in the past.** Their training data is months or years old, and they don't know the specifics of the libraries you're using today.
+// But v6 changed the API entirely:
+import { ToolLoopAgent } from 'ai';
+```
 
----
+The fix isn't better prompting. It's giving your AI the right docs.
 
-## The Solution
+## How It Works
 
-Context connects your AI assistant directly to up-to-date documentation—locally, instantly, and privately.
+Context is an MCP server backed by a [community-driven package registry](registry/) with **100+ popular libraries** already built and ready to use. When your AI agent needs documentation, it searches the registry, downloads the right package, and queries it locally — all automatically.
 
-```
-You: "How do I create middleware in Next.js 16?"
-
-AI:  [automatically queries local docs]
-     "In Next.js 16, create a middleware.ts file in your project root..."
-     [accurate, version-specific answer]
-```
-
-No copy-pasting. No hallucinations about deprecated APIs. No waiting for cloud lookups.
+**Install once. Configure once. Then just ask your AI.**
 
 <p align="center">
   <img src="https://media.githubusercontent.com/media/neuledge/context/main/packages/context/assets/ai-sdk-demo.gif" alt="Context demo" width="800">
@@ -42,72 +37,6 @@ No copy-pasting. No hallucinations about deprecated APIs. No waiting for cloud l
 
 ---
 
-## Real-World Use Cases
-
-### :muscle: "Make my AI actually useful for the stack I use"
-
-Add docs for your entire tech stack. Your AI assistant becomes an expert in the exact versions you're using:
-
-```bash
-context add https://github.com/vercel/next.js
-context add https://github.com/prisma/prisma
-context add https://github.com/tailwindlabs/tailwindcss
-```
-
-Now ask things like:
-- *"How do I set up Prisma with Next.js App Router?"*
-- *"What's the Tailwind config for dark mode?"*
-- *"Show me the new Server Actions syntax"*
-
-### :building_construction: "Stop answering the same questions for my team"
-
-Building an internal library? Package your documentation once, share it with your team:
-
-```bash
-# Build docs from your repo
-context add https://github.com/your-company/design-system
-
-# Your whole team can now ask:
-# "How do I use the DataTable component?"
-# "What props does Button accept?"
-```
-
-### :airplane: "Code on flights and in coffee shops"
-
-Context works 100% offline. Download docs once, query forever—no internet required.
-
-### :lock: "Keep proprietary code discussions private"
-
-Cloud documentation services see your queries. Context runs entirely on your machine. Your questions about internal APIs stay internal.
-
----
-
-## Why Context Over Cloud Alternatives?
-
-| | Context7 | Deepcon | **Context** |
-|---|:---:|:---:|:---:|
-| **Price** | $10/month | $8/month | **Free forever** |
-| **Free tier** | 1,000 req/month ¹ | 100 req/month | **Unlimited** |
-| **Rate limits** | 60 req/hour | Throttled | **None** |
-| **Latency** | 100-500ms | 100-300ms | **<10ms** |
-| **Works offline** | :x: | :x: | :white_check_mark: |
-| **Privacy** | Queries sent to cloud | Queries sent to cloud | **100% local** |
-| **Private repos** | $15/1M tokens | :x: | **Free** |
-
-<sub>¹ Context7 reduced free tier from ~6,000 to 1,000 requests/month in January 2026</sub>
-
----
-
-## :zap: Key Features
-
-- **Single tool** - One MCP tool does everything, no multi-step lookups
-- **Token-aware** - Smart relevance filtering, never overwhelms the context window
-- **Dynamic schema** - Available libraries shown in tool definition
-- **Offline-first** - Zero network calls during operation
-- **SQLite + FTS5** - Fast full-text search with stemming
-
----
-
 ## :rocket: Quick Start
 
 ### 1. Install
@@ -116,28 +45,9 @@ Cloud documentation services see your queries. Context runs entirely on your mac
 npm install -g @neuledge/context
 ```
 
-### 2. Add documentation
+### 2. Connect to your AI agent
 
-```bash
-# From any git repository (GitHub, GitLab, Bitbucket, etc.)
-context add https://github.com/vercel/next.js
-context add https://gitlab.com/org/repo
-context add git@github.com:user/repo.git
-
-# From a local directory
-context add ./my-project
-context add /path/to/docs
-
-# From URL (pre-built package)
-context add https://example.com/react@18.db
-
-# From local file
-context add ./my-package.db
-```
-
-### 3. Configure your AI agent
-
-Context works with any MCP-compatible agent. Choose your setup below:
+Context works with any MCP-compatible agent. Pick yours:
 
 <details>
 <summary><strong>Claude Code</strong></summary>
@@ -274,21 +184,116 @@ extensions:
 
 </details>
 
-### 4. Start using it
+### 3. Ask your AI anything
 
-That's it! Now just ask your AI agent:
+That's it. Just ask:
 
 > "How do I create middleware in Next.js?"
 
-The agent automatically uses the `get_docs` tool when relevant.
+Your agent searches the [community registry](registry/), downloads the docs, and answers with accurate, version-specific information. Everything happens automatically — no manual `context install` needed for registry packages.
+
+---
+
+## The Community Registry
+
+The registry is what makes Context plug and play. It's a growing collection of **100+ pre-built documentation packages** maintained by the community. Think of it like a package manager, but for AI-ready docs.
+
+**Popular packages available today:**
+
+| Category | Libraries |
+|----------|-----------|
+| **Frameworks** | Next.js, Nuxt, Astro, SvelteKit, Remix, Hono |
+| **React ecosystem** | React, React Router, TanStack Query, Zustand, Redux Toolkit |
+| **Databases & ORMs** | Prisma, Drizzle, Mongoose, TypeORM |
+| **Styling** | Tailwind CSS, shadcn/ui, Styled Components |
+| **Testing** | Vitest, Playwright, Jest, Testing Library |
+| **APIs & Auth** | tRPC, GraphQL, NextAuth.js, Passport |
+| **AI & LLMs** | LangChain, AI SDK, OpenAI, Anthropic SDK |
+
+[Browse the full registry →](registry/)
+
+**Anyone can contribute.** If a library you use isn't listed, [submit a PR](registry/) to add it — your contribution helps every Context user.
+
+---
+
+## Why Local?
+
+Context runs entirely on your machine. Docs are downloaded once and stored as compact SQLite databases in `~/.context/packages/`. After that, everything is local.
+
+- **Fast** — Local SQLite queries return in under 10ms
+- **Offline** — Works on flights, in coffee shops, anywhere
+- **Private** — Your queries never leave your machine
+- **Free** — No subscriptions, no rate limits, no usage caps
+- **Reliable** — No outages, no API changes, no service shutdowns
+
+---
+
+## Beyond the Registry
+
+The registry covers popular open-source libraries, but Context also works with any documentation source. Use `context add` to build packages from private repos, internal libraries, or anything not yet in the registry.
+
+```bash
+# Build from a git repository
+context add https://github.com/your-company/design-system
+
+# Build from a local directory
+context add ./my-project
+
+# Specific version tag
+context add https://github.com/vercel/next.js/tree/v16.0.0
+```
+
+Once built, share packages with your team — they're portable `.db` files that install instantly:
+
+```bash
+# Export a package
+context add ./my-project --name my-lib --pkg-version 2.0 --save ./packages/
+
+# Teammate installs it (no build step needed)
+context add ./packages/my-lib@2.0.db
+```
 
 ---
 
 ## :books: CLI Reference
 
+### `context browse <package>`
+
+Search for packages available on the registry server.
+
+```bash
+# Browse by registry/name
+context browse npm/next
+
+# Output:
+#   npm/next@15.1.3           3.4 MB  The React Framework for the Web
+#   npm/next@15.0.4           3.2 MB  The React Framework for the Web
+#   ...
+#
+#   Found 12 versions. Install with: context install npm/next
+
+# Browse with just a name (defaults to npm)
+context browse react
+```
+
+### `context install <registry/name> [version]`
+
+Download and install a pre-built package from the registry server.
+
+```bash
+# Install latest version
+context install npm/next
+
+# Install a specific version
+context install npm/next 15.0.4
+
+# Install from other registries
+context install pip/django
+```
+
 ### `context add <source>`
 
-Install a documentation package. The source type is auto-detected.
+Build and install a documentation package from source. Use this for libraries not in the registry, or for private/internal docs. The source type is auto-detected.
 
 **From git repository:**
 
@@ -401,7 +406,7 @@ context remove nextjs
 
 ### `context serve`
 
-Start the MCP server (used by Claude Desktop).
+Start the MCP server (used by AI agents).
 
 ```bash
 context serve
@@ -420,57 +425,90 @@ context query 'nextjs@16.0' 'middleware authentication'
 
 ---
 
-## :gear: How It Works
+## :gear: Architecture
 
 ```
-┌─────────────────────────────────────────────────────┐
-│                   Your Machine                      │
-│                                                     │
-│  ┌──────────┐     ┌────────────┐     ┌───────────┐ │
-│  │  Claude  │────▶│ MCP Server │────▶│ ~/.context│ │
-│  │          │     │ (get_docs) │     │  /packages│ │
-│  └──────────┘     └────────────┘     └───────────┘ │
-│                          │                         │
-│                          ▼                         │
-│                   ┌────────────┐                   │
-│                   │   SQLite   │                   │
-│                   │   FTS5     │                   │
-│                   └────────────┘                   │
-└─────────────────────────────────────────────────────┘
+┌─────────────────────────────────────────────────────────┐
+│                     Your Machine                        │
+│                                                         │
+│  ┌──────────┐    ┌──────────────────┐    ┌────────────┐ │
+│  │    AI    │    │   Context MCP    │    │ ~/.context │ │
+│  │  Agent   │───▶│     Server       │───▶│  /packages │ │
+│  │          │    │                  │    └────────────┘ │
+│  └──────────┘    └────────┬─────────┘         │         │
+│                           │            ┌──────────┐     │
+│                           │            │  SQLite  │     │
+│                           │            │   FTS5   │     │
+│                           │            └──────────┘     │
+└───────────────────────────┼─────────────────────────────┘
+                            │ (first use only)
+                            ▼
+                   ┌────────────────┐
+                   │   Community    │
+                   │   Registry     │
+                   └────────────────┘
 ```
 
-**When you add a package:**
+**First time you ask about a library:**
+1. The MCP server searches the community registry
+2. Downloads the pre-built documentation package (a SQLite `.db` file)
+3. Stores it locally in `~/.context/packages/`
 
-1. Repository is cloned (for git URLs) or read (for local directories)
-2. Documentation is parsed and split into sections
-3. Sections are indexed with FTS5 full-text search
-4. The package is stored in `~/.context/packages/`
+**Every time after:**
+1. FTS5 full-text search finds relevant sections locally
+2. Smart filtering keeps results within token budget
+3. Your AI gets focused, accurate documentation in under 10ms
 
-**When Claude queries:**
+---
 
-1. FTS5 finds relevant sections by keyword matching
-2. Results are filtered by relevance score
-3. Token budget ensures responses stay concise
-4. Claude receives focused, relevant documentation
+## :question: FAQ
 
----
+### Can I use Context with non-JavaScript frameworks like Spring Boot, Django, or Rails?
+
+**Yes!** Context is language-agnostic. It natively supports Markdown (`.md`, `.mdx`), AsciiDoc (`.adoc`), and reStructuredText (`.rst`) — no conversion needed.
 
-## :package: Package Format
+```bash
+# Python - FastAPI (Markdown)
+context add https://github.com/fastapi/fastapi --path docs/en/docs
+
+# Python - Django (reStructuredText)
+context add https://github.com/django/django --path docs
 
-Packages are SQLite databases (`.db` files) containing pre-indexed documentation.
+# Java - Spring Boot (AsciiDoc)
+context add https://github.com/spring-projects/spring-boot --path spring-boot-project/spring-boot-docs/src/docs
 
+# Rust - The Rust Book
+context add https://github.com/rust-lang/book --path src
 ```
-~/.context/packages/
-├── nextjs@16.0.db
-├── react@18.db
-└── typescript@5.5.db
+
+Point Context at the docs folder with `--path` and it handles the rest.
+
+### Can I contribute package definitions for new ecosystems?
+
+Yes! The `registry/` directory has YAML definitions organized by package manager:
+
+- **`registry/npm/`** — JavaScript/TypeScript (Next.js, React, Tailwind, etc.)
+- **`registry/pip/`** — Python (FastAPI, Flask, Django, Pydantic)
+- **`registry/maven/`** — Java (Spring Boot, JUnit, Micrometer)
+
+To add a package, create a YAML file:
+
+```yaml
+# registry/pip/my-library.yaml
+name: my-library
+description: "Short description of the library"
+repository: https://github.com/org/my-library
+
+versions:
+  - min_version: "2.0.0"
+    source:
+      type: git
+      url: https://github.com/org/my-library
+      docs_path: docs
+    tag_pattern: "v{version}"
 ```
 
-You can:
-- Build from any git repository (GitHub, GitLab, Bitbucket, etc.)
-- Build from local directories
-- Download pre-built packages from URLs
-- Share packages via releases or any file host
+Version discovery is supported for npm, PyPI, and Maven Central. See existing definitions for examples.
 
 ---
 

package/dist/build.d.ts

@@ -1,6 +1,6 @@
 /**
  * Build utilities for generating documentation packages.
- * Parses markdown/MDX files and chunks them by section.
+ * Parses markdown/MDX, AsciiDoc, and reStructuredText files and chunks them by section.
  */
 export interface DocFrontmatter {
     title?: string;
@@ -23,3 +23,19 @@ export interface ParsedDoc {
  * Parse a markdown/MDX file and extract sections.
  */
 export declare function parseMarkdown(source: string, filePath: string): ParsedDoc;
+/**
+ * Parse an AsciiDoc file and extract sections.
+ * Chunks on level-1 headings (== Heading), which are equivalent to markdown h2.
+ */
+export declare function parseAsciidoc(source: string, filePath: string): ParsedDoc;
+/**
+ * Parse a reStructuredText file and extract sections.
+ * RST headings are text lines followed by underline characters (=, -, ~, ^, etc.).
+ * Chunks on the second heading level encountered (equivalent to markdown h2).
+ */
+export declare function parseRestructuredText(source: string, filePath: string): ParsedDoc;
+/**
+ * Parse a document file, auto-detecting format from file extension.
+ * Supports: Markdown (.md, .mdx, .qmd, .rmd), AsciiDoc (.adoc), reStructuredText (.rst)
+ */
+export declare function parseDocument(source: string, filePath: string): ParsedDoc;