The Freelancer's Guide to Cursor Rules: One File Per Client

Have you ever started a new freelance project and spent the first 3 days just explaining your setup to the AI? Your stack, your coding style, your client's requirements, your preferred patterns — over and over again, with every new conversation. I did. Then I stopped. ## The Freelancer's Context Problem When you're juggling 3-4 clients at once, each project has its own: - Tech stack and versions - Code style preferences - Business logic quirks - Naming conventions - Things the client explicitly hates Most freelancers handle this by re-explaining everything every session. Senior freelancers keep a mental model. Smart freelancers build systems. ## One File Per Client Here's the setup that changed how I work: I keep a file in every client project. Not a generic one — a specific, living document that captures everything Cursor needs to know to produce useful output immediately. any ## Why This Pays Off Compoundingly Session 1 with this file: Cursor writes code that fits the project without me explaining anything. Session 10: The file has grown. It includes patterns we established, decisions we documented, things we discovered broke. Session 50: I have institutional knowledge captured in a file. When I onboard a subcontractor, I hand them the file. When the client asks why we made a decision 3 months ago, the answer is there. ## The Proposal Angle Here's something most freelancers miss: a well-maintained file is also a scoping tool. Before I write a project proposal, I spend 30 minutes building a draft based on the client's requirements. It forces me to think through: - What stack decisions need to be made upfront - What context I'll need during development - What patterns the client will likely insist on By the time I write the proposal, I actually understand the project. My estimates are better. My questions to the client are sharper. I win more projects. ## The Freelancer's Cursor Setup If you're billing by the hour, AI context efficiency directly affects your margin. Here's what I run: **Per-client rules** (in each project ): - Client business context - Tech stack decisions - Things that are live and untouchable - Current sprint focus **Global rules** (in Cursor settings): - Your personal coding style - Your preferred patterns for common tasks - Your default error handling approach - Languages/frameworks you hate and why The combination means Cursor knows you + knows the client. Output quality goes up. Revision cycles go down. ## The Real Unlock The dirty secret of freelancing with AI is that most people use it like a search engine with autocomplete. They ask questions. They paste code. They explain the same context 50 times. The freelancers who are quietly doubling their output are the ones who invested 20 minutes building proper context infrastructure. Your file isn't a configuration file. It's a knowledge system. --- *If you want a head start, I put together a Cursor Rules Pack with 7 production-tested templates for common freelance scenarios — client onboarding, API integrations, SaaS projects, and more. [Check it out here](https://oliviacraftlat.gumroad.com/l/wyaeil).*