Capture project architecture, coding conventions, and tech stack details for Qoder to use in tasks.
Knowledge Cards are compact knowledge units extracted from your codebase. Together with Repo Wiki, they provide project context for Qoder. Cards record architecture, coding conventions, and tech stack details to help agents understand projects, write code, and troubleshoot issues.
With Citation enabled, Qoder can automatically use Knowledge Cards in tasks within the same workspace. You can also specify the knowledge to reference, for example: "Add an order cancellation API using the order module's architecture and coding conventions."
Invoke the
Knowledge Cards support English and Simplified Chinese. Exported files are stored by language in
On the Knowledge Cards Overview page, open More (âŠ):
Generation and updates consume Credits as usual. Check the records in Usage - Credits.
Knowledge Card Types
- Architecture Documents: Record module structure, service dependencies, and design decisions to explain system architecture and change impact.
- Code Specifications (Spec): Capture naming conventions, interface agreements, and business constraints for development, code review, and troubleshooting.
- Tech Stack: Record the frameworks, libraries, and versions used in the project to guide dependency choices and implementation.
Generate and view Knowledge Cards
- Open More in the sidebar, select Repo Wiki, and open the target repository.
- Switch to the Knowledge cards view and choose English or ç®äœäžæ under Language.
- Review Auto Update, Auto Export, and Citation, then select Generate.
- Search for or select a card on the left to view its details on the right.

Use Knowledge Cards in a task
With Citation enabled, Qoder can automatically use Knowledge Cards in tasks within the same workspace. You can also specify the knowledge to reference, for example: "Add an order cancellation API using the order module's architecture and coding conventions."
Edit generated knowledge
Invoke the /knowledge-edit skill in the task input in the target workspace, then describe which cards to change and what to update. You can provide design documents, API documentation, or other references. Review the results on the Knowledge Cards page, then export if you want to share them through Git.
Sharing and multilingual knowledge
Knowledge Cards support English and Simplified Chinese. Exported files are stored by language in .qoder/repowiki/knowledge/zh/ or .qoder/repowiki/knowledge/en/.
Commit and push .qoder/repowiki to your Git repository so team members can pull the files with git pull, then import them. Where team knowledge sharing is available, select Pull from team in the More (âŠ) menu to retrieve published team knowledge.
When account and organization policy allow, Qoder can automatically retrieve available team knowledge for the current repository, branch, and language. You can still use the existing team-pull action to retrieve it manually.
Knowledge Card Import and Export
On the Knowledge Cards Overview page, open More (âŠ):
- Export to
.qoder/repowiki: Save cards for the current branch and language to.qoder/repowiki/knowledge/under the project root, in thezh/oren/language subdirectory. Enable Auto Export to export automatically after generation or updates. - Import from
.qoder/repowiki: Read Knowledge Cards from the corresponding language subdirectory under.qoder/repowiki/knowledge/in the project root and replace the corresponding current content after confirmation. Use this after pulling files through Git or editing them manually, without regenerating.

Knowledge Cards are stored in
.qoder/repowiki/knowledge/, separately from Wiki pages. Keep the complete .qoder/repowiki directory structure when sharing or moving it. Import replaces the corresponding Wiki pages and Knowledge Cards for the current branch and language. Export overwrites the corresponding language directories, so import any manual file edits before exporting.