liatrio-brand-guidelines
Liatrio Brand Guidelines
When to Use
Use this skill when the user asks for any of the following:
- Liatrio-branded UI implementation (web, docs, decks, screenshots)
- brand audits and compliance review deliverables
- logo and logomark variant selection for light or dark backgrounds
- typography, color, spacing, iconography, or component decisions
- correcting stale or conflicting brand values in existing artifacts
Source Priority and Conflict Resolution
If sources disagree, use this order:
https://www.liatrio.com/brand-data.json(canonical structured source)references/liatrio-brand-guidelines.md(local detailed reference)assets/liatrio-brand-guidelines-consolidated.png(visual snapshot)
More from liatrio-labs/ai-prompts
git-commit-conventional
Create Conventional Commit messages and execute safe git commits from working tree changes. Use when users ask to create a commit, write a conventional commit message, split broad changes into multiple commits, stage only parts of files, run pre-commit before committing, or perform a quick commit-time quality review with severity guardrails.
24create-pull-request
Generate a reviewer-ready pull request or merge request title and description from branch changes. Use when a user asks to draft PR/MR content, summarize branch deltas against a base branch, or optionally create the PR with gh/glab after approval.
23create-mermaid-diagrams
Create, validate, and repair Mermaid diagrams for technical documentation with a deterministic CLI feedback loop. Use when an AI needs to create Mermaid diagrams, improve Mermaid diagram quality, validate Mermaid fences in markdown, diagnose Mermaid rendering failures, or fix Mermaid syntax and formatting issues.
21branch-surgery-pr-split
Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.
21uv-usage
Provides concise guidance for using uv (Python package manager), including project workflows, pip-compatible commands, Python version management, and PEP 723 inline script dependencies. Use when users mention uv, uv run, inline dependencies, PEP 723, or Python dependency/project management.
16tilt-dev
Manage local development environments with Tilt. Use when working with projects that run services via Tilt (indicated by presence of Tiltfile), including checking service status, viewing logs, troubleshooting connectivity issues, or managing the Tilt stack. Essential for projects using Tiltfile with local_resource for orchestrating backend, frontend, and other services.
15