Save developer documentation to memory
Project-specific documentation or coding standards are saved to the ainote memory system, making them accessible for future sessions and multi-device sync.
How it works
Changes data in your accountsSoftware development
The agent takes user-provided documentation content and metadata (title, category). It calls the ainote MCP server's create_dev_doc tool to store this information. This is useful for persisting context like API conventions or team guidelines. The user should ensure the content is accurate before saving.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Save developer documentation to memory
Save this to memory: 'We use snake_case for API responses, never camelCase.' Title it 'api-naming-convention.md' under category 'feedback'.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Claude 가 create_dev_doc 호출: json { "title" : "api-naming-convention.md" , "category" : "feedback" , "content" : "# API Naming \n\n 우리는 Stripe 방식으로 snake_case..." }5분 Quickstart · ainote 개발자 문서