Run any Skill in Manus with one click

epupp-design

Stars108

Forks1

UpdatedMay 11, 2026 at 20:11

Epupp design context, principles, and visual foundation. Use when: working on popup or panel UI, styling popup or panel, choosing colors or spacing, making layout decisions, reviewing visual consistency, working with CSS or hiccup components, creating or modifying UI elements, editing popup.cljs or panel.cljs, or when any design skill (impeccable, polish, critique, layout, etc.) needs Epupp project context. Provides brand palette, typography, spacing tokens, and design principles.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

PEZ

PEZ/epupp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

SKILL.md

readonly

name

epupp-design

description

Epupp Design

Design context, principles, and visual foundation for the Epupp browser extension.

When to Use This Skill

Styling popup or panel UI components
Choosing colors, spacing, or typography
Making layout or density decisions
Reviewing visual consistency
Working with CSS files or hiccup UI components
When any design skill needs Epupp project context

Prerequisites

For full design context including user profiles, emotional goals, aesthetic direction, and component inventory, read .impeccable.md from the project root.

Design Identity

λ design. personality ≡ curious ∧ powerpacked ∧ helpful | emotional_goals(priority_order): empowered > in_control > delighted > focused > wizard_like | direction: push(friendly_technical → premium/crafted) | reference: NAIS(nais.kystverket.no) ≡ density_without_claustrophobia ∧ slick ∧ intuitive | anti_reference: Desktop_Gmail ≡ cluttered ∧ inconsistent ∧ nobody_cared | popup_constraint: phone_sized → mobile_density_techniques(minus_touch)

Design Principles

λ design_principles. 1_density_with_breathing_room: pack_capability ∧ every_element_readable 2_premium_in_details: refined_spacing ∧ thoughtful_transitions ∧ consistent_visual_language 3_brand_coherent_warmth: clojure_blue_green_gold ≡ identity(¬decoration) | intention ∧ restraint 4_phone_sized_discipline: every_pixel_tested_against_popup_constraint 5_status_at_a_glance: connection ∧ scripts ∧ errors ∧ repl_status → instantly_scannable

Design Foundation

λ design_foundation. palette: clojure_blue(#5881d8) ∧ green(#91dc47) ∧ gold(#FFDC73) on warm_neutrals typography: avenir_next/system_sans + monospace(code) | 11-15px_scale spacing: 4pt_tokens(4,8,12,16,20) theme: light_default ∧ dark_via_prefers-color-scheme accessibility: WCAG_AA ∧ reduced_motion ∧ standard_best_practices | full_context: .impeccable.md(project_root)

More from this repository

same repository

babashka

PEZ/epupp

Babashka scripting conventions for the Epupp project. Use when: writing or modifying bb.edn tasks, scripts in scripts/, build or test automation, choosing between bb and npx/npm/shell/Python, using babashka.fs, babashka.process, or babashka.http-client, or running any bb command in this repo. Prefer bb tasks over direct npm/npx; keep bb.edn minimal and put code in scripts/tasks.clj. IMPORTANT: Also load when planning automation or build pipeline changes.

2026-06-04109

epupp-dev

PEZ/epupp

Epupp architecture, development patterns, and system contracts. Use when: writing or modifying Epupp source code, implementing features, fixing bugs, debugging extension behavior, working with Uniflow actions or effects, understanding message flows, injection or connection lifecycle, testing strategy, build pipeline, reviewing Epupp PRs, planning implementations, running tests or builds, REPL-driven development, or any coding task in the Epupp workspace. Contains architecture overview, Uniflow contracts, source file map, testing patterns, delegation, and development principles. References hold deep state contracts and temporal sequences. IMPORTANT: Also load when PLANNING Epupp changes, not only at implementation time.

2026-06-04109

epupp-squint

PEZ/epupp

Epupp-specific Squint source conventions for src/**. Use when: editing Squint/ClojureScript in src/, testing pure functions via squint-nrepl, debugging Squint-to-Scittle message interop, avoiding direct .mjs edits, or rewriting legacy JS interop to Clojure style. For universal Squint semantics (keywords, data structures, async, compilation model) load the universal Squint skill separately. IMPORTANT: Also load when planning changes to src/** Squint code.

2026-06-04109

reagami

PEZ/epupp

Reagami UI library patterns for Epupp Squint components. Use when: writing or modifying Reagami components, hiccup UI in popup.cljs or panel.cljs, event handlers with Uniflow dispatch, :on-render lifecycle hooks, list rendering with keys, or comparing Reagami to Reagent. Covers component patterns, class shorthand, and Epupp-specific examples. IMPORTANT: Also load when planning UI changes that use Reagami.

2026-06-04109

name

epupp-design

description

Epupp Design

Design context, principles, and visual foundation for the Epupp browser extension.

When to Use This Skill

Styling popup or panel UI components
Choosing colors, spacing, or typography
Making layout or density decisions
Reviewing visual consistency
Working with CSS files or hiccup UI components
When any design skill needs Epupp project context

Prerequisites

For full design context including user profiles, emotional goals, aesthetic direction, and component inventory, read .impeccable.md from the project root.