Bibliography & Resources

Bibliography & Resources

Masood, A. (2025). Context Engineering: Elevating AI Strategy from Prompt Crafting to Enterprise Competence. Medium . – Defines context engineering vs prompt engineering, and principles for providing complete and dynamic context to LLMs. • 59 3

• Reddit discussion on Cursor AI (2024). "Context is King" r/cursor . User tips on giving Cursor AI more context (tagging files, using notepads and rules files) to improve results. • 18 60
• DataCamp (Feb 2025). Windsurf AI: Features, Setup, Use Cases . Documentation of Windsurf's context features like Local Index and Memories (persistent user rules and automatic memory across interactions). • 25 26
• Anthropic (2024). Introducing the Model Context Protocol . Blog/announcement describing MCP as a standard to connect AI assistants with external data/tools, enabling rich context retrieval (e.g., filesystem, APIs). • 19 22
• Sygnal (Apr 2025). Claude Desktop + MCP . Article illustrating how Claude Desktop integrates MCP for tools like Webflow, and best practices (using projects for context, token management tips). • 61 62
• Stack Overflow & Reddit threads on "vibe coding" (2023–2024) . Various community perspectives on vibe coding definition, skepticism, and guides (e.g. "The Ultimate Vibe Coding Guide"), highlighting typical behaviors and issues encountered by vibe coders. • 63 41
• GitHub Copilot Chat Docs (2023). Manage context for AI VS Code . Official documentation on how to explicitly reference workspace context (#codebase, #changes, etc.) in Copilot Chat to supply it with needed information. • 64 35
• Knuth, D. (1984). Literate Programming. (Historical reference) Proposed weaving code and documentation; conceptually influential for context-rich coding. •
• Xu, S. et al. (2022). Prompt Chaining and Tool Use in LLMs. (Research paper) Discusses how breaking tasks and using tools (retrieval) can effectively extend context beyond the raw window, forming basis for techniques used in context engineering. •

(Note: Above sources have been cited inline in the report where relevant. Additional internal documents and user experiences were referenced as needed to inform the analysis.)