dark-tech
Skill1 starsChanged 3 months agoMITView on GitHub
Genre pack: dark, precise, developer-adjacent minimalism — the Linear/Vercel/Stripe-dark school. Near-black surfaces, one restrained accent, fine hairline borders, compact type, subtle glow only on the accent, dashboard-ready density. Use for developer tools, infra products, AI platforms, and technical audiences. Stack on the design-taste core skill.
In this repository23 other files it gives its agents.
- brutalist-industrialSkill
- cinematic-motionSkill
- corporate-trustSkill
- design-tasteSkill
- editorial-minimalSkill
- japanese-minimalSkill
- neo-brutalismSkill
- playful-colorSkill
- quiet-luxurySkill
- retro-printSkill
- taste-accessibilitySkill
- taste-brand-identitySkill
- taste-code-craftSkill
- taste-code-reviewSkill
- taste-colorSkill
- taste-design-reviewSkill
- taste-design-systemSkill
- taste-gsapSkill
- taste-landing-pageSkill
- taste-motionSkill
- taste-typographySkill
- taste-ux-copySkill
- taste-web-performanceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
No gradients (flat surfaces only), no colored full-bleed backgrounds.
- Very specific: line 37
Fine border discipline: every panel, row, and table cell is separated by 1px rgba(255,255,255,0.08) borders.
- Very specific: line 45
No emoji as icons. Draw icons: 1.5px stroke, rounded caps, 16–20px grid, #9CA3AD at rest, accent at active.
- Distinctive: line 46
No photography by default.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dark-tech
One identity: a machine you can trust — precise, quiet, fast.
1. PALETTE (Fixed)
- Ground:
#08090A(near-black). Panels:#0E0F11and#131417. Hover surfaces:#181A1D. - Ink text:
#F7F7F8(primary),#9CA3AD(secondary),#5C6370(tertiary/muted). - Borders:
rgba(255, 255, 255, 0.08)hairlines. Stronger on interactive:rgba(255, 255, 255, 0.16). - Accent — exactly one: indigo
#5E6AD2, violet#7C7CF0, or emerald-safe#34D399— selected by brand/meaning. Accent used for: links, the single primary button, active states, one data series. - No gradients (flat surfaces only), no colored full-bleed backgrounds. Glow allowed ONLY on the accent:
box-shadow: 0 0 0 1px rgba(accent, .35), 0 0 24px rgba(accent, .25)on the primary button.
2. TYPOGRAPHY (Fixed)
- Display: neutral grotesk with personality — Space Grotesk, or system sans at 500–600 weight. Sizes
clamp(2.2rem, 5vw, 4rem), tracking −0.03em, leading 1.05. Dark tech is restrained: powerful but not shouting. - Body: 14–15px,
#9CA3ADsecondary for almost everything; pure#F7F7F8reserved for headings, key values, and interactive labels. Line-height 1.55. - Labels/metadata: monospaced (
IBM Plex Mono/ui-monospace), 11–12px,#5C6370, no letterspacing theatrics (0–0.02em). Version numbers, keys, statuses live here. - UI density: 12–14px is normal. This is an instrument console, not a billboard.
3. COMPOSITION (Fixed)
- Fine border discipline: every panel, row, and table cell is separated by 1px
rgba(255,255,255,0.08)borders. Inner fills are tonal (#0E0F11/#131417), never white cards on black. - Hero: small caps mono kicker, medium-size headline (max 4rem), sub in secondary, CTA row — primary accent button + ghost button. Optional: a metrics strip or product panel below, bordered.
- Data is the hero: metrics, code blocks, terminal snippets, and status tables are aesthetic assets. A bordered panel with mono numbers beats a decorative illustration.
- Radius: 6–10px on panels (this is the ONE pack where a bit of radius is correct — machine parts), 4–6px on buttons. Shadows only at hover:
0 4px 20px rgba(0,0,0,0.5). - Pricing: bordered rows or 3-panel grid; featured panel gets a 1px accent border + accent dot/check list.
4. CONTENT TREATMENT
- No emoji as icons. Draw icons: 1.5px stroke, rounded caps, 16–20px grid,
#9CA3ADat rest, accent at active. - No photography by default. Dark-tech surfaces are better empty: hairlines, mono labels, and metrics.
- Status language:
status: healthy,v2.4.1,99.99% SLA— product authenticity beats marketing claims. - CTA text: concrete ("Deploy now", "Run benchmark"), never "Get started today!!".
5. MOTION (Precise)
- Durations 120–240ms. Easing
cubic-bezier(0.4, 0, 0.2, 1)(Material-style) orease-outhovers. - Hover: surface tone shift (
#0E0F11→#131417) + border brighten. Border/glow transitions only, 150ms. - One allowed flourish: a slow ambient status pulse on one accent element (like a "live" dot), 2–4s cycle, opacity only.
- Respect
prefers-reduced-motion: everything off.
6. CHECKLIST (Fail the page if…)
- Any white or light background surfaces (main background must be near-black).
- More than one accent color in use.
- Any gradient fill.
- Headline above 4rem or in a display serif.
- Body text in pure white for normal paragraphs.
- Rounded corners above 10px on panels or above 6px on buttons.
- Emoji icons or bright marketing photography.
- Any section that could not exist in a developer tool.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

