AI Agent Hub
Back to plugins
🤖

project-ai-docs

Model Inference Updated 2026.08.16

Run the following command in DeepSeek Harness:

dsh plugin install igugyj/project-ai-docs

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install igugyj/project-ai-docs in the DeepSeek Harness terminal to install this plugin; the source repository is https://github.com/igugyj/project-ai-docs .

About this plugin

The quiet killer in AI-agent-assisted development is not low quality in a single response, but context drift across sessions. A new window opens and the agent has forgotten last round of architecture decisions, cannot tell which file paths were actually verified versus merely assumed, and all hard-won knowledge evaporates the moment the chat log scrolls away.

project-ai-docs gives every project a persistent docs/.ai/ knowledge base. index.md is the single entry point and a priority routing table; documents are organized into four layers (core, modules, config, best-practices) with explicit token budgets. Hard constraints sit at the very top of the index, ahead of every technical detail. The agent reads the index before acting, point-reads only the relevant slice for the current task, and must write back updates plus a changelog entry when the task ends, so knowledge lives in files rather than in session memory. A human/agent separation keeps the user-facing README and the agent-facing docs/.ai namespace cleanly apart, and every recorded fact is required to be a tested path, version, or command that can be verified.

Built for individual developers and teams that rely on Claude Code, Codex, DSH, or similar agent hosts day to day, and for multi-module, long-cycle projects where cross-session project awareness is non-negotiable.

Use Cases

  • Agent reads index and changelog at session start to instantly restore project context
  • Point-read only relevant document slices per task to avoid full-load token waste in multi-module projects
  • Write back document updates and log changelog entries after each task to persist knowledge across sessions

Best For

  • Developers who work daily with agent hosts such as Claude Code, Codex, and DSH
  • Teams maintaining multi-module, long-cycle projects that require consistent cross-session awareness
  • Solo developers who want structured documentation to replace session memory for durable project knowledge