Craft, packaged.
A skill is a set of instructions a coding agent loads before it starts working, so the work comes out in a known shape instead of a generic one. These five carry the conventions I use every day: a visual language with verified tokens, command-line tooling, and manuscript review in two languages. Two are public; the other three are shared on request.
Pure Design UI
madsondeluna/skill-pure-design-ui OpenThe visual language behind every interface here. Four colour modes, tokens checked by script, glass and liquid materials, a pointer-driven light layer, motion recipes, twelve review routines and matplotlib and plotly themes. It ships the language files, so a project starts already inside the conventions.
CLI DevOps with ultimate UI
madsondeluna/skill-cli-devops-and-ui Open · pageTerminal tools that survive a pipe and still look like something. Behaviour comes first: streams, exit codes, help text, TTY detection, configuration precedence, completion. Appearance follows: gradients, spinners, live panels, tables and diffs. Covers Bash, Python, TypeScript, Go and Rust, and audits an existing tool without rewriting what already works.
Install one
A skill is a folder with a SKILL.md and its references. Copy it into the agent's skills directory and it becomes available by name. A skill that exists only in its repository cannot be loaded, whatever a listing says.
git clone https://github.com/madsondeluna/skill-pure-design-ui
cp -R skill-pure-design-ui/skills/* ~/.claude/skills/Seen working
The atlas of protein language models on this site is built entirely inside the first two: the interface follows Pure Design, and every check it had to pass came from the review routines that ship with the skill.