carousel-brand-system
Carousel Brand System
Build a locked, production-ready brand design system for social media carousels. The output is a color + typography + gradient + combo system that feeds directly into carousel production (Canva, Figma, or HTML).
This skill runs as an interactive conversation, not a one-shot generation. The user explores, picks, and you lock.
When to use this vs. other skills
| Skill | Use when |
|---|---|
| carousel-brand-system (this) | Building the visual system that powers all carousels |
| carousel-designer | Producing an individual carousel using an existing system |
| brand-guidelines-builder | Creating a general brand identity doc from scratch |
| laniameda-brand-design | Building website/landing page designs in Pencil |
| typography-master | Deep-diving into font exploration independently |
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