From cklph-architect
Options-not-estimates. Use when writing a proposal after discovery, following up on a "send me a quote" ask, or any time you're tempted to send a single number.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cklph-architect:proposeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A single number is a commodity quote. The client compares it to other numbers and you've already lost the conversation. **Always offer 2–3 tiered options.** Three makes you think harder; one makes the client argue, three makes them choose.
A single number is a commodity quote. The client compares it to other numbers and you've already lost the conversation. Always offer 2–3 tiered options. Three makes you think harder; one makes the client argue, three makes them choose.
This is the move most people get wrong. Bad tiers are S/M/L of the same deliverable — "20 hours / 40 hours / 60 hours of the same thing." That's still selling hours; the client just picks the cheapest.
Good tiers are distinct outcomes — each one a real choice about how much of the problem to solve, how durably, and with what level of commitment. Examples:
Each tier should feel like a different answer to the client's question, not a different size of the same answer.
scope format inside each tier.More than three options is decision paralysis. The client can't compare four things at once; they delay, then go cold. Two clean tiers often beats three muddled ones. If you can't articulate a real third tier, don't invent one.
Pair with discover (the source material for which options to offer), scope (format inside each tier), price (how to set the numbers), position (peer-not-vendor framing throughout), and engagement-shape (so each tier reflects the right shape — project / retainer / advisor / fractional).
npx claudepluginhub chykalophia/cklph-marketplace --plugin cklph-architectProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.