egoisutolabs
- 7 skills
- 0 followers
- 1 day ago last updated
- ▌ Radical 2030 · egoisutolabsBias Figma design output toward 2030-aligned radical aesthetics and explicitly reject generic 2022 SaaS defaults. Use when the designer asks for "2030", "futuristic", "radical", "anti-polish", "cyberpunk", "spatial UI", "HUD", "editorial", "brutalist", "maximalist", "Y2K", "AI-native", "make this less generic", "not another SaaS landing", or signals a clear preference for forward-looking design. Works in concert with the `design-system` skill — this skill filters the style pool and enforces anti-patterns, design-system produces the Figma output.
- ▌ Ambient Depth · egoisutolabsAdd premium ambient glow / atmospheric depth to dark-mode Figma screens using blurred alpha ellipses. Use when the designer asks for "ambient depth", "premium feel", "glow behind hero number", "iOS-style atmosphere", "aurora background", "dark mode with depth", or similar. Works on any frame; no component dependency.
- ▌ Design System · egoisutolabs bundleTurn a product brief into a Figma design system — color palette, type pairing, aesthetic/style, layout spine, and component scaffold — as real Figma Variables, Paint Styles, Text Styles, and Components. Use when the designer asks to "set up a design system", "pick colors and fonts for a new app", "build a brand foundation in Figma", "give me a palette and type scale", "start a new project", "scaffold a design system", or anything that needs a coherent visual foundation before screens get built. Reads from bundled reference data (161 palettes, 57 type pairings, 85 styles, 161 product-type rules) to make opinionated recommendations, not defaults.
- ▌ Rename Layers · egoisutolabsRename Figma layers semantically based on their content, role, and position. Use when the designer asks to "rename layers", "clean up layer names", "fix Rectangle 1234 names", "give these semantic names", or similar. Operates on the current Figma selection by default.
- ▌ Tab Metaphors · egoisutolabsDesign multi-tab app screens (fitness / analytics / productivity / social) so each tab uses a distinct structural layout instead of just rotating accent colors. Use when the designer asks to "design a tab bar app", "make 4 screens for a fitness app", "Home / Insights / Profile screens", or any multi-screen app where the screens share chrome but serve different content kinds. Prevents the "four templated screens that feel fake" trap.
- ▌ Mercury Gotchas · egoisutolabsReference for chaining Mercury MCP calls safely. Covers batch sizing limits, auto-layout sizing modes, text style application order, off-canvas scaffolding, corner radius quirks, and the "verify visually" discipline. Consult when composing multi-step Mercury operations, when a batch is failing, when auto-layout output looks wrong, or before declaring a design complete.
- ▌ Variant Component Setup · egoisutolabsCreate a multi-variant Figma component correctly. Use when the designer asks to "make this a variant", "add size/state variants", "build a button with primary/secondary/ghost", "turn this into a component set", or any task that needs VARIANT properties. Covers the full promote → clone → combine → add properties sequence and avoids the "variant properties require component set" trap.