Laniameda Brand Design
Laniameda Brand Design System & Landing Page Workflow
Build marketing pages and product websites that follow the laniameda design system — a warm editorial + brutalist hybrid aesthetic designed for technical/developer audiences.
Brand Identity
Mood: Warm editorial, studio console, paper & ink, artisan digital Tone: Quiet confidence — authoritative but never loud. Sharp, technical, no fluff. Audience: AI engineers, vibe coders, developers who live in the terminal Test: "These people get it" — if a developer reads the hero at 11pm and thinks that, it works.
What It Is NOT
- SaaS corporate, playful/whimsical, enterprise formal
- No Lorem Ipsum. No "game-changing". No "unlock potential".
- No pure white (
#ffffff) backgrounds. No pure black (#000000) text. - No cold/gray shadows. No neon accents.
More from michailbul/laniameda-skills
notion-sync
>
14instagram-extract
Extract text, links, and key takeaways from Instagram/Threads posts (especially carousels) and LinkedIn posts using an already-logged-in Brave/Chrome tab via OpenClaw Browser Relay. Use when the user pastes an Instagram/Threads/LinkedIn URL (or forwards screenshots) and asks something generic like “save it”, “capture this”, “summarize and store”, or “put this in the vault” — you should decide what’s worth saving, classify it into the right pillar, save it to the local KB and/or ingest prompts via the laniameda-kb skill, and also emit a compact JSON payload into a media-agent inbox file for downstream reuse.
12carousel-designer
>
11andromeda-messages
>
10deepgram-transcribe
>
10repo-kanban-pm
Install and enforce a lightweight product-management workflow inside a code repo: feature-as-kanban boards, ROADMAP status tracking, branch/PR conventions, and an optional daily OpenClaw cron PM review. Use this skill when (1) starting work in a NEW repository/project that does not yet have a ROADMAP+feature-KANBAN system, (2) you are delegated to spin up a new project and want multi-agent coordination from day one, or (3) you are asked to fix/restructure an existing repo and introduce an organized backlog/feature tracking system. Also use when adding a daily PM audit loop (cron) to keep code + docs + PRs in sync.
10