8.8.7.3.3 - How to Use Cursor: Chatting with your repo to find and edit specific CSS classes or Liquid logic (Difficulty: Hero | Path: Scale)

For years, modifying a Shopify theme meant playing a frustrating game of "hide and seek" with file structures. You wanted to change the color of the "Add to Cart" button, but you first had to determine if that style lived in theme.scss.liquid, base.css, or perhaps buried inline within a specific snippet file like product-form.liquid. You spent 80% of your time searching for the right line of code and only 20% of your time actually writing the fix. This inefficiency is not just annoying; it is a bottleneck that stifles experimentation and slows down your speed to market.

Cursor fundamentally changes this dynamic by treating your entire codebase—every folder, asset, and snippet—as a single, searchable memory bank. It does not just "autocomplete" what you are typing; it understands the context of your entire project. By indexing your repository, Cursor allows you to have a plain-English conversation with your theme. Instead of hunting for classes, you ask, "Where is the logic that controls the mobile menu drawer?" and Cursor points you exactly to the line number in the correct file, often explaining how the code works along the way.

This lesson is the operational manual for that capability. We are moving beyond the conceptual "what is AI" into the tactical "how do I use this." We will focus specifically on the two primary workflows that define the Cursor experience: Chat (Cmd+L) for discovery and understanding, and Inline Edit (Cmd+K) for rapid, precise execution. These two shortcuts are the controls for your new engine. Mastering them turns a terrifying folder of 200+ Liquid files into an accessible, malleable toolkit that you can reshape at will.