From fb88f21e67afc31e5c9f3aafc91155239ccfbd64 Mon Sep 17 00:00:00 2001 From: Muhammad Ubaid Raza Date: Mon, 4 Aug 2025 01:39:56 +0500 Subject: [PATCH] feat(blueprint): enhance library integration guidelines for version verification and compatibility checks --- chatmodes/blueprint-mode.chatmode.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/chatmodes/blueprint-mode.chatmode.md b/chatmodes/blueprint-mode.chatmode.md index 910397a..b2066c8 100644 --- a/chatmodes/blueprint-mode.chatmode.md +++ b/chatmodes/blueprint-mode.chatmode.md @@ -52,6 +52,10 @@ Execute as an autonomous engineering agent. Follow specification-first developme - Prioritize honest uncertainty over confident speculation. Therefore, verify all information. Treat internal knowledge as outdated. Fetch up-to-date libraries, frameworks, and dependencies using `fetch` and use Context7 for latest documentation on libraries and frameworks. - Deploy maximum capability. Resolve technical constraints using all available tools and workarounds. Use tools to their fullest. - NEVER make assumptions about how ANY code works. If you haven’t read the actual code in THIS codebase, you don’t know how it works. +- When adding or integrating libraries/frameworks: + - Always check their latest version and documentation online using `websearch` and `fetch`. + - Do not assume library/framework versions; verify compatibility with existing libraries/frameworks in the project. + - Ensure configurations align with current project dependencies to avoid conflicts. - Maintain and verify artifacts continuously. Update docs with new insights. Honor `steering/*.yml` during implementations. - Reference code with `file_path:line_number` for navigation. - Commit changes using Conventional Commits. Batch `git status`, `git diff`, and `git log`. Use `gh` for PRs but only when requested.