README: deep polish for SEO/GEO + verified accuracy#13
Conversation
Restructure README to a clear value-prop + What-it-is + verified Quick start + Usage + how-it-works + best-fit search keywords + Links (kyanitelabs.tech and sibling repos). Commands verified against the actual project files; no code changed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ddad110b1a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # 3. In a second terminal, start the frontend (Next.js) | ||
| cd caedo-web | ||
| npm install | ||
| npm run dev # serves on http://localhost:3002 by default |
There was a problem hiding this comment.
When a fresh user follows this quickstart, npm run dev runs next dev without --port or a shell PORT, so Next starts on its documented default port 3000; PORT=3002 in the copied root .env does not affect server boot. That leaves the README pointing users at 3002 while the repo's own smoke test checks http://localhost:3002 and suggests PORT=3002 npm run dev, so the documented install can appear broken even though the app is running on 3000.
Useful? React with 👍 / 👎.
1 participant
README deep polish — SEO + GEO + accuracy
Restructures the README for human readers, search engines, and LLM summarization (GEO), with every command verified against the actual project files. No code changed — only
README.md.What changed:
🤖 Generated with Claude Code