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.
What it ships
Each name below is an entry point an agent can be routed to.
- sheleg-design
Shape: static. Packs and tokens are chosen, not discovered. The choice is recorded in the pack, so a second run reproduces the first.
the catalogue, rendered from each pack's own token layer — a data surface too large for this page, kept where it is built
Install just this one
Every pack installs standalone. The whole family is one command.
npx skills add ssheleg/sheleg-design-skill
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: «без дизайна» or «как есть».
If sheleg-design is installed, the visual layer goes through it — tokens and themes, typography and rhythm, motion and its degradation to calm, the brand's visual language, and the Figma seam (tokens as variables, design into code without hand-copied values). A cinematic landing page, a dashboard, an admin panel, an agent's interface — one and the same layer.
The boundary — "HOW it looks is being decided." NOT through it: a purely structural change (what sits where is super-ux), text (copywriting), the backend, internal scripts with no interface. Picking a palette for a log parser is how you teach an agent to route around it.
Refusal phrase: «без дизайна» or «как есть».
Among the routers: super-ux decides what the interface must do; sheleg-design how it looks and moves. The wireframe goes to the first, the visual on top of it to the second.
The rest of the family
super-ux v0.48.0
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…
task-pipeline v1.77.0
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.
agent-sync v1.17.0
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.
make-skill v0.23.1
A skill that builds skills: create, retrofit, audit and publish agent skills and Claude Code plugins — Agent Skills standard conformance, marketplace layout, version sync, validator + CI, every distribution…
seo-aeo-audit v0.25.1
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 a…
sheleg-dev v0.10.0
The integration layer a product reaches once it has users: Stripe subscription billing reconciled into your own database — checkout, renewals, seats and proration, refunds, claim-first webhook idempotency…
agent-stack v0.13.2
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 and…