HomeStylesTemplates
StyleKit
StylesTemplates
  1. Home
  2. /Styles
  3. /Developer Terminal
Style Catalog/Developer Terminal

Developer Terminal

终端风

D
49/100Poor

Turn a website into a terminal session: phosphor-green mono text, prompt prefixes, paired command-and-output blocks, and a tmux status bar. Tool authenticity as developer identity.

terminalCLIcommand linedeveloperhackermonospaceshelltmuxpromptconsole
View Full Showcase →Templates

Best For

terminal / CLI / command line

Primary Move

Use font-mono everywhere, no exceptions

Watch Out

Never use sans-serif or serif fonts (font-sans, font-serif)

Showcase Entry

Live preview of the showcase page. Click to explore the full experience.

View Full Showcase →

Color Palette

Primary

#4AF626

Secondary

#0A0E12

Accent 1

#8BE9FD

Accent 2

#FF79C6

Accent 3

#FFB86C

Accent 4

#6272A4

AI ImplementationComponent PreviewReadinessExportsRatings & Feedback

AI Implementation

Copy the Hard Prompt first, then use the spec when needed

Use the Hard Prompt by default to generate UI. Use the Design Spec to understand, modify, and review the style. Use the Creative Brief for early exploration.

Hard Prompt

Use this by default: copy it, append the concrete requirement, and let AI generate consistent production UI.

When to use

  • -When AI should generate UI directly
  • -When repeated outputs must stay consistent
  • -When style drift is the main risk

How to use

  • -Copy the full prompt
  • -Append the concrete requirement
  • -Review against forbidden rules and UI states
STYLEKIT_STYLE_REFERENCE
style_name: Developer Terminal
style_slug: developer-terminal
style_source: /styles/developer-terminal

# Hard Prompt

## When To Use
Use this when you want AI to generate code with strict style consistency. It is the safest default for production UI.

## How To Use
- Copy the full prompt into ChatGPT, Claude, Cursor, or another coding assistant.
- Append the concrete product/page requirement after the prompt.
- After generation, check the forbidden rules and interaction states before accepting the output.

Strictly follow the style rules below and maintain consistency. No style drift allowed.

## Requirements

- Prioritize style consistency first, then creative extension.
- When conflicts arise, treat prohibitions as the highest priority.
- Self-check before output: verify colors, typography, spacing, and interactions still match this style.

## Style Rules

You are a Developer Terminal design expert. All generated code must strictly follow these constraints:

