Engineering portfolio
A restrained portfolio where case-study evidence and technical decisions lead the visual hierarchy.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
DESIGN.mdReference it from AGENTS.md.DESIGN.mdImport it from CLAUDE.md.DESIGN.mdReference it from GEMINI.md.Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
See the design before you give it to an agent
This sandboxed preview is rendered directly from the same DesignBrief embedded in the downloadable DESIGN.md.
What this preset defines
The file gives an agent concrete design constraints instead of a vague request to “make it look good.”
- Product
- portfolio
- Layout archetype
- portfolio
- Density
- spacious
- Base radius
- 10px
- Type scale
- 1.2
#0e1116surface#171b22text#f2f5f8muted#9aa6b2accent#6cb6ffsuccess#7ee787warning#e3b341danger#ff7b72Required layout sections
- Identity
- Selected work
- Case study
- Technical principles
- Contact
How to use it
The preset is useful without AI and does not execute code.
- 01Preview and customize
Check desktop and mobile, then open the visual builder if the palette, typography, spacing, or sections need adjustment.
- 02Download DESIGN.md
Save it in the repository root. It contains readable design rules plus the versioned machine-readable DesignBrief.
- 03Connect your agent
Add the generated integration snippet to AGENTS.md, CLAUDE.md, or GEMINI.md so the agent explicitly reads the design system.
DESIGN.md is a OneLiners convention. The included integration file explains exactly how to use it with your selected agent.
Start with DESIGN.md, then take only the extras you need
The main download is human-readable Markdown. JSON is available only as an optional design-token file.
Product direction, semantic palette, typography, layout, responsive behavior, accessibility, and an importable DesignBrief.
3359 bytes · MarkdownView generated DESIGN.md
# Engineering portfolio
## Product direction
- **Page type:** portfolio
- **Layout archetype:** portfolio
- **Audience:** Engineering leaders and collaborators
- **Goal:** Demonstrate impact, judgment, and implementation quality.
- **Tone:** Confident, thoughtful, and specific
## Visual system
- Use the semantic palette below; never use color without meaning.
- Heading: Inter, ui-sans-serif, system-ui, sans-serif; body: Inter, ui-sans-serif, system-ui, sans-serif; code: JetBrains Mono, ui-monospace, monospace.
- Density is spacious; base radius is 10px; shadows are subtle.
- Icons: Lucide-style outline icons with consistent 1.75px strokes.
- Imagery: Use product-specific imagery only when it explains the workflow; never use decorative filler..
## Semantic palette
| Role | Value | Intended use |
| --- | --- | --- |
| Background | `#0e1116` | Page canvas and the deepest application layer |
| Surface | `#171b22` | Cards, panels, navigation, and raised regions |
| Text | `#f2f5f8` | Primary copy, labels, and high-emphasis content |
| Muted | `#9aa6b2` | Secondary copy, metadata, and inactive controls |
| Accent | `#6cb6ff` | Primary actions, focus, selection, and active state |
| Success | `#7ee787` | Confirmed success and healthy state |
| Warning | `#e3b341` | Caution, pending review, and non-blocking risk |
| Danger | `#ff7b72` | Errors, destructive actions, and blocking risk |
The optional `design-tokens.css` from the full export pack mirrors these values. This `DESIGN.md` remains complete when used on its own.
## Layout and content
1. Identity
2. Selected work
3. Case study
4. Technical principles
5. Contact
## Responsive and accessibility
- Collapse sidebars into an explicit drawer and preserve the primary task before secondary metadata..
- Meet WCAG AA contrast, preserve visible focus, and respect reduced motion.
- Do not reduce essential content or actions on mobile.
## Machine-readable OneLiners DesignBrief
<!-- oneliners-design-brief:v1 -->
```json
{
"schemaVersion": "1",
"name": "Engineering portfolio",
"pageType": "portfolio",
"layoutStyle": "portfolio",
"audience": "Engineering leaders and collaborators",
"goal": "Demonstrate impact, judgment, and implementation quality.",
"tone": "Confident, thoughtful, and specific",
"palette": {
"background": "#0e1116",
"surface": "#171b22",
"text": "#f2f5f8",
"muted": "#9aa6b2",
"accent": "#6cb6ff",
"success": "#7ee787",
"warning": "#e3b341",
"danger": "#ff7b72"
},
"typography": {
"heading": "Inter, ui-sans-serif, system-ui, sans-serif",
"body": "Inter, ui-sans-serif, system-ui, sans-serif",
"mono": "JetBrains Mono, ui-monospace, monospace",
"baseSize": 16,
"scale": 1.2
},
"density": "spacious",
"radius": 10,
"shadow": "subtle",
"sections": [
"Identity",
"Selected work",
"Case study",
"Technical principles",
"Contact"
],
"iconStyle": "Lucide-style outline icons with consistent 1.75px strokes",
"imagery": "Use product-specific imagery only when it explains the workflow; never use decorative filler.",
"mobileStrategy": "Collapse sidebars into an explicit drawer and preserve the primary task before secondary metadata.",
"accessibility": {
"contrastTarget": "WCAG AA",
"reducedMotion": true,
"visibleFocus": true
}
}
```
Real example
Input
portfolio: Demonstrate impact, judgment, and implementation quality.
Expected result
A spacious portfolio using #6cb6ff as the semantic accent and 5 defined sections.