Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qoder.com/llms.txt

Use this file to discover all available pages before exploring further.

Applies only to version 1.0.0 and above.
Generated synchronously with the Repo Wiki, a Knowledge Card is a high-density knowledge unit extracted from code. It stores architecture documents, code specifications (Spec), and tech stack information in a format that the Agent can easily consume directly. It continuously tracks code changes during every commit, maintaining real-time accuracy and relevance. Knowledge Card

​
Use Cases

  • Architecture Document-Driven System Understanding: Based on pre-built architecture documents, the Agent can quickly answer questions like “What is the overall design concept of this module?” or “What are the dependencies between these services?” without repeatedly searching the codebase.
  • Code Specification (Spec)-Guided Development Tasks: When you need to ensure code style, interface design, or business logic complies with team standards, the Agent can refer directly to the specification knowledge, supporting scenarios like:
    • Automatically aligning with naming conventions and interface agreements when adding features
    • Quickly verifying if implementations meet spec requirements during code review
    • Identifying potential risks that violate specs when fixing bugs
  • Tech Stack Knowledge Accelerating Technical Decisions: Combining pre-configured tech stack information, the Agent efficiently supports the following tasks in context-limited or cross-language/framework scenarios:
    • Evaluating compatibility when introducing new dependencies
    • Generating code snippets that conform to the current tech stack style
    • Answering technical environment questions like “Which frameworks and versions are used in the current project?”

​
Knowledge Card Types

  • Architecture Documents Records the overall design concepts of modules, service dependencies, and key decisions, helping the Agent understand the complete system without reading code line-by-line.
  • Code Specifications (Spec) Accumulates team coding standards, naming conventions, interface agreements, and business logic constraints, ensuring the Agent automatically aligns with team standards when generating code.
  • Tech Stack Records frameworks, libraries, and version information used in the project, helping the Agent make decisions that match the current technical environment when introducing new dependencies or generating code snippets.

​
Knowledge Card Generation

It is recommended to select the main branch and core development branches for generation to cover the core content of the project. During generation, completed cards can be previewed in real-time without waiting for the entire process to finish.
Generation Recommendation: Prioritize Knowledge Card generation on the main branch (main / master) and frequently used team development branches to ensure the Agent understands the most critical business logic and code structures.

​
Sharing and Multilingual Knowledge

Knowledge Card sharing helps knowledge flow more efficiently within your team. When you generate Knowledge Card locally, the system automatically saves the data to a dedicated directory in your code repository: .qoder/repowiki. You can commit and push this directory to a remote branch. Team members can then pull the generated Knowledge Card content via git pull—no extra configuration required. Additionally, Knowledge Card supports multiple languages. You can select your preferred language when generating them (currently supporting English and Chinese). Based on your language choices, the system automatically creates independent subdirectories for each selected language (e.g., zh/, en/).

​
Billing

Knowledge Card generation and updates consume Credits as usual. You can check the consumption records in Usage - Credits.