Launch pricing — lifetime updates included. Buy now Preview in Figma

The Figma kit and design system for defense and critical-systems interfaces

Three operator-grade themes — day, NVG-safe night, monochrome — with threat coding, comms and COP components, and RTL built in. Designed against MIL-STD-1472. Nothing generic.

7-day money-back · lifetime updates · try the free kit first

NOMINALCOP link nominal — 14 tracks held.
HostileFriendlyUnknownCritical
TXCH 12SEC
GRID38S MC 1234 5678
Lifetime updates7-day money-backDesigned against MIL-STD-1472

Why it's different

Four things a generic kit can't give a tactical team

Most UI kits lead with volume. This one leads with the things only it has — each one you can see working, right here.

01

Three modes, one switch

Day, NVG-safe night, and monochrome are modes on the Semantic token collection — not duplicated component sets. Flip the switch and the entire surface re-themes at once, with no drift.

NOMINALCOP link nominal — 14 tracks held.
HostileFriendlyUnknownCritical
TXCH 12SEC
GRID38S MC 1234 5678

02

Never color alone

Every threat and status pairs color with a second cue — shape, glyph, count. Strip the color in Mono and the meaning survives. This is the single clearest proof the design is domain-correct.

Day — color + shape
HostileFriendlyNeutralUnknown
NominalCautionCritical
Mono — color stripped, meaning intact
HostileFriendlyNeutralUnknown
NominalCautionCritical

03

Tactical components, not dashboards

Push-to-talk and comms state, signal reticle, COP overlay panels, mission banner, APP-6 threat indicators. The parts you actually need for an operator surface — not charts and pricing tables.

IDLECH 12SEC
RXCH 12SEC
TXCH 12CLR

Sensor feed

Feed: ACTIVE
Track count: 14

04

RTL done right

Right-to-left from the token layer, via CSS logical properties. Coordinates and grids stay LTR-isolated inside an Arabic UI, so tactical digits never bidi-reorder into nonsense.

إحداثيات الهدف الحالية
الشبكة38S MC 1234 5678
خط العرض/الطول34.0522, -118.2437

Built right

Rigor you can audit, not adjectives

100% variable coverage

Every property reads a token. Zero hardcoded values — reject-on-sight in review.

APCA-validated contrast

Contrast checked on the APCA algorithm, not WCAG 2 ratios — NVG- and sunlight-readable.

Theme is a mode

Day / Night-NVG / Mono are modes on the Semantic collection. Re-theme everything in one click.

Clean to ship

Built on MIT primitives (shadcn/Radix/React Aria) + Blueprint structure. No commercial-kit files.

Accessibility floor

Focus-visible rings, ARIA wiring, correct aria-live politeness, reduced-motion respected.

Code ↔ Figma parity

Token and component names match 1:1, so design and dev never drift apart.

What's inside

Not 6,500 filler components — ~30 that are right where it counts

Every one is themed across all three modes, RTL-ready, accessible, and tested. The count is the point: depth over breadth. A reskinned dashboard kit is recognizable instantly to this buyer — these are built for the surface, not the storefront.

  • StatusIndicator
    APP-6 threat + status, shape-coded
  • MissionBanner
    mission-state header
  • PTTIndicator
    push-to-talk / comms state
  • SignalReticle
    link-strength reticle
  • OverlayPanel
    COP overlay, 8 anchors
  • CoordReadout
    LTR-isolated coordinates
  • Alert / AlertStack
    P-level badged alerts
  • Button
    27 variants, 3 intents
  • Input
    labelled, mono, error states
  • Select
    truncating, accessible
  • Dialog
    Radix-backed, focus-trapped
  • Table
    numeric-aligned, selectable rows

Premium IP

The standards-mapping spec — the reasoning, not just the pixels

A documented mapping of each design decision to the public standard it answers to. This is the thing no competitor ships, and the reason a critical-systems team can defend the choice internally.

MIL-STD-1472

Human-factors

Control sizing, target areas, legibility and labelling mapped to the human-engineering design criteria.

APP-6 / 2525

Threat coding

Affiliation framework (hostile/friendly/neutral/unknown) realized as shape + glyph, never color alone.

APCA

Contrast

Perceptual contrast validated for dark, NVG-safe and sunlight-readable conditions.

Included in the Code Kit + Standards Spec tier below.

Proof, not logos

New to market — so we show you the thing is real

No borrowed testimonials yet. Instead: open code you can read, a free kit you can duplicate, and a documented standards mapping. For this buyer, proof beats authority.

Open
Source on GitHub — read the code before you buy.
Free
Figma Community teaser kit — duplicate it, try it.
~30
Tactical components, every one themed + tested.
3
Modes from one token switch: Day · Night · Mono.

Pricing

One-time, with lifetime updates

Priced to the buyer and the capability, not to a race with generic kits. Start free, upgrade when you're convinced. 7-day money-back on paid tiers.

Free — Figma teaser
$0
on Figma Community

The funnel. Tokens + base components, one theme. See the quality before you buy.

  • Day-mode token set (CSS variables)
  • Base components: Button, Input, Select, Status
  • Figma variables, named to match code
  • No card required
Preview in Figma
Code Kit + Standards Spec
$249
one-time · lifetime updates

Everything in the Code Kit, plus the documented standards-mapping spec — the reasoning, not just the pixels.

  • Everything in the Code Kit
  • Standards-mapping spec: each decision mapped to MIL-STD-1472 / APP-6 / APCA
  • The premium IP no competitor ships
  • Priority support

Most defensible — the documented rationale.

Buy now

FAQ

Straight answers

Is this a one-time payment?

Yes. One purchase, lifetime updates — you keep every future release at no extra cost.

Can I use it on multiple projects or with a team?

The license covers unlimited projects by your team. It is a use-license, not a resale-license — you ship products built with it, you don't redistribute the kit itself. Full terms are in the license agreement.

Is it MIL-STD certified?

No. It is designed against MIL-STD-1472 human-factors guidelines. Certification is a formal program we do not claim — and any buyer who needs certification would know the difference. We give you the rationale and the mapping; the formal program is yours to run if you need it.

What framework does it use?

React + TypeScript on Radix and native primitives, plus a matching Figma library. The token layer is framework-agnostic CSS variables, so the design language travels even if your stack isn't React.

Does it support RTL / Arabic?

Yes — from the token layer up, via CSS logical properties. Coordinate and grid digits stay LTR-isolated inside an Arabic UI so tactical data never bidi-reorders.

What's your refund policy?

7-day money-back, no questions asked. If it isn't right for your team, email us within 7 days.

Why this exists

“I built this because the tools for tactical interfaces were either locked inside primes or reskinned SaaS kits that fall apart the moment color is the only signal. So I built the kit I wanted: correct under NVG, correct in Arabic, correct in mono — with the reasoning written down. If your team works on the screen that can't be wrong, this is for you.”

— Founder, Operator-Grade