8 skills · 25 entry points · one command
Agent skills for the work around the code.
A coding agent writes code well and does almost everything around it badly. It builds an interface with no idea who uses it, calls a task done without checking what was asked, and ships a page no answer engine can read. These 8 skills each take one of those gaps and give the agent a contract it has to follow — documentation, validators and small standard-library scripts. No services, no telemetry, no API keys.
npx sshlg-skills install
The family
Each pack owns one question. They compose: the router decides the route, and every route names the phrase that declines it.
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…
sheleg-design v1.49.1
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…
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…
Install
One launcher installs every pack into every agent you have, and prunes the plain Claude Code copies that would shadow your plugins.
npx sshlg-skills install
npx sshlg-skills update
npx --yes sshlg-skills@latest list
Three commands are the whole interface. install when
nothing is there, update when it is there and behind, list
to see where each member stands.
update takes no member argument on purpose: a member updated on its
own leaves the bundle in a combination nobody tested.
What it actually does
- Claude Code → each pack as a plugin, never as a plain
~/.claude/skills/copy. - Every other agent → the vercel
skills
CLI, into
~/.agents/skills/. - Then it prunes the plain Claude copies the skills CLI recreates on its own. That duplicate shadows your plugin and silently serves a stale skill — the one failure mode worth automating away.
Why a router, and not eleven more prompts
Installing a skill does not make an agent reach for it. The family writes a routing block into your agent's own instruction file: one table saying which pack answers what, and when. Every route also names the phrase that declines it, so the rule can be turned off in the sentence rather than in a file.
| Router | Answers | When |
|---|---|---|
| super-ux | what the interface must do | there is user-facing behaviour |
| sheleg-design | how it looks and moves | there is a visual layer |
| copywriting | how it sounds | text a user of the product will read |
| sheleg-dev | what it runs on to charge, track and sign in | money, tracking, sign-in or speed is being wired |
| agent-stack | how an agent system is built, judged and metered | the thing being built is an agent |
| seo-llmo | whether a machine will find it | a logged-out reader can see the surface |
| evidence-docs | what proves it | something is stated as true |
| task-pipeline | how the change reaches the repository | the change touches the repository |
| project-audit | what is actually true of this project right now | the question is the whole project, not one change |
| make-skill | how the skill itself is built | a skill or plugin changes shape |
| agent-sync | who is holding this file | the project has agent coordination on |
The manifesto this pack implements
These skills are the reference implementation of Proof of Done: The Agentic Software Development Manifesto by Sergey Sheleg. Its claim is that the unit of progress is not generated code but an evidence-carrying change: one that carries the intent it implements, the evidence that verifies it, the limits of that evidence, and the decision that accepts it. The manifesto lives in its own repository; this one is where it stops being an argument.