## Absolutely Forbidden
- Any sans-serif / serif font (font-sans, font-serif)
- White or light backgrounds (bg-white, bg-gray-50, etc.)
- rounded-lg or larger radii (only rounded-sm and rounded-none allowed)
- Gradients bg-gradient-* and glassmorphism backdrop-blur
- Photography or illustration (a terminal only has glyphs)
- A 5th accent color (only #8BE9FD / #FF79C6 / #FFB86C / #6272A4 allowed)
- Heavy shadows shadow-md and above

## Must Follow
- font-mono globally
- Background #0A0E12, panels #0D141B, borders border-[#1F2937]
- Primary text phosphor green #4AF626; comments start with # in #6272A4
- Section headings start with a prompt prefix: visitor@stylekit:~$ command
- Headings or inputs carry a blinking cursor block (w-2 h-4 bg-[#4AF626] animate-pulse)
- Organize content as command + output pairs; lists as ls -la aligned output
- Status via exit code badges: [0] OK (green) / [1] ERR (magenta #FF79C6)
- End pages with a tmux style status bar
- Separate sections with ASCII rules (------)

## Color Semantics
- #4AF626 green: primary output, success, prompt commands
- #8BE9FD cyan: paths, links, usernames, info
- #FF79C6 magenta: keywords, errors, destructive actions
- #FFB86C amber: strings, numbers, warnings
- #6272A4 blue-gray: comments, secondary info, inactive items

## Motion & Interaction
- Cursor blink via steps() or animate-pulse, roughly 1s period
- Hover only shifts background alpha (hover:bg-[#4AF626]/10) or border brightness; no translate or scale
- Optional faint scanline texture (repeating-linear-gradient, alpha under 0.03)
- Use transition-colors duration-150

## Responsive
- Mobile: still a single-column terminal window, text-xs/text-sm, tables scroll horizontally
- Desktop: terminal window centered around max-w-5xl, keep an 80-column feel

## Self-Check
1. No non-mono font anywhere on the page
2. No gradients, glassmorphism, heavy shadows, or images
3. Every section reads as the output of a command
4. Color carries semantics only, never decoration
5. A tmux status bar exists at the bottom and at least one cursor blinks

## Absolute Bans (Match and Refuse)

If any of the following patterns appear, it is a style violation — rewrite without exception.

- use sans-serif or serif fonts (font-sans, font-serif)
- use white or light backgrounds (bg-white, bg-gray-50)
- use rounded-lg or larger radii (terminal chrome stays within rounded-sm)
- use gradients (bg-gradient-*) or glassmorphism (backdrop-blur)
- use photography or illustration (a terminal only has glyphs)
- exceed 4 terminal accent colors (cyan/magenta/amber/blue-gray only)
- use heavy shadows shadow-md or above (terminals are flat)

## Self-Check (Verify Before Shipping)

If any item fails, the style has drifted — fix before shipping.

- [ ] No purple-to-blue gradients
- [ ] No overused fonts (Inter, Roboto, Geist, Fraunces, Plus Jakarta Sans)
- [ ] No nested cards (cards inside cards)
- [ ] No gray text on colored backgrounds
- [ ] Body text contrast meets WCAG AA (>= 4.5:1)
- [ ] No bounce or elastic easing curves
- [ ] Animations have a prefers-reduced-motion fallback
- [ ] Body text line length capped at 65-75 characters
- [ ] No side-stripe accent borders (border-left/right > 1px)
- [ ] No gradient text (background-clip: text)
- [ ] No glassmorphism used as the default surface treatment
- [ ] No tiny uppercase tracked eyebrow labels above every section heading
- [ ] never use sans-serif or serif fonts (font-sans, font-serif)
- [ ] never use white or light backgrounds (bg-white, bg-gray-50)
- [ ] never use rounded-lg or larger radii (terminal chrome stays within rounded-sm)
- [ ] never use gradients (bg-gradient-*) or glassmorphism (backdrop-blur)
- [ ] never use photography or illustration (a terminal only has glyphs)

Use it in your workflow

Ship Developer Terminal in your AI coding tool

All integrations →
shadcn

Drop this style's theme into an existing shadcn project with one command.

bash
npx shadcn add https://www.stylekit.top/r/developer-terminal.json
CLI

Grab this style's theme without leaving your terminal.

bash
npx stylekit-cli add developer-terminal
MCP

Let Claude, Cursor & Windsurf apply “Developer Terminal” while you code.

bash
npx stylekit-mcp
Part ofDark Mode Design Styles

Component Templates

Component Preview

命令按钮

按钮即命令:主操作是反色的可执行命令,次操作是普通命令行

Frontend Readiness

Dark Mode, States, Motion, and Accessibility

This layer tracks whether the style is ready for real websites: theme modes, state feedback, keyboard access, and performance constraints.

Overall

51%

Fallback

Dark Mode

0%

Missing

UI States

79%

Partial

Motion

70%

Partial

A11y

70%

Partial

Performance

35%

Fallback

Key State Coverage

light
HoverFocus VisibleDisabledLoadingEmptyErrorSuccess

Button

Default / Hover / Focus Visible / Active / Disabled

Input

Default / Hover / Focus Visible / Disabled / Error

Card

Default / Hover / Focus Visible / Loading / Skeleton

Form

Default / Focus Visible / Disabled / Loading / Error

Implementation Notes

  • No curated dark-mode contract exists yet.
  • Check contrast in both light and dark modes.
  • Check heavy shadows, blur, large media, and scroll-linked effects manually.
  • No style-specific performance cost profile has been curated yet.
Global Styles

Global CSS

css
@keyframes developer-terminal-blink {
  0%, 49% { opacity: 1; }
  50%, 100% { opacity: 0; }
}

.developer-terminal-cursor {
  display: inline-block;
  width: 0.55em;
  height: 1.1em;
  background: #4af626;
  vertical-align: text-bottom;
  animation: developer-terminal-blink 1.06s steps(1, end) infinite;
}

.developer-terminal-prompt::before {
  content: "visitor@stylekit:~$ ";
  color: #8be9fd;
}

.developer-terminal-glow {
  text-shadow: 0 0 8px rgba(74, 246, 38, 0.35);
}

/* Optional faint CRT scanline texture. Apply to a positioned container. */
.developer-terminal-scanlines::after {
  content: "";
  position: absolute;
  inset: 0;
  pointer-events: none;
  background: repeating-linear-gradient(
    to bottom,
    rgba(139, 233, 253, 0.025) 0px,
    rgba(139, 233, 253, 0.025) 1px,
    transparent 1px,
    transparent 3px
  );
}

.developer-terminal-selection ::selection {
  background: rgba(74, 246, 38, 0.3);
  color: #4af626;
}

IDE Integration

IDE Configuration Export

Download configuration files for AI coding assistants to generate code in this style.

Style Pack

Export Style Pack

Get complete machine-readable style assets including design tokens, Tailwind presets, CSS variables, and shadcn/ui themes.

Metadata

Style metadata including version information

Design Tokens

Compatible with Figma / Style Dictionary / Tokens Studio

Tailwind Preset

Tailwind CSS theme preset, import directly in config

Global CSS

CSS variables and base styles

shadcn Theme

shadcn/ui theme configuration

CSS Variables

Pure CSS variables, works with any project

SKILL.md

Loadable skill pack for Cursor / Claude Code / VS Code

Design Philosophy

Developer Terminal does not imitate how a terminal looks; it borrows how a terminal speaks. For developers, the terminal is home -- the most honest, efficient, decoration-free tool they own. Building a personal site as a terminal session is a statement: my identity needs no marketing page, the tool itself is my business card.

Accessibility

Accessibility Score

WCAG 2.1 compliance analysis based on color contrast and typography readability.

49

Overall Score

Grade: D - Poor

Contrast Ratios

Score: 43/100Average Ratio: 5.78:1
AA FailAAA Fail
ContextColorsRatioAAAAA
Text on background
/#4AF626 / #0A0E12
13.37:1
Secondary text on background
/#8BE9FD / #0A0E12
13.99:1
Muted text on background
/#6272A4 / #0A0E12
4.11:1
Text on secondary background
/#4AF626 / #0D141B
12.8:1
Secondary text on secondary
/#8BE9FD / #0D141B
13.39:1
Button primary
/#0A0E12 / #4AF626
13.37:1
Text on accent 1
/#4AF626 / #4AF626
1:1
Alt text on accent 1
/#8BE9FD / #4AF626
1.05:1
Text on accent 2
/#4AF626 / #8BE9FD
1.05:1
Alt text on accent 2
/#8BE9FD / #8BE9FD
1:1
Text on accent 3
/#4AF626 / #FF79C6
1.65:1
Alt text on accent 3
/#8BE9FD / #FF79C6
1.72:1
Text on accent 4
/#4AF626 / #FFB86C
1.18:1
Alt text on accent 4
/#8BE9FD / #FFB86C
1.23:1

Readability

Score

63/100

Font Size

text-sm

Font Weight

font-mono font-bold tracking-tight

Line Height

default

Scoring is based on WCAG 2.1 standards. AA requires 4.5:1 contrast for normal text, 3:1 for large text; AAA requires 7:1 for normal text, 4.5:1 for large text.

StyleKit

A curated web design style library to help AI generate better-looking websites.

Navigation

StylesColorsCollectionsTemplatesGuideBlogChangelog

Resources

UI Design PromptsLanding Page PromptsDashboard PromptsTailwind UI PromptsDark Mode UI PromptsGitHub Repository

Stay Updated

By subscribing, you agree to our Privacy Policy and Terms.


Feedback

Have an idea, a suggestion, or found a bug? Tell me — it lands straight in my inbox.

Send feedback

Support Maintenance

If StyleKit helps your workflow, voluntary support helps cover servers, domains, and ongoing upkeep.

Scan to support / View all options

(c) 2026 StyleKit. Open source project.

AboutContactPrivacyTermsBuilt with the Editorial style
StyleKit frontend style librarystylekit.top陕ICP备2025065501号-3