claude-skills: Instructions file for Claude Code

Claude Skills

Repository: https://github.com/jezweb/claude-skills Owner: Jeremy Dawes (Jez) | Jezweb

Production workflow skills for Claude Code CLI. Each skill guides Claude through a recipe to produce tangible output: working deliverables, not knowledge dumps.

Philosophy

• Every skill must produce visible output (files, configurations, deployable projects); reference material Claude already knows does not earn a place.
• "The context window is a public good": only include what Claude doesn't already know.
• Teach patterns, not ship scripts: skills teach Claude what to do, and Claude generates scripts adapted to the user's environment. Pre-built scripts in scripts/ are the rare exception; proven implementation patterns go in references/ for Claude to adapt.
• Follow the official Claude Code plugin spec.

Layout

plugins/<plugin>/skills/<skill>/, one folder per plugin and skill; .claude-plugin/ holds marketplace.json and plugin.json; README.md is the public overview; LICENSE is MIT. The folders are the truth, so this file lists no plugins, skills or counts. A plugin carries .claude-plugin/plugin.json (name, description, author) and auto-discovers its skills/; the skill folder layout is SKILL_SHAPE.md "Multi-file layout".

Adding a New Plugin

1. mkdir -p plugins/my-plugin/{.claude-plugin,skills}
2. Create .claude-plugin/plugin.json:

   {
     "name": "my-plugin",
     "description": "What this plugin does.",
     "author": { "name": "Jeremy Dawes / Jezweb", "email": "[email protected]" }
   }
   

3. Add skills inside plugins/my-plugin/skills/, each with SKILL.md.
4. Add an entry to .claude-plugin/marketplace.json:

   { "name": "my-plugin", "description": "...", "source": "./plugins/my-plugin", "category": "development" }
   

5. Update the table in README.md.

Categories: development, design, productivity, testing, security, database, monitoring, deployment

Creating a Skill