← ClaudeAtlas

hawkeye-designlisted

Design, build, or restyle any Hawkeye surface: the control plane dashboard, the review comment posted on GitHub, the CLI output, docs and any landing page. Use whenever a change touches what a user sees or reads. Carries the product's voice, visual system, tokens, primitives and the list of things Hawkeye never does.
ShobhitPatra/hawkeye · ★ 0 · Code & Development · score 64
Install: claude install-skill ShobhitPatra/hawkeye
# Design Hawkeye Hawkeye is a personal code reviewer. It reads a pull request on the author's own machine, on the author's own plan, and posts a judgment as `hawkeye[bot]`. The dashboard is an instrument panel the user owns, not a service they rent. The review comment is where most people first meet Hawkeye, and it delivers an opinion about someone's work. Every surface should carry that: sharp, quiet, trustworthy, unhurried, yours. Never chatty, never gamified, never corporate SaaS. Confidence comes from precision and restraint, not from decoration, praise or exclamation. ## Priority order When rules conflict, protect them in this order: 1. The facts of the review: verdict, severities, claims, paths, lines, counts. Never soften, reorder for effect, or hide a finding. 2. The repo's conventions and the shipped contracts (`core` exports, runner to control plane HTTP, the review comment shape already on people's pull requests). 3. The reader's job on this surface: decide whether to act, and on what, in one read. 4. The visual system below, applied exactly. 5. Polish. ## Surfaces Four faces, one voice. The visual tokens apply to the dashboard and any landing page. Voice and structure apply everywhere. - **Dashboard** (`apps/web`): pull request list, pull request detail, runners, connect, settings. Dense lists, editorial detail pages. - **Review comment** on GitHub: markdown only. Structure and words carry the design. - **CLI** (`hawkeye-review`): plain text, minimal color