brand
Inkeep Brand
Background knowledge for all visual creation. Consumer skills (/graphics, /motion-video, /gslides) load this for Inkeep-specific brand guidance.
Brand Principles
- Human + AI Collaboration — Technology feels cooperative and understandable. Visuals emphasize partnership, not replacement.
- Developer Clarity — Structure and readability before decoration. Clear hierarchy, logical organization, precise communication.
- Imperfect Precision — Hand-drawn visuals introduce warmth into technical environments. Slight irregularities create approachability.
- Practical Intelligence — Visuals explain systems and outcomes, not abstract concepts. Every graphic serves a functional purpose.
Logo Selection
Always lead with the Primary full-color logo (icon + wordmark) on light backgrounds. Use the white version on dark backgrounds. Monochrome is a last resort — only when backgrounds are too busy for color. Minimum clear space = 1x the icon height on all sides. Never distort, rotate, recolor, or add effects to the logo.
Typography
| Font | Use for | Rules |
|---|---|---|
| Neue Haas Grotesk Display Pro | H1, H2, card titles, testimonial quotes | 400 for headings, 300 for descriptions, 500 for interactive |
| JetBrains Mono | Tags, eyebrows, buttons, H3, H4 | Always 500, always uppercase for UI labels |
| Noto Serif | Body copy, descriptions, long-form | 300 for body, 400 for bios |
Never mix more than 2 typefaces in a single component.
Color Usage
- Page backgrounds — always warm cream (#FBF9F4). Never use pure white (#FFFFFF) as a page background.
- Card surfaces — use cream (#F7F4ED) for contrast against page background
- Feature cards — rotate through warm-peach, warm-gray, light-blue, light-purple for visual variety
- Accent colors (Golden Sun, Orange Light) — use sparingly, never for primary UI
- Blue icons on blue backgrounds — NEVER. Blue icons disappear on blue. Use white or dark variants instead.
Text Style Rules
- Titles in sentence case — only first letter capitalized
- "Agent" always capitalized — it's a brand term
- Tagline: "The Agent Platform for Customer Operations"
- URL format:
inkeep.com/path(no https://)
Logo & Watermark Timing (video/slides)
- Logo appears in the first 5 seconds
- Watermark present in content frames (small icon, reduced opacity, bottom-right)
- Watermark excluded from intro/outro scenes
- Outro logo is large and prominent
Size Minimums
- Headlines: 48px minimum (for readability across mediums)
- Body text: 24px minimum
Deep Reference
Load the reference files relevant to what you're building:
| If your content includes... | Load |
|---|---|
| Any layout or arrangement decisions (almost always) | references/composition-guide.md — Z-pattern, split layout, visual hierarchy, color restraint, edge bleed, content coverage, brand system consistency |
| Product mockups, code blocks, badges, metric callouts, logos, quotes, headers, buttons | references/element-patterns.md — reusable element recipes with exact brand styling |
| Illustrations, icons, diagrams, or gradient backgrounds | references/brand-guide.md — illustration style, icon rules, diagram rules, gradient tiers, decorative elements, what feels dated |
| Product screenshots and mockups | references/product-representation.md — fidelity spectrum (6 levels), decision framework, cleaning-up techniques, brand-product bridging |
| Charts, graphs, or data visualization | references/data-visualization.md — data series colors, labeling standards, chart type selection, data integrity rules |
| Animation or motion (video scenes, slide transitions) | references/motion-philosophy.md — principles, do's/don'ts, standard motion patterns |
| Marketing website copy (headlines, CTAs, landing pages) | references/copy-patterns.md — headline formulas, CTA conventions, value framing hierarchy, use case page patterns |
| Delegating to subagents or external APIs (Quiver, GPT Image, Gemini, etc.) | references/create-brand-packet.md — how to assemble brand context for downstream AI processes, series briefs for parallel outputs, verification after boundary crossings |
Token Values & Assets
All token values and brand assets live in this skill:
tokens/marketing.md— marketing brand tokens (colors, typography, spacing, radius, shadows) from Figmatokens/product.md— product tokens (semantic colors, component variants, canvas tokens) fromagents-manage-uitokens/figma.json— Figma component keys and node IDs (forimportComponentByKeyAsync)assets/— SVGO-optimized SVGs and PNGs organized by Figma section hierarchy (logos/,icon-set/,illustrations/,decorative-and-backgrounds/,fonts/)
Regeneration (when Figma or product code changes):
- Marketing tokens + assets:
bun scripts/process-manifest.ts <raw-manifest.json>(requires Figma export first viagenerate-manifest.js) - Product tokens:
bun scripts/generate-product-manifest.ts(fetches from GitHub, no local clone needed)
Product Resources
Inkeep's product repos, apps, and documentation — for when visual creation skills need to understand or reference the actual product.
| Resource | URL | What it contains |
|---|---|---|
| Product repo | github.com/inkeep/agents |
Agent platform, Slack integration, tool system, approval workflows. Also contains product documentation (docs/) — check docs first for feature understanding. |
| Widget library | github.com/inkeep/agents-ui |
Chat widget, message components, approval buttons, agent cards — the actual React components and their styling. Ground truth for what product UI looks like. |
| Running app | app.inkeep.com |
Production application. Use for screenshotting the actual product in its real state (requires auth). |
| Marketing site | inkeep.com |
Public website. Check for existing product illustrations, screenshots, and visual treatments. |
| Marketing repo | github.com/inkeep/marketing-site |
Next.js marketing site source. Existing graphics in public/images/, component patterns, blog MDX content. |
More from inkeep/team-skills
qa
Manual QA testing — verify features end-to-end as a user would, by all means necessary. Exhausts every local tool: browser (Playwright), Docker, ad-hoc scripts, REPL, dev servers. Mock-aware — mocked test coverage does not count. Proves real userOutcome at highest achievable fidelity. Blocked scenarios flow to /pr as pending human verification. Standalone or composable with /ship. Triggers: qa, qa test, manual test, test the feature, verify it works, exploratory testing, smoke test, end-to-end verification.
61write-agent
Design and write high-quality Claude Code agents and agent prompts. Use when creating or updating .claude/agents/*.md for (1) single-purpose subagents (reviewers, implementers, researchers) and (2) workflow orchestrators (multi-phase coordinators like pr-review, feature-development, bug-fix). Covers delegation triggers, tool/permission/model choices, Task-tool orchestration, phase handoffs, aggregation, iteration gates, and output contracts. Also use when deciding between subagents vs skills vs always-on repo guidance.
50write-skill
Create or revise Claude Code-compatible Agent Skills (SKILL.md with optional references/, scripts/, and assets/). Use when designing a new skill, improving an existing skill, or updating/refactoring an existing skill while preserving the original author's intent (avoid semantic drift unless explicitly requested/approved by the author). Also use when integrating skills with subagents (context fork, agent).
45pr
Write or update a GitHub PR body — self-contained, stateless, and structured for efficient review. Gathers context from the diff, spec, and implementation to produce a comprehensive PR description. Re-invoke after pushing commits to a branch with an open PR to keep the body current. Standalone or composable with /ship and /review-cloud. Triggers: PR body, PR description, pull request, write PR, update PR, create PR, PR template, refresh PR, stale PR body, pushed changes to branch with open PR.
33explore
|
31debug
|
29