Every client proposal I send comes from a Skill.
7 August 2026

Every client proposal I send comes from a Skill.
It produces the same structure, the same pricing logic and the same voice every single time, which is the whole point. A client can't tell whether I wrote their proposal on a good day or a rushed one.
Last month that consistency turned into a problem.
I needed a new offer, something I hadn't pitched before. I opened a chat with the proposal Skill loaded and asked for ideas. I pushed it four or five times, rewording the ask, and every answer came back looking like one of my existing proposals wearing a different hat. New words, same shape.
The Skill wasn't broken. Following the pattern is its job. I'd loaded a pattern-follower and then asked it to break patterns.
So I opened a blank chat instead, with no Skills and no Project files loaded. I asked the same question and got an offer I'd never have arrived at on my own.
A loaded chat pulls every answer towards what's already in it. An empty one has nowhere to pull from, so it has to actually think.
The rule I run now: Skills for work I want done the same way every time, like proposals and reports. An empty room for anything I haven't thought of yet.
Next time you need an idea rather than an output, open a blank chat and leave your carefully built context at the door.