Social media.
Rules for every Evalgist account: channels, templates, voice, and review. Visual rules from PATTERNS.md apply here too.
One playbook for every account.
The marketing owner maintains this guide. A designer builds templates. A reviewer signs off before anything scheduled goes live. These rules apply to company accounts and to any teammate posting as Evalgist.
Social is distribution, not a separate product surface. When copy or visuals disagree with Shortlist production, Shortlist wins.
Match the channel to the job.
Each platform has a primary use. Do not cross-post the same asset without retargeting size and copy.
X
Short product updates, release notes, links to guides, and timely replies. One idea per post.
Hiring workflow stories, evidence-first positioning, and longer context for committees and HR leaders.
YouTube
Walkthroughs and explainers with captions. Thumbnail carries the promise; the video shows real screens.
Vertical video
Short clips (Shorts and similar). Lead with the workflow problem, then show production Shortlist UI.
Link previews / Open Graph
Any link to evalgist.ai or the docs. Generated cards must match /brand/og-image.png and the runtime /api/og route.
Branding follows the content.
Full brand treatment is for announcements. Walkthroughs stay honest. Casual engagement stays light.
How much branding
full · screen · lightProduct announcement
Wrong: a meme template with tiny product mention.
Right: full template: mark, headline, OG grid or evidence artifact, brand accent off data panels.
Product walkthrough
Wrong: a staged UI mock with features Shortlist does not ship.
Right: a screen capture from production Shortlist, minimal caption bar, no fake quote highlights in the resume view.
Casual engagement
Wrong: a locked brand frame for a one-line reply.
Right: plain text or a light mark watermark; skip the full template.
Tokens, real screens, no invented UI.
Social assets use the same tokens as the design system. Brand accent stays on chrome, not on candidate data.
- Use design tokens and Geist (see @evalgist/design-system and @evalgist/og-kit hex mirrors).
- Screenshots come from production Shortlist only.
- Do not invent features (no quote highlight bands in the resume view unless the product ships them).
- Follow the Visual rules table in PATTERNS.md (selected row, EvidenceQuote, verdict tokens).
- Never use a rounded card with a colored left border on social crops (that pattern is for selected list rows only).
Official sizes
checked 2026-10-25Safe zones
per format- OG 1200 × 630: Keep copy and mark in the left ~62%. Right side stays open for the grid and evidence artifact.
- X 1600 × 900: 48 px outer margin. Title and mark in the lower third.
- X 1200 × 628: 48 px margin. One headline and mark; keep evidence UI readable at link-preview scale.
- LinkedIn 1200 × 627: 48 px margin. Avoid critical copy in the bottom 12% (mobile chrome).
- Portrait feed 1080 × 1350: 96 px margin. Stack mark, headline, then product screenshot centered.
- YouTube 1280 × 720: 80 px margin. One short headline (3–5 words); faces and UI left of center.
- Vertical 1080 × 1920: 96 px top and bottom safe area; stack mark, headline, then product screenshot centered.
Generate assets the same way as OG cards.
Open Graph images use @evalgist/og-kit. Channel sizes use @evalgist/social-kit on the same Geist fonts and token hex. Export PNGs with the package CLI or preview every template at exact pixel size on the docs site.
Template preview (exact pixel sizes)
Where images are implemented
production pathspackages/social-kit (channel templates, render CLI)
packages/og-kit/src/handler.tsx (createOgHandler, OG_IMAGE_SIZE)
packages/og-kit/src/og-illustration.tsx (layout and token hex)
apps/www/app/api/og/route.tsx + apps/www/lib/social-metadata.ts
apps/docs/app/api/og/route.tsx
Static fallback: apps/www/public/og-image.png and apps/docs/public/brand/og-image.png
Template inputs
all formats- title (required, plain language)
- subtitle or description (optional, one line)
- eyebrow / product name (Evalgist Shortlist on first mention)
- product screenshot (production Shortlist only)
- band label (Strong / Review / Low, never a percentage)
- format key (x-landscape | x-link | linkedin | portrait)
Example
docs snippet onlyimport { ImageResponse } from "next/og";
import { OG_IMAGE_SIZE, createOgHandler } from "@evalgist/og-kit";
// Production routes today:
// apps/www/app/api/og/route.tsx
// apps/docs/app/api/og/route.tsx
export const GET = createOgHandler({
eyebrow: "Evalgist Shortlist",
title: "AI resume screening, with evidence attached.",
description: "Quoted evidence for every criterion.",
});
// Custom social sizes: reuse the same fonts and token hex from OgIllustration.
// X: 1600 × 900 (16:9 template) or 1200 × 628 (1.91:1 link-style); see /social#visual-rules.
export function renderLandscapeSocial(title: string) {
return new ImageResponse(
(
<div
style={{
width: "100%",
height: "100%",
display: "flex",
flexDirection: "column",
justifyContent: "flex-end",
padding: 48,
background: "#f8fafc",
color: "#0f172a",
fontFamily: "Geist",
}}
>
<div style={{ fontSize: 20, color: "#64748b" }}>Evalgist Shortlist</div>
<div style={{ fontSize: 44, fontWeight: 600, letterSpacing: "-0.02em" }}>{title}</div>
</div>
),
{ width: 1600, height: 900 },
);
}
// OG cards stay on OG_IMAGE_SIZE: { width: 1200, height: 630 }OG preview
live /api/ogSame voice, shorter sentences.
Social copy follows packages/content-style (rendered on /brand/voice). It is not a separate tone: tighten cadence, one message per post, and keep evidence language.
Length
Wrong: a thread that restates the whole landing page.
Right: one claim, one proof point, optional link.
Match language
Wrong: posting an 87% match score.
Right: naming a band (Suggested match in product UI; spell out Strong / Review / Low in prose).
Language
Wrong: mixing languages in one post.
Right: English only for Evalgist accounts.
Length, links, and hashtags.
Stay inside platform limits. Prefer clarity over trend chasing.
- X: keep copy short; long-form posts are rare. Put the link in the post or rely on the card, not both with duplicate CTAs.
- LinkedIn: intro text can run longer, but the first two lines must stand alone in the feed.
- YouTube: title and description follow content-style; put primary links in the description.
- Hashtags: at most two CamelCase tags per post (example: #HiringOps).
- Links: use UTMs on evalgist.ai/shortlist, for example
https://evalgist.ai/shortlist?utm_source=linkedin&utm_medium=social&utm_campaign=pilot_evidence - Emoji: avoid emoji spam; none in product-voice surfaces.
- Engagement bait: never ask for likes, reposts, or reshares.
One approved and one rejected crop per format.
Tiles use design-system tokens. Rejected crops break the visual rules on purpose.
X 16:9
Approved direction
X 16:9
Rejected direction
LinkedIn landscape
Approved direction
LinkedIn landscape
Rejected direction
YouTube thumbnail
Approved direction
YouTube thumbnail
Rejected direction
Vertical 9:16
Approved direction
Vertical 9:16
Rejected direction
OG / link preview
Approved direction
OG / link preview
Rejected direction
Review, accessibility, and change control.
No credential or account-security content in this guide. Operational security stays in internal runbooks.
Accessibility
every postAlt text on every image. Captions or a transcript on every video.
Scheduling
breaking newsPause scheduled posts during major breaking news. The marketing owner calls the pause; a reviewer confirms before posts resume.
Sign-off
before publishA reviewer role approves copy, visuals, and links before anything goes live or is scheduled.
Review checklist
any author- Screenshot is from production Shortlist (not a design comp).
- Copy matches packages/content-style and uses bands, not scores.
- Template size matches the channel table; safe zones respected.
- At most two CamelCase hashtags; UTMs present on evalgist.ai/shortlist links.
- Alt text written; video has captions or transcript.
- No engagement bait; English only; no emojis in product-voice posts.
- Reviewer sign-off recorded (ticket or doc link).
History
shared changelogSocial publishing changes are recorded in the design system changelog under Social (source: packages/design-system/CHANGELOG.md).