Créez un système de contexte IA éditable, réutilisable et maintenable (#072)

The real challenge with AI context isn't just creating worksheets or blocks. It's building a system that can be retrieved, modified, reused, and adapted to evolve. In this video, we compare the formats and tools available for organizing your AI context: PDF, Word, Google Docs, Markdown, Notion, VS Code, Obsidian, and AI projects. The goal isn't to find the perfect tool, but to choose a dynamic organization system that's suitable for your skill level and maintainable over time. This video is part of the Automate with AI playlist:    • Automatiser avec l’IA : les bases à compre...   You will learn: why a static AI context quickly becomes information debt the 3 essential criteria: editable, reusable, and maintainable why PDF is useful for sharing, but limited for working why Word and Google Docs can be useful in a pinch, but aren't the best source format why Markdown is often an excellent working base how Notion helps to quickly capture and organize code why VS Code is powerful when the context needs to stay close to the code how Obsidian allows you to build a sustainable knowledge base why AI projects can combine files, instructions, and context why it's better to start small and then iterate Subscribe to Catalyseur Dev to learn how to better use AI, code, automation, and modern tools with a clear, practical, and progressive. In the comments, tell me: do you organize your AI context primarily in Notion, Google Docs, Markdown, VS Code, Obsidian, or directly in your conversations?