See @AGENTS.md for guidelines on working with this codebase.
Backend engineers, application developers, and platform teams evaluating or adopting OGX for production AI workloads. They arrive from GitHub, blog posts, or search. They already use OpenAI/Anthropic SDKs and want to know: can I point my existing code at this server and have it just work? They are practical, time-constrained, and skeptical of marketing fluff. They read docs in dark terminals, IDEs, and browser tabs at all hours.
Powerful, flexible, production-grade. Not flashy. Not cute. Not corporate. The kind of project where the README is better than most companies' entire docs site. Speaks in code examples, not marketing copy. Respects the developer's time above all else.
Three words: capable, direct, trustworthy.
- Tone: Technical confidence without pretension. Think: well-organized CLI output, a clean terminal, a tool that does exactly what it says.
- Theme: Dark mode default, both supported. Dark should feel like a refined terminal environment, not "glowing neon AI dashboard." Light should feel like clean paper, not washed-out gray.
- Anti-references: Purple-to-blue gradients, animated gradient text, icon-in-colored-circle card grids, "Works with 20+ providers!" vanity stats, marquee scrolling logos, decorative mesh backgrounds. All of these are present on the current site and should be replaced.
- Color: Move away from purple as primary. The logo uses a deep navy-to-teal gradient. The palette should feel grounded, not synthetic. Consider warm neutrals or muted earth tones as an alternative to the current purple/teal AI palette.
- Typography: Current fonts (Space Grotesk, Inter) are on the overused list. Find something with more character that still reads as technical and trustworthy.
- Show, don't decorate. Every visual element must communicate information. No decorative gradients, glows, or animations that exist for "wow factor."
- Code is the hero. The most important thing on the landing page is a working code example. Make it prominent, readable, and real.
- Earn trust through clarity. Clean structure, consistent spacing, and direct language signal competence better than any visual flourish.
- Respect the scroll. Every section must justify its existence. If it doesn't answer a question the developer has, cut it.
- No AI slop. If a pattern appears on 50 AI-generated landing pages, it doesn't belong here. When in doubt, do less.