---
name: pivoshenko-brand-guidelines
description: Apply Volodymyr Pivoshenko personal brand guidelines to content, UI, and visual decisions. Use when drafting or editing pages, blog posts, docs, components, themes, or assets that should match pivoshenko.dev style.
updated_at: 2026-03-16
---

# Pivoshenko Brand Guidelines

Use this skill to keep output aligned with the established pivoshenko style.

## Workflow

1. Read [`references/brand-system.md`](references/brand-system.md).
2. Identify the artifact type: `ui`, `content`, `theme`, or `mixed`.
3. Apply the matching rules from the reference file.
4. Run the quality checklist before returning output.

## Default Rules

- Keep style minimal, technical, and practical.
- Prefer monospace-first UI (`JetBrains Mono` style) and compact density.
- Use neutral stone surfaces for product UI; add accent colors only with intent.
- Keep copy factual and direct; avoid hype and marketing-style language.
- Preserve dark/light parity with subtle transitions.

## Output Modes

### UI and Frontend

- Apply the tokenized typography and color roles from the reference.
- Keep structure simple: thin borders, restrained radius, low-motion interactions.
- Use accent colors as highlights, not as full-page backgrounds.

### Writing and Copy

- Use a first-person, practitioner voice where relevant.
- Favor concrete wording over abstract claims.
- Keep descriptions short and operational.

### Theme and Palette Work

- Use the `morok` palette as the accent source of truth.
- Keep semantic grouping: `accent`, `text`, `surface`.
- Maintain readability against deep dark surfaces.

## Guardrails

- Do not switch to loud gradients or decorative visual noise unless requested.
- Do not use generic startup copy patterns.
- Do not introduce whimsical iconography or playful language by default.
- Do not break the monochrome-first layout rhythm.