Document Types

An AiNecto project can manage the current standard, executable work, source materials, and specialized deliverables in the format best suited to each purpose. Start with one Markdown document and add other types only when real work requires them.

Recommended order

1. Use Markdown to record the goal, scope, decisions, and questions.
2. Use Kanban to manage executable work and review flow.
3. Add HTML, Design, Diagram, OpenAPI, File, or ERD documents when needed.
4. Reflect decisions discovered in those deliverables back in Markdown.

Markdown

The default project memory for goals, requirements, decisions, open questions, review results, and next actions.

Kanban

Manages card types, owners, priorities, due dates, completion criteria, review, and blocked states. Requirements and result documents can be linked to cards.

HTML

Creates browser-based screens, prototypes, reports, guides, dashboards, and other rendered content for review.

Design

Lays out several screen mockups on one canvas so you can compare them, then open one to try it. Your AI creates and changes them over MCP: create_documents with type design, then design_apply_changes (baseRevision is required). It reads them with get_document and design_get_boards. You can't create or edit mockups directly in the web app; there you can view, comment, share, restore a version, and download a mockup as a PNG.

create_document_images does not support Design documents (UNSUPPORTED_TYPE). Download images in the web app or from the public link (sign-in required). For a Design document, get_document returns only relation counts. Each document keeps up to 100 versions; the oldest are removed first.

Diagram

Uses nodes, connections, and groups to express workflows, system structures, state changes, information architecture, and conceptual relationships.

OpenAPI

Manages API paths, requests, responses, authentication, and error contracts as a structured specification.

File

Stores source materials and output files—such as images, PDFs, video, audio, text, code, and CSV—in the project tree.

ERD

Designs tables, columns, indexes, enums, and relationships as a structured data model. Use it when requirements and domain decisions need to become a database structure.

File versus attachment

A File is an independent document in the project tree. An attachment is kept with a particular document. Summarize important information and evidence in Markdown instead of leaving it only in a file.

Choose by purpose

• Current standard → Markdown
• Ownership and state → Kanban
• Browser-based presentation or interaction → HTML
• Screen mockups to compare side by side → Design
• Flow, relationship, or structure → Diagram
• API contract → OpenAPI
• Source or output file → File
• Database structure → ERD

All types follow the permissions and context of the same workspace and project.

Next, go to Markdown Documents.