DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to install skins and pick a readable theme in Claude Code with Claude Skins

Add the skins plugin, restart, and switch among fifteen built-in themes with /skin.

Who it is forA developer who uses Claude Code daily and finds its default tool output hard to scan during long coding sessions.

The problemTool calls, edits and tables in Claude Code's default drawing are plain and dense, which makes it slow to see what Claude just did.

The outcomeTool rows show icons and timings, edits appear as diff cards, and the chosen skin is applied in every new session.

What you need first

  • Claude Code 2.1.287 or later, in a terminal or the desktop app's Code tab
  • Permission to run /plugin commands inside Claude Code

Steps

  1. Inside Claude Code, run /plugin marketplace add hellosverre/claude-skins.
  2. Run /plugin install skins@hellosverre-mods.
  3. Restart Claude Code. The noir skin is on by default.
  4. Type /skin to open the settings and preview skins with a live preview, or run /skin list to see every skin.
  5. Run /skin tokyo-night or another built-in name to switch, and check that tool rows and tables now use the new colours. (inferred, check the README)

Prompt for your agent

In Claude Code, install the plugin from the repo hellosverre/claude-skins by running `/plugin marketplace add hellosverre/claude-skins` and then `/plugin install skins@hellosverre-mods`, restart, and run `/skin list`. Report the list of skins shown and the one currently active. Verify that tool rows now show icons and timings.

Caveat. The README says the terminal and desktop app were checked by hand on Windows, Linux was run, and macOS, VS Code and mobile were not looked at by hand, so results there may differ.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page