Progressive Clarity — AI responses worth reading

See it work

The detail you need, as you need it.

Ask a simple question, explore a bigger decision, then follow up. See how the response changes with you.

Pick an example

Everyday

Keeping your family photos safe

01 Focused Quick question

You
Is cloud photo sync the same as a backup?

Assistant
Not necessarily. Sync keeps one library matched across devices, so deletions and unwanted changes can spread. A backup is a separate copy you can restore.
02 Full More to consider

You
My cloud library holds years of family photos. Should it be the only copy?

Assistant

At a glance

No. Keep at least one independent backup that survives accidental deletion, account lockout, or failure of the synced library.

In context

Sync helps when a device is lost, but it is designed to mirror changes—not preserve every past state. Deleting the wrong folder or losing account access can remove the recovery path you thought you had.

At depth

Keep the live library plus a local backup and a second off-site or versioned copy. Automate both, protect recovery credentials, and test restoring a few photos before trusting the setup.
03 Focused Follow-up

You
My library is 280 GB and grows by 3 GB a month. What capacity covers three years plus 25% headroom?

Assistant
You need about 485 GB of usable space: (280 + 3 × 36) × 1.25. A 1 TB drive is the practical choice once formatting, version history, and continued growth are included.

Developer

Keeping payment records reliable

01 Focused Quick question

You
Is Redis a database?

Assistant
Yes. Redis is an in-memory data store that can persist data, but its durability depends on how it is configured.
02 Full More to consider

You
We process card payments. Should Redis be our sole source of truth for payment state?

Assistant

At a glance

No. Keep canonical payment state in transactional storage with tested recovery, and use Redis only for roles where data loss is recoverable.

In context

Payment updates often span status, money movement, idempotency, and audit history. A transactional database can commit related changes together; explicit transition records preserve what happened and when.

At depth

Redis can still accelerate reads, coordinate short-lived work, and hold idempotency keys. Design cache loss as recoverable, bound lock lifetimes, and test replay, failover, stale reads, and delayed webhooks before production use.
03 Focused Follow-up

You
Our provider retries webhooks for up to 72 hours, and we require a 24-hour buffer. What TTL should the idempotency keys use?

Assistant
Use a 96-hour TTL. That covers the 72-hour retry window plus the required 24-hour buffer.

Crypto broker

Controlling execution risk

01 Focused Quick question

You
What does slippage mean in a trade?

Assistant
Slippage is the difference between the expected execution price and the average price actually received. It usually grows when an order is large relative to available liquidity.
02 Full More to consider

You
A client wants to buy $750,000 of a thinly traded token. Only $220,000 is offered within 1% of the current price. Should I send one market order?

Assistant

At a glance

No. The order is more than three times the visible depth, and a market order leaves price impact uncapped. Use an approved execution plan with a hard slippage limit.

In context

The top quote represents only the next fill, not the average for the whole order. Consuming the book can move later fills sharply, while fragmented venues, fees, and latency can widen the realized cost.

At depth

Confirm the client mandate and venue limits, then compare staged limit orders, approved liquidity providers, and venue splitting. Define the benchmark, time window, cancellation rule, and post-trade review before routing.
03 Focused Follow-up

You
The client allows 60 basis points. Expected impact is 42 bps and fees are 8 bps. Are we inside the limit?

Assistant
Yes—50 bps total, leaving 10 bps of headroom. That assumes both estimates use the same notional and no other execution costs apply.

These conversations are written examples, not live AI output. The broker scenario is educational, not investment or execution advice.

How it works

Answer first. Go deeper when it helps.

The goal is a useful answer at the right level of detail, all the way through the conversation.

01
Get to the point

Start with the answer and anything that changes how you should use it. Add reasoning and detail where they help.
02
Keep it flowing

Follow-ups get focused answers. Keep exploring without a recap of everything you've already covered.
03
Bring it together

When the plan changes or it's time to decide, pull together what matters now. Use more structure only if it makes things clearer.

Focused

A direct, complete answer.

For quick facts, follow-ups, and decisions that can be explained simply. Just the answer and the context you need to use it.

Full

Three views, each worth reading.

At a glance — the answer and any caveat that changes what it means for you.
In context — why it makes sense, what matters, and what to do next.
At depth — evidence, alternatives, or practical details when you want to dig in.

The skill guides your assistant's responses. It can't guarantee activation, accuracy, or consistency across chats. Live-app behavior hasn't been verified.

Install

Use it in the tools you already know.

Choose your app to get started with version 0.5.0. Progressive Clarity is free and open source.

01

Chat apps

Published 0.5.0

ChatGPT

Install from OpenAI's Plugins Directory.

Open the Progressive Clarity listing below.
Install version 0.5.0.
Start a new chat and try one of the prompts below.

Confirm: The installed version is 0.5.0.

Open in ChatGPT Download ZIP

Package 0.5.0

Claude.ai

Add Progressive Clarity as a custom Skill in Claude.

Download the Claude.ai Skill.
Enable code execution, then open Customize → Skills.
Choose Add, upload the ZIP, and enable the Skill.

Confirm: It is enabled in Customize → Skills, then try a prompt below.

Download for Claude.ai Anthropic guide

02

Coding tools

Available 0.5.0

Claude Code

Install from the project's public marketplace. Anthropic review has passed; the official directory listing is still syncing.

Run these commands in a terminal:

claude plugin marketplace add firaskafri/progressive-clarity
claude plugin install progressive-clarity@firas-kafri-plugins

Start a new Claude Code session.
Run /progressive-clarity and ask a question.

Confirm: claude plugin list reports version 0.5.0.

View on GitHub Download ZIP

Package 0.5.0

Cursor

Add the skill to one project or use it across projects.

Download and extract the Cursor Skill.
Move the progressive-clarity folder into one of these folders:

.agents/skills/
.cursor/skills/
~/.agents/skills/
~/.cursor/skills/

Open Cursor in that project and start a new Agent chat.

Confirm: Type /, search for Progressive Clarity, and select it for one message.

Download for Cursor Cursor guide

Platform names and marks belong to their respective owners.

Your first chat

Start with these two questions.

After installing, try these prompts in a new chat. The first calls for a direct answer; the second benefits from reasoning and practical steps.

Suggested: Focused A quick question

Is cloud photo sync the same as a backup?

Suggested: Full A bigger decision

My cloud library holds years of family photos. Should it be the only copy? Recommend a backup setup I can rely on.

Have a preference? Just ask.

Keep it brief.
No headings.
Answer in Focused format.
Use Full format with all three views.

More examples

Clear answers start with good judgment.

Ask when a key detail is missing. Correct mistakes plainly. Respect the format you asked for.

01 Missing detail · Clarification Ask instead of guessing

Prompt

We have $420,000 in cash. How many months of runway do we have?

Response

What's your average monthly net burn—the cash you spend minus the cash you bring in?

Why ask: Runway depends on monthly net burn. Ask for the missing number rather than guess.

02 Changed recommendation · Full Own the mistake and update the advice

Prompt

Earlier you said the data migration was reversible. The vendor documentation confirms rollback is unavailable after conversion starts. Update your recommendation.

Response

At a glance

I was wrong: this migration cannot be rolled back once conversion starts. Pause until you've tested recovery and the cutover is approved.

In context

The earlier plan relied on undoing the migration if something went wrong. Since that's not possible, verify the backup and test restoring it before production.

At depth

Document the point of no return, who approves the cutover, and what would stop it before conversion. Define the checks to run afterward, and keep the source system read-only until validation is complete.

Why Full: The advice has changed, and the reasons and recovery steps need explaining. Simpler corrections can stay brief.

03 Your format · Focused Follow your lead

Prompt

No headings. In two sentences, explain why passkeys resist phishing better than passwords.

Response

Passkeys are tied to the legitimate site, so a fake login page cannot trick you into sending it a reusable secret. They also remove passwords that can be copied, guessed, or reused after a breach.

Why Focused: You asked for two sentences and no headings. The answer follows that request.

These are written examples, not live AI output.

Principles

Respect the reader's time.

01
Make every word count

Use as much detail as the question needs, even when the answer is short.
02
Add something new

Each section should help you understand more, not repeat the last one.
03
Ask what matters

Ask for missing details that would actually change the answer.
04
Show the assumptions

Keep assumptions beside the advice, especially when numbers are involved.
05
Fix mistakes plainly

Say what was wrong, what's right, and what changes because of it.
06
Keep the work usable

Let code be code, stories be stories, and step-by-step guides stay complete.

AI responses you actually want to read.

The detail you need, as you need it.

At a glance

In context

At depth

At a glance

In context

At depth

At a glance

In context

At depth

Answer first. Go deeper when it helps.

Get to the point

Keep it flowing

Bring it together

A direct, complete answer.

Three views, each worth reading.

Use it in the tools you already know.

Chat apps

ChatGPT

Claude.ai

Coding tools

Claude Code

Cursor

Start with these two questions.

Have a preference? Just ask.

Clear answers start with good judgment.

At a glance

In context

At depth

Respect the reader's time.

Make every word count

Add something new

Ask what matters

Show the assumptions

Fix mistakes plainly

Keep the work usable

Make your next AI conversation worth reading.