بنقرة واحدة
brand-guidelines
Applies official Kortix colors, type, and layout from kortix.com to decks, docs, slides, and other artifacts. Use when matching brand visuals, formatting deliverables, or checking work against company design standards.
القائمة
Applies official Kortix colors, type, and layout from kortix.com to decks, docs, slides, and other artifacts. Use when matching brand visuals, formatting deliverables, or checking work against company design standards.
| name | brand-guidelines |
| description | Applies official Kortix colors, type, and layout from kortix.com to decks, docs, slides, and other artifacts. Use when matching brand visuals, formatting deliverables, or checking work against company design standards. |
This skill is the entry point for Kortix visual identity on kortix.com—colors, typography, accents, shadows, spacing, and motion for any branded output.
Keywords: Kortix, kortix.com, brand identity, visual identity, brand colors, typography, Roobert, styling, layout, corporate design, post-processing
All values are hex, converted from the source OKLCH tokens. Build on a neutral base and use a single accent per surface — never a rainbow.
Core neutrals (Light / Dark):
| Token | Light | Dark | Use |
|---|---|---|---|
| Background | #FFFFFF | #0A0A0A | Page background |
| Foreground | #0A0A0A | #FAFAFA | Primary text |
| Card / surface | #F3F3F3 | #171717 | Elevated surfaces |
| Muted surface | #F5F5F5 | #262626 | Secondary surfaces, fills |
| Muted text | #737373 | #A1A1A1 | Secondary / supporting text |
| Border | #E5E5E5 | #27272A | Hairlines, dividers, outlines |
| Input | #F2F2F2 | #262626 | Form field fills |
| Ring (focus) | #A1A1A1 | #737373 | Focus rings |
| Primary | #171717 | #E5E5E5 | High-emphasis fills / buttons |
Brand accents (pick ONE per surface):
#2B91F7 — primary semantic accent#CCA300#D18B19#8AD693#AB80D6#F14B4CChart ramp (data visualization only): #FFD230 → #FE9A00 → #E17100 → #BB4D00 → #973C00
Destructive: #E7000B (light) / #FF6467 (dark)
kortix.toml, sessions, CLI, paths, identifiers; fallback to system monoTracking & leading:
0em (normal) is the default for body and most UI. Apply tight tracking (-0.01 to -0.02em) only on hero / large display type. Never loosen body tracking.Do not invent marks, alternate wordmarks, or decorative lockups.
Rules:
#0A0A0A. Prefer the symbol alone unless the layout needs the full wordmark.#FAFAFA. Never place the white logomark on light backgrounds.currentColor to #0A0A0A or #FAFAFA; never substitute a different shape.0.23rem base (--spacing). Build gaps and padding as multiples of this unit for consistent rhythm.0.625rem (10px) base (--radius). Use md for cards and controls, lg (≈1rem) for large panels and covers.1px everywhere; rely on the border token, not heavier strokes.Shadows are subtle only — low opacity, small offsets, no glow or neon. Shadow color: #1A1F2E (light) / #000000 (dark).
| Level | Offset / blur | Opacity |
|---|---|---|
2xs/xs | 0px 1px 2px | 0.02 |
sm / — | 0px 1px 2px + 0px 1px 2px -1px | 0.04 |
md | 0px 1px 2px + 0px 2px 4px -1px | 0.04 |
lg | 0px 1px 2px + 0px 4px 6px -1px | 0.04 |
xl | 0px 1px 2px + 0px 8px 10px -1px | 0.04 |
2xl | 0px 1px 2px | 0.10 |
Animate with purpose — fade, slide, or product-reveal only.
100ms · normal 150ms · moderate 200ms · slow 300ms · slower 500mscubic-bezier(0.2, 0, 0, 1) · in cubic-bezier(0.4, 0, 1, 1) · out cubic-bezier(0, 0, 0.2, 1) · in-out cubic-bezier(0.4, 0, 0.2, 1)ease-default for most UI transitions.#FFFFFF, foreground #0A0A0A, border #E5E5E5#0A0A0A, foreground #FAFAFA, border #27272AFor positioning, terminology, audience pitches, and the full don't-say / prefer wording list, use
../internal-comms/SKILL.md— the verbal source of truth that complements these visual guidelines.
How to read, write, and curate project memory in `.kortix/memory/` — the project brain. Load this skill whenever you (or the memory-reflector agent) need to add, update, or reorganize what this project knows about itself. Defines the rubric for what belongs in memory, the file structure, and the change-request flow for landing memory edits on `main`.
Canonical reference for a Kortix project. Covers (1) the platform overview — repo-native projects, sessions backed by ephemeral branches, the strict boundary between Kortix config (`kortix.toml`) and OpenCode config (`.kortix/opencode/`) — (2) the in-depth `kortix.toml` manifest with every key, every trigger field, the secrets contract, the `[[apps]]` deployment surface, (3) the full `kortix` CLI reference (every command, every flag, the project-scoped token model, what works inside a session sandbox with the pre-injected `KORTIX_TOKEN`), (4) the Kortix change-request (CR) system — the mandatory path for landing any session-branch work on `main`, including the rule that an agent MUST open a CR if it wants its changes merged, (5) the session sandbox runtime environment — what runs inside a session, including the fact that the sandbox **does support Docker and Docker-in-Docker** (`dockerd`, building images, and running containers/services all work in-session, so agents should never assume a sandbox can't run Do
Canonical reference for a Kortix project. Covers (1) the platform overview — repo-native projects, sessions backed by ephemeral branches, the strict boundary between Kortix config (`kortix.toml`) and OpenCode config (`.kortix/opencode/`) — (2) the in-depth `kortix.toml` manifest with every key, every trigger field, the secrets contract, the `[[apps]]` deployment surface, (3) the full `kortix` CLI reference (every command, every flag, the project-scoped token model, what works inside a session sandbox with the pre-injected `KORTIX_TOKEN`), (4) the Kortix change-request (CR) system — the mandatory path for landing any session-branch work on `main`, including the rule that an agent MUST open a CR if it wants its changes merged, and (5) the OpenCode runtime reference mirroring opencode.ai/docs/ for agents, skills, commands, tools (built-in + custom), plugins, MCP servers, permissions, rules (AGENTS.md), and models. Load when the user asks how Kortix works, asks about anything in `kortix.toml` or the `kortix` CLI,
How to answer in Slack as a teammate. Covers the live plan-block stream (`slack step` with --detail/--output, `slack send` to finalize the answer), file uploads, posting to other channels/threads, reactions, search, message editing/deletion, and the tone the bot should use. Load this when the turn is triggered from Slack (the prompt mentions a Slack workspace/channel/thread, or when `$SLACK_BOT_TOKEN` is set in the env), or when the user asks how to do anything in Slack.
Kortix brand + design system: the rules, tokens, and component library for building any Kortix frontend UI (apps/web). Load this WHENEVER you create or edit a page, screen, component, list, card, badge, avatar, modal, form, empty state, or any visual surface in apps/web — and whenever deciding whether to reuse an existing component or add a new one. Enforces: always import from the design system, never hand-roll chrome, people-are-round / things-are-square avatars, and one standardized brand identity. Source of truth is globals.css + the live /design-system page + src/components/ui.
Use when writing or reviewing any Kortix-facing words — headlines, taglines, elevator pitches, audience pitches (developers, companies, enterprise), captions, deck or social copy, product naming, or text composited into images — or when another skill needs Kortix's canonical positioning, terminology, or approved wording. Verbal source of truth; pair with brand-guidelines for visuals.