Project-specific documentation or coding standards are saved to the ainote memory system, making them accessible for future sessions and multi-device sync.
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.
- Category: Software development
- Effect: Changes data in your accounts
- MCP servers: ainote MCP (https://koskamo.com/explore/ainote-mcp)
- Source: 5분 Quickstart · ainote 개발자 문서 (https://docs.ainote.dev/guide/quickstart)
- Source quote: "Claude 가 create_dev_doc 호출: json { "title" : "api-naming-convention.md" , "category" : "feedback" , "content" : "# API Naming \n\n 우리는 Stripe 방식으로 snake_case..." }"
- Playbook page: https://koskamo.com/explore/use-cases/save-developer-documentation-to-memory
Prompt: Save this to memory: 'We use snake_case for API responses, never camelCase.' Title it 'api-naming-convention.md' under category 'feedback'.