Skip to content

feat(dashboard): update landing page messaging for vibe coders#38

Merged
duyet merged 1 commit into
mainfrom
claude/landing-intro-messaging
Mar 17, 2026
Merged

feat(dashboard): update landing page messaging for vibe coders#38
duyet merged 1 commit into
mainfrom
claude/landing-intro-messaging

Conversation

@duyet
Copy link
Copy Markdown
Owner

@duyet duyet commented Mar 17, 2026

Summary

  • Reposition AgentState hero copy: "You're building AI agents — not a conversation database"
  • Add "Built for vibe coders" tagline — no SDK needed, just give your coding agent the docs
  • Dual code examples: vibe coder approach (paste agents.md URL) + REST API curl
  • Add agents.md as prominent CTA button alongside Get Started and API Reference
  • Update README intro to match new positioning

Test plan

  • Verify landing page renders correctly in light/dark mode
  • Check responsive layout on mobile
  • Verify agents.md link works

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation

    • Updated product messaging to emphasize API-first, agent-focused development approach
    • Added API documentation links and framework-agnostic positioning
  • New Features

    • Enhanced dashboard with dual code examples showcasing "vibe coder" and REST API integration patterns
    • Improved call-to-action with updated button text and responsive two-column layout

Reposition AgentState as the solution for devs who want to build agents
without building their own conversation database. Add "vibe coder" messaging
highlighting the no-SDK approach — just give your coding agent the agents.md
URL and let it wire things up.

- Update hero copy with new value proposition
- Add dual code examples: vibe coder approach + REST API
- Add agents.md as prominent CTA button
- Update README intro to match

Co-Authored-By: Duyet Le <me@duyet.net>
Co-Authored-By: duyetbot <bot@duyet.net>
Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @duyet, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the marketing and onboarding experience for AgentState by updating key messaging across the landing page and README. The changes aim to better communicate the product's value proposition to AI agent developers, particularly those who prefer a streamlined, "no SDK needed" approach, while still supporting traditional REST API integration.

Highlights

  • Hero Copy Repositioning: The main hero copy on the landing page and README was updated to "You're building AI agents — not a conversation database."
  • "Vibe Coders" Tagline: A new tagline "Built for vibe coders" was added, emphasizing ease of use without an SDK.
  • Dual Code Examples: The landing page now features two distinct code examples: one for the "vibe coder" approach using agents.md and another for the traditional REST API curl.
  • agents.md CTA: A prominent call-to-action button linking to agents.md was added to the landing page.
  • README Introduction: The README.md file's introductory section was updated to align with the new product positioning and messaging.
Changelog
  • README.md
    • Updated the introductory paragraph to reflect the new messaging, including the "You're building AI agents" and "Built for vibe coders" taglines.
  • packages/dashboard/src/app/page.tsx
    • Modified the main hero paragraph to emphasize the "not a conversation database" message.
    • Added a new paragraph introducing the "Built for vibe coders" concept.
    • Introduced a new "agents.md" button alongside "Get started" and "API Reference".
    • Refactored the code example section to display two distinct examples: one for the "vibe coder" approach and another for the direct REST API curl.
Activity
  • The PR was generated with Claude Code.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 17, 2026

📝 Walkthrough

Walkthrough

The PR updates README and dashboard homepage messaging to reposition the product from conversation storage/retrieval toward AI agent development. Changes include revised hero text, new call-to-action buttons, and a two-column code example layout showcasing different usage approaches.

Changes

Cohort / File(s) Summary
README Marketing Copy
README.md
Replaces descriptive text about storing/retrieving conversations with agent-focused messaging. Adds CTA promoting API docs and SDK-less approach.
Dashboard Homepage Redesign
packages/dashboard/src/app/page.tsx
Updates hero messaging from conversation database to AI agents; adds secondary paragraph for "vibe coders"; restructures code examples into two-column grid with "Vibe coder approach" and "REST API approach" sections; adds agents.md button and adjusts button styling.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Our agents now hop with pride so bright,
No database chains, just APIs in flight!
Two paths to code, vibe or REST divine,
We're bouncing past storage — pure agent design! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: updating landing page messaging to target 'vibe coders' with a new positioning and dual code examples.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/landing-intro-messaging
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the landing page and README with new messaging targeting 'vibe coders'. It introduces a dual code example on the landing page, showcasing both a prompt-based approach for AI agents and a traditional REST API curl example. The changes align well with the PR's goal. I have one minor suggestion to improve the accuracy of the new code example.

Comment on lines +115 to +117
<span className="text-green-600 dark:text-green-400/70">
{`agentstate.app/agents.md`}
</span>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The URL for the API docs appears to be incomplete as it's missing the https:// protocol. While a human developer might infer the protocol, an AI agent could interpret it as a relative path, leading to errors. It's best practice to use the full, unambiguous URL in documentation and examples, especially when the target audience includes automated agents.

Suggested change
<span className="text-green-600 dark:text-green-400/70">
{`agentstate.app/agents.md`}
</span>
<span className="text-green-600 dark:text-green-400/70">
{`https://agentstate.app/agents.md`}
</span>

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 5-7: The README currently points users to the API docs URL
(/dashboard/docs/) which is inconsistent with the landing page CTA that shares
agentstate.app/agents.md; update the README text to reference and link to
agents.md instead of /dashboard/docs/, ensuring the phrasing that tells "give
your coding agent the API docs" matches the landing page by replacing the API
docs URL with agentstate.app/agents.md (update the literal link and any
accompanying description to reference agents.md).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 80b3112a-6e8d-47f5-bfa7-fa71908d1de4

📥 Commits

Reviewing files that changed from the base of the PR and between 93bb4c5 and fa55d9b.

📒 Files selected for processing (2)
  • README.md
  • packages/dashboard/src/app/page.tsx

Comment thread README.md
Comment on lines +5 to +7
You're building AI agents — not a conversation database. Stop reinventing storage, analytics, and history management. Just call an API.

Built for vibe coders. No SDK needed — give your coding agent the [API docs](https://agentstate.app/dashboard/docs/) and let it wire things up. Or use the REST API directly with any language, any framework.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Inconsistent URL for "vibe coders" between README and landing page.

The README instructs users to give their coding agent the "API docs" link (/dashboard/docs/), but the landing page in page.tsx (lines 114-116) shows agentstate.app/agents.md as the URL to share with coding agents. The PR also adds an agents.md button as a prominent CTA.

Consider updating the README to reference agents.md instead, to match the landing page messaging:

Suggested fix
-Built for vibe coders. No SDK needed — give your coding agent the [API docs](https://agentstate.app/dashboard/docs/) and let it wire things up. Or use the REST API directly with any language, any framework.
+Built for vibe coders. No SDK needed — give your coding agent the [agents.md](https://agentstate.app/agents.md) and let it wire things up. Or use the REST API directly with any language, any framework.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 5 - 7, The README currently points users to the API
docs URL (/dashboard/docs/) which is inconsistent with the landing page CTA that
shares agentstate.app/agents.md; update the README text to reference and link to
agents.md instead of /dashboard/docs/, ensuring the phrasing that tells "give
your coding agent the API docs" matches the landing page by replacing the API
docs URL with agentstate.app/agents.md (update the literal link and any
accompanying description to reference agents.md).

@duyet duyet merged commit eaeed86 into main Mar 17, 2026
4 checks passed
@duyet duyet deleted the claude/landing-intro-messaging branch March 17, 2026 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants