# Product ## Register brand ## Users Working software engineers who already live in the terminal — backend, infra, ML, and Python-heavy generalists. They're evaluating an open-source CLI coding agent against Claude Code, Cursor, and Aider. They land on this page from PyPI, GitHub, Hacker News, or a colleague's link, usually mid-task and skeptical. They want to know in 10 seconds what Pythinker Code is, in 60 seconds whether it fits their stack, and in 3 minutes how to install it and what it'll cost them. Context: desktop-first (terminal users on laptops/external monitors). Mobile traffic is real but secondary; a single-column shell is enough. ## Product Purpose Pythinker Code is an open-source, terminal-native AI engineering agent. It reads repos, edits files, runs commands, browses the web, and integrates with ACP-aware editors and MCP tools — all from the shell. This page exists to convert technically-credible visitors into installs. Success = `pip install pythinker-code` runs, GitHub stars climb, and the right kind of contributor finds the repo. Failure = the page reads as another AI-SaaS marketing skin and the visitor closes the tab. The page is also a soft bridge to Pythinker AI (the sister product) — discoverable, never pushy. ## Brand Personality **Sharp. Technical. Confident.** Tool-for-experts altitude, in the family of Linear, Vercel, and Stripe docs. - Voice: declarative, specific, no hedging. Mentions exact integrations (ACP, MCP), exact runtimes (Python 3.12+), exact verbs (reads, edits, runs). - Tone: quiet authority. No exclamation marks, no "powered by AI", no growth-marketing copy. - Personality cue: the friendly robot mascot is the one warm note. Everything around it is precise. The contrast is the point. ## Anti-references This page must not look or read like: - **Generic AI-SaaS landings.** No "powered by AI" badges, glowing CTAs, hero gradient meshes, generic 3D blob illustrations, or "10x your productivity" copy. The current cream-and-peach base stays; the bloat goes. - **Claude Code / Cursor / Copilot landings.** No dark-purple gradient hero, no IDE chrome screenshots framed in glass, no "introducing the future of coding" framing. We are open-source and terminal-native — that should be visible without saying it. - **Heavy 3D / glassmorphism.** Backdrop-filter is fine for the floating nav and one or two surfaces; glass everywhere is not. - **Robot-mascot kitsch.** The mascot is brand identity, not a sticker pack. It appears prominently in the hero and as the favicon/nav mark, then steps back. No "Hi, I'm Py!" speech bubbles, no animated jumps in every section. ## Design Principles 1. **Show the terminal, not the marketing.** The hero's centerpiece is the agent at work — real-feeling commands, real labels (`plan`, `edit`, `verify`), real output. Code over claims. 2. **Practice what we preach.** A tool for engineers must feel like one. Dense, scannable, no fluff sections. Every section earns its scroll. 3. **One warm note, then precision.** The peach + mascot supply warmth; everything else (typography, grids, spacing, code surfaces) is taut. Warmth is a single accent, not the whole composition. 4. **Open source visible.** GitHub, PyPI, license, version, downloads, and source links are first-class — not relegated to a footer afterthought. 5. **Mascot as identity, not entertainment.** The robot is a wordmark companion, not a guide character. It animates subtly (idle bob), it doesn't perform. ## Accessibility & Inclusion - Target WCAG 2.2 AA. Body text on cream meets contrast at the existing `--ink` (#17324C) — keep it. - All CTAs and nav targets ≥ 44×44px touch area on mobile. - Respect `prefers-reduced-motion`: disable mascot bob, scroll-reveal, and any background drift. - Code surfaces (`#10263c` / `#17324c`) carry monospace text in `--cream` or `--peach`; verify ≥ 4.5:1 for any inline syntax color. - Nav must be keyboard-navigable with visible `:focus-visible` (already wired via `--focus` token). - No color-only signaling; every "success/warning" cue pairs color with a glyph or label.