A Proposal That Reads Like a Page
Orders the blocks the way a buyer scrolls on a phone, instead of pouring a printed document into a web page and hoping.
What it is for
A proposal built as a web page fails when it is laid out like a printed one: cover page, eleven paragraphs, then the price. This orders the blocks the way a buyer actually scrolls — outcome and price on the first screen, one idea per block, nothing longer than three lines on a phone. It also tells you which blocks would fall apart as a PDF, and where a hurried reader would quit.
The skill
Lay this proposal out as a web page that gets read by scrolling on a phone, not as a document that gets printed. What we are proposing: [...] Who opens it first: [role] Who has to approve it: [role] Their deadline: [...] Block order, top to bottom: 1. First screen: the outcome in one line, their name, and the price or the price range. No cover page of our logo. They know who sent it. 2. Their problem in their words. Three sentences. No solution yet. 3. What we will do, as deliverables with dates. One block per phase, not one block containing every phase. 4. Proof: one relevant case, with a number in it. 5. Price. 6. Terms and what happens next. Rules per block: - One idea per block. If a block needs a subheading, it is two blocks. - No paragraph longer than three lines on a phone. Rewrite it; do not shrink the text to make it fit. - Anything only a lawyer reads goes into a collapsed or linked section, not into the scroll. - A video replaces a paragraph, it does not sit on top of one. If both stay, cut the paragraph. - Every image must carry information. Delete stock photography of handshakes. Before I send, tell me: - the first sentence a phone reader sees, quoted back to me - which blocks would collapse into nonsense if this were exported to PDF - where a reader in a hurry would decide to stop
How to install it
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.