Design SystemsCommand Design System MarkSix directional chevrons converging on a core

Design System Release 1.0

Command

Dark-first, dense, and technical. Built for developer and operations products.

Purpose-built instrument.

  • Solid graphite planes
  • Operational cyan signals
  • Dense persistent context
Command Design System MarkSix directional chevrons converging on a core
Installation command controls
npx agentkogei@latest addnpx agentkogei@latest add command

Command is retrieved anonymously from AgentKogei's public Design Systems collection. The CLI shows the absolute target and the exact change before it writes anything.

Design System Preview / Rendered evidence

One direction across the whole product.

Preview is evidence, not the Design Contract. It demonstrates direction and evaluated coverage; the Design Contract itself is public, so you can read every word before you add it.

01 / Principles

Principles and signature

Node 04

  1. 01Solid graphite planes
  2. 02Operational cyan signals
  3. 03Dense persistent context

02 / Semantic colors

Dark and light roles

Dark

  • Background
    #080b10The page canvas behind every surface.
  • Foreground
    #e8edf5Primary text and high emphasis symbols.
  • Card
    #0d1118The primary solid working plane for grouped content.
  • Muted
    #121823Nested regions, secondary controls, and quiet solid fills.
  • Muted Foreground
    #98a4b5Supporting copy that remains readable.
  • Border
    #283344One-pixel separators, control outlines, and structural rules.
  • Primary
    #55d6ffPrimary actions, focus, active selection, links, and live information.
  • Primary Foreground
    #051015Content placed on the primary color.
  • Destructive
    #ff6b7aIrreversible actions and critical errors.
  • Success
    #6ee7a8Confirmed completion and healthy status.
  • Warning
    #f6c85fCaution that needs attention without blocking work.
  • Info
    #55d6ffNeutral guidance and informational status.
  • Ring
    #55d6ffKeyboard focus indication around interactive controls.

Light

  • Background
    #f3f6faThe page canvas behind every surface.
  • Foreground
    #111827Primary text and high emphasis symbols.
  • Card
    #ffffffThe primary solid working plane for grouped content.
  • Muted
    #e9eef5Nested regions, secondary controls, and quiet solid fills.
  • Muted Foreground
    #526174Supporting copy that remains readable.
  • Border
    #aebdceOne-pixel separators, control outlines, and structural rules.
  • Primary
    #006f95Primary actions, focus, active selection, links, and live information.
  • Primary Foreground
    #ffffffContent placed on the primary color.
  • Destructive
    #b42335Irreversible actions and critical errors.
  • Success
    #18794eConfirmed completion and healthy status.
  • Warning
    #8a6100Caution that needs attention without blocking work.
  • Info
    #006f95Neutral guidance and informational status.
  • Ring
    #006f95Keyboard focus indication around interactive controls.

03 / Typography

Role based type scale

A distinct point of view.

Display

2.5rem to 4rem · 600 · 0.94 line height · -0.04em tracking

Singular marketing statements only.

Current workspace

Page-title

1.5rem to 2rem · 600 · 1.08 line height · -0.025em tracking

Section hierarchy and important grouped content.

Clear hierarchy makes complex product work easier to understand.

Body

0.875rem to 0.875rem · 400 · 1.5 line height · 0em tracking

Reading text, explanations, and form guidance.

OPERATIONAL CONTEXT

Eyebrow

0.625rem to 0.6875rem · 700 · 1.35 line height · 0.12em tracking

Compact sans-serif labels, metadata, and interface wayfinding.

RUN 042 · 98% HEALTHY

Telemetry

0.6875rem to 0.75rem · 400 · 1.35 line height · 0em tracking

Telemetry, counters, and technical evidence with tabular numerals.

Release activity

Section-title

1rem to 1.25rem · 600 · 1.2 line height · -0.01em tracking

Ruled panel and operational section headings.

Filter results

Compact-interface

0.75rem to 0.8125rem · 500 · 1.4 line height · 0em tracking

Dense controls, table content, and persistent operational context.

04 / Spacing

Spacing scale

  • 1

    0.25rem · Tight icon and inline relationships.

  • 2

    0.5rem · Default panel padding, compact control internals, and paired labels.

  • 3

    0.75rem · Maximum product panel padding and related component groups.

  • 4

    1rem · Default control and card rhythm.

  • 6

    1.5rem · Distinct groups within a section.

  • 8

    2rem · Generous product separation and compact marketing groups.

  • 12

    3rem · Marketing section spacing, never routine product panel spacing.

05 / Layout and responsive behavior

Constraints that preserve hierarchy

Keep operational context visible, align dense panels within a solid ruled frame, and use no decorative background texture.

Maximum 96rem · Reading width 72ch · Columns 1/8/16 · Gutters 0.75/1/1.25rem

  • Mobile

    320px and wider

    Use one content column and preserve source order.

  • Tablet

    768px and wider

    Introduce paired regions only when each remains independently readable.

  • Desktop

    1024px and wider

    Use precisely aligned ruled regions while keeping reading lines constrained.

  • Zoom

    200% zoom

    Allow controls and content to wrap without clipping or overlap.

  • Reflow

    320px reflow

    Retain every action and meaning in a single logical flow.

06 / Radius, borders, and elevation

Surface geometry and depth

Radius

  • Subtle · 0.125rem · Small indicators and restrained interactive detail.

  • Control · 0.125rem · Buttons, fields, and compact interactive surfaces.

  • Panel · 0rem · Square cards, panels, tables, navigation, and grouped regions.

Borders

  • Hairline · 1px · Quiet dividers and table structure.

  • Default · 1px · Controls and ordinary surface boundaries.

  • Strong · 2px · Selected, focused, or strongly separated regions.

Elevation

  • Flat · Default surfaces separated by spacing or borders.

  • Raised · Solid luminance steps and inset highlights, never cast card shadows.

  • Overlay · Dialogs, menus, and content above the working plane.

07 / Controls

Buttons and links

Keep actions compact, instrument like, and explicit about the operation they trigger. Use precise destination names, persistent underlines, and visible keyboard focus.
Button states
Default
Hover
Focus
Active
Disabled
Loading
Success
Error
Link states
DisabledOpen run log
Interactive actionsInspect configuration

Ready for local interaction.

08 / Fields

Forms and inputs

Align labels, fields, help, and validation as persistent operational context. Use compact controls, persistent labels, and reserved validation rows to prevent panel movement.
Check target

The alert address receives the local check summary.

09 / Containers

Cards and panels

Use cards for one operational object and keep state visible before action. Use solid graphite panels with one-pixel rules for durable context and align telemetry to predictable columns.
Current run
A dense operational card keeps status, telemetry, and the next action in one scan path.
RUN 042 · 98% healthy

Use cards for one operational object and keep state visible before action.

10 / Wayfinding

Navigation

Expose the current console section in text and aria current while preserving keyboard sequence.

11 / Data

Tables, lists, and data display

Align operational values into dense ruled columns with persistent row headings. Expose horizontal overflow on a labelled region while preserving every operational column.
Active checks
CheckRegionResult
API latencyMNLPassing
Queue depthSINWarning
Job errorsNRTFailed

Run context

  • Runtime

    Production edge checks.

    Active
  • Interval

    Checks execute on a fixed local specimen clock.

    5 min
  • Escalation

    Failures require an operator decision.

    Manual

12 / Feedback

Badges, alerts, and feedback states

Report the operation, result, and next action in one compact scan path. Pair semantic color with a written result, symbol, and ruled treatment.
  • IdleThe check is not currently running
  • RunningThe check is actively evaluating
  • PassingThe latest result met its threshold
  • FailedThe latest result crossed its failure threshold
Feedback states
Loading

Running operational checks…

Empty

No checks are configured for this target.

Filtered empty

No checks match the active result filter.

Error

Check results could not be read. Retry the local run.

Success

Every active check is passing.

Disabled

Acknowledge is unavailable until the run completes.

Destructive

Deleting this check removes it from the local run plan.

13 / Consequence

Dialogs and destructive actions

Keep the operation and current run identifier visible throughout the dialog. Repeat the exact check name and operational consequence before confirmation.

Inspect run summary

Review Run 042 telemetry before returning to the checks table.

  • Escape closes inspection because no operational change is pending.
  • Return focus to the run summary control.

Job errors check

The check will be removed from the local Run 042 plan.

This specimen can restore the check because it performs no external operation.

Job errors check remains available.

Inspect run summary

Review Run 042 telemetry before returning to the checks table.

Remove Job errors check?

The check will be removed from the local Run 042 plan.

This specimen can restore the check because it performs no external operation.

13

Motion and reduced motion

Timing supports state changes and never starts without a Builder action.
Motion specimen
Ready to move

The specimen is ready and does not autoplay.

Motion timings

feedback
80 ms
transition
120 ms
spatial
180 ms

Use fast operational transitions that confirm input without delaying the next action.

Reduced motion

Remove translation and scaling while preserving an immediate labelled state change.

14

Accessibility guidance

Complete accessibility direction for the Design System Preview.
  • Semantics

    Use native landmarks, headings, controls, tables, lists, and status regions before adding ARIA.

  • Keyboard

    Keep every action reachable and operable in a logical source and tab order.

  • Focus

    Show a persistent high contrast focus indicator and restore focus after modal interactions.

  • Contrast

    Meet text, icon, control boundary, and state contrast in both supported color schemes.

  • Target size

    Provide targets at least 24 by 24 CSS pixels with adequate spacing between adjacent actions.

  • Zoom

    Preserve content and operation at 200 percent page zoom without overlap or clipping.

  • Reflow

    Reflow to a 320 CSS pixel viewport without two dimensional page scrolling.

  • Forced colors

    Retain boundaries, focus, selection, and status meaning when system colors replace authored colors.

  • Status communication

    Announce asynchronous and local state changes in named status or alert regions without relying on color.

Preview

The Design System Preview is a public visual and descriptive specimen of evaluated direction.

Design Contract

The complete Design Contract is the public raw Markdown installed into a Project.

Evaluation evidence

Evaluation metadata and raw evidence paths remain public so coverage can be inspected.

Read the methodology

Release 1.0

Release details

Release evidence

Public metadata for release 1.0.
Compatibility
React >=18 <20 · Next.js >=15 <17 · Tailwind >=4 <5 · shadcn/ui
Evaluation
Design System Evaluation passed · WCAG 2.2 Level AA reference implementation
Evidence coverage
  • 1440x900 · 390x844
  • Light · Dark · Reduced motion
  • Human review passed · Rights review passed
  • 4 agent generation runs
  • structure · accessibility · responsive overflow · color contrast
  • evaluation/report.json

Coverage

Required surfaces and system states.
  • Marketing
  • Authentication
  • Onboarding
  • Dashboard
  • Table
  • Form
  • Settings
  • States

Inside the Design Contract

Installation writes one root DESIGN.md and nothing beside it.
  • Interface principles, layout, and product surfaces
  • Semantic tokens and their definitions
  • Components, interaction states, and feedback
  • Motion and accessibility direction
  • Agent instructions and worked examples
  • A final validation checklist
  • React or Next.js, Tailwind CSS v4, and shadcn/ui implementation direction
Learn how Design Contracts direct future agent work

Design Contract and changelog

The complete agent direction for Release 1.0.

Release 1.0

Changelog

Initial Design System Release with solid graphite planes, dense technical patterns, and complete state coverage.

Read Command 1.0 Design Contract
View raw Design Contract