Conversation
The landing page opens by arguing that grep is insufficient, which only lands if the reader has already decided they have that problem. Someone arriving cold — from a directory listing, a search result, a link in a thread — has a cheaper question first: is this for me? Answer it before the argument. Three situations, phrased as the visitor's week rather than the product's features: an agent that should arrive knowing the codebase, research across code you didn't write, and a spread out team whose agents should all read the same index. Each maps to something the project actually does — hooks and skills, workspaces, and the multi-user server with roles, view-groups and per-user API keys — so the section qualifies rather than promises. Reuses .why-grid for layout so the mobile collapse already applies; the marker is a small arrow instead of a display-size numeral, otherwise this section and "The problem" below it read as one long numbered list. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Spec work, security passes and sprawling microservice estates are the cases people described in their own words, and each already maps to something the tool does — references and touchpoints for scoping, the five search modes for tracing what reaches a risky function, workspaces for a system split across a dozen repos. The security card says plainly that cix does not scan for CVEs. It finds everything worth scanning, which is a different and more defensible claim than implying a scanner. Cards move to a data array now that there are six of them; the grid already handles the second row and the mobile collapse. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
feat(site): add a "who it's for" section above the problem pitch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotion of #211 to
main.Adds a six-card
Who it's forsection between the hero andThe problem,so a cold visitor can answer "is this for me?" before the page starts
arguing that grep is insufficient. Situations covered: agent context, research
on unfamiliar code, spec/scoping work, security passes, multi-repo
microservice estates, and distributed teams.
Every card maps to shipped behaviour, and the security card explicitly says
cix is not a CVE scanner.
Test plan
The problematdesktop and mobile widths.
🤖 Generated with Claude Code