ssheleg skills → sheleg-design

how it looks and moves

sheleg-design

The taste layer: cinematic scroll-driven landing pages (one scroll clock, motion that degrades to calm, WebGL particle formations), product-UI style packs with a ready token layer each, and the Figma border — tokens as variables, design to code.

Install this pack on its own, or use it with the ssheleg harness.

v1.64.0pinned in this release of the family
1skill in the pack
1routing rule it owns

What it ships

Each name below is an entry point an agent can be routed to.

Shape: static. Packs and tokens are chosen, not discovered. The choice is recorded in the pack, so a second run reproduces the first.

sheleg-design

Use when deciding how something LOOKS or MOVES — landing/hero pages, dashboards, admin/internal tools, mobile screens, web decks, chat/agent UIs; particle/WebGL, scrubbed motion, drift; tokens, themes, palettes, typography, Figma mockups. Not for structure, copy, backend or.pptx.

Browse all 39 style packs →

the catalogue, rendered from each pack's own token layer — a data surface too large for this page, kept where it is built


This page is built from one of its packs

Not an illustration of the pack — the page you are reading consumes it. The site's token layer is workbench, the pack this skill ships for product UI, copied from its own tokens/workbench.css and consumed as var(--…) with no literal hex anywhere in the generator.

--bgapp ground
--panelcards, bars, dialogs
--panel-2inset, quiet stat tiles
--border1px lines
--accentthe one accent
--okdone, healthy
--warnneeds a human
--dangerfailed

Two decisions this page had to make out loud. workbench is the core contract: it declines ## Hero, ## Components, ## Responsive and ## Signature element, so those four are authored rather than inherited — and the pack requires saying so instead of filling them from the token layer with a citation attached.

The pack whose register matched this site exactly was field-notes, for open-source and developer tools sold on auditability. It was refused on its own words: its palette section says the dawn gradient has no dark twin and "do not ship the hero in dark". This site is dark, so the register lost to the constraint.


Install just this one

Every pack installs standalone. The whole family is one command.

any agent the skills CLI supports
$
npx skills add ssheleg/sheleg-design-skill
claude code, as a plugin
$
claude plugin marketplace add ssheleg/sheleg-design-skill && claude plugin install sheleg-design@sheleg-design-skill

When the agent reaches for it

These are the rules the family writes into your agent's own instruction file — verbatim. Each one states the rule, the boundary in both directions, and the phrase that declines it.

/sheleg-design — how it looks and moves

  • when: there is a visual layer
  • decline it: no design

If sheleg-design is installed, the visual layer goes through it — all surfaces: tokens/themes, typography/rhythm, motion and calm fallback, brand, Figma variables and design-to-code without hand-copied values. Before design/redesign/layout/front-end/mobile UI, run npx sshlg-skills pack design: lane owners and exact missing-tool install commands; reports, never installs. Accessibility has NO family owner; listed tools are not additional entry points.

The boundary — "HOW it looks is being decided." NOT through it: structure (super-ux), text (copywriting), backend, internal scripts.

Refusal phrase: "no design" or «без дизайна».

Among the routers: super-ux owns the wireframe; sheleg-design the visual layer and motion.


The rest of the family

super-ux v0.59.1

what the interface must do

Scenario-driven UI development: a versioned design chain in docs/ux/ — the product vision, personas and jobs, user flows and the paid-acquisition funnel among them, a screens-and-states map with Figma frames…

7 skills/super-ux

task-pipeline v1.90.2

how a change reaches the repository

Full-cycle delivery orchestrator: an intake grill turns the request into a complete brief, then ten gated stages carry it from docs to acceptance, refusing to advance until each gate passes.

3 skills/task-pipeline

agent-sync v1.21.5

who is holding this file right now

Coordination plane for concurrent agents: leases with a TTL so two agents cannot claim the same work, race-free id reservation, a run journal and a generated board, over a pluggable knowledge cloud.

1 skill/agent-sync

make-skill v0.29.2

how the skill or plugin itself is built

A skill that builds skills: create, retrofit, audit and publish agent skills and Claude Code plugins

1 skill/make-skill

seo-aeo-audit v0.26.3

whether a machine will find it

Evidence-first website audit for search and answer engines: ten tracks from crawl access to AI citation mechanics, every finding backed by an observation and every recommendation tiered, ending in…

1 skillRead →

sheleg-dev v0.13.2

integrations: money in, tracking, errors, sign-in, speed

The integration layer a product reaches once it has users: Stripe subscription billing reconciled into your own database

7 skills/sheleg-dev

agent-stack v0.25.5

orchestration, prompts, evals, protocols, and the LLM wallet

Production patterns for AI agent systems, in four skills. The orchestrator: tool-calling loops that survive context pressure, pipelines with human checkpoints and resume, provider routing with fallback…

4 skills/agent-stack

telegram-dev v0.2.2

which Telegram API each surface speaks, and what each one costs

Telegram, split by the API each surface actually speaks, in three skills. telegram-bots covers the official HTTP Bot API

3 skills/telegram-dev

xr-dev v0.3.2

how a Quest product moves from platform choice to launch and operation

Quest product delivery from platform choice to launch and operation, with stage owners, evidence gates and next actions.

7 skills · a catalogue of its own/xr-dev

web3d-dev v0.1.2

how realtime 3D on the web runs, ships its assets and moves

Realtime 3D on the web with three.js and React Three Fiber, in three skills split by the question. web3d-runtime owns how the scene runs

3 skills/web3d-dev