Rescoped — part of this landed. The README now opens with a value proposition, a host line and an embedded demo above the Commands table (see #19). What is still missing is the legible half: the before/after and the concrete first-session deltas.
Problem
README.md currently opens with:
- tagline — "Make your AI code like it already knows your repo",
- one paragraph of what it does, one line of supported hosts,
- "See it work" +
demo.gif,
- the Commands table.
That answers "what is this" and shows motion, but a first-time visitor still cannot see what changes in their repo after install — there is no before/after and no statement of the first-session deltas. The demo carries the whole burden of conveying outcome, and a reader who does not watch it gets nothing.
Expected result
A tight (<20-line) block above the Commands table:
- a two-column before/after diagram — flat ad-hoc markdown pile → typed, related graph — as a Mermaid flowchart so it stays diffable and needs no asset;
- three short outcome bullets naming concrete first-session deltas ("your ADRs are reachable by the agent without you pasting them", etc.).
It should sit next to demo.gif, not replace it: the gif shows the loop in motion, the diagram shows the end state.
Impact
Communicates value in the first screenful for readers who don't play the demo, reducing bounce and raising the odds a visitor installs or contributes. Pure-markdown change with no external assets — a good first contribution.
Proposed approach
Acceptance criteria
- The diagram renders on GitHub (Mermaid in a fenced ```mermaid block).
- The outcome bullets name concrete deltas, not adjectives.
References
Design rationale: .archcore/plugin/readme-first-60-seconds.idea.md (status: draft). Code: README.md.
Problem
README.mdcurrently opens with:demo.gif,That answers "what is this" and shows motion, but a first-time visitor still cannot see what changes in their repo after install — there is no before/after and no statement of the first-session deltas. The demo carries the whole burden of conveying outcome, and a reader who does not watch it gets nothing.
Expected result
A tight (<20-line) block above the Commands table:
It should sit next to
demo.gif, not replace it: the gif shows the loop in motion, the diagram shows the end state.Impact
Communicates value in the first screenful for readers who don't play the demo, reducing bounce and raising the odds a visitor installs or contributes. Pure-markdown change with no external assets — a good first contribution.
Proposed approach
Acceptance criteria
References
Design rationale:
.archcore/plugin/readme-first-60-seconds.idea.md(status: draft). Code:README.md.