plexable

Plexable Claude Code Plugin

Internal plugin for the Plexable team. Bundles skills for working in Plexable's identity, voice, brand visuals, and messaging — so Claude (in Claude Code, Copilot CLI, etc.) produces work that sounds and looks like Plexable.

---

What's inside

plexable-plugin/
├── .claude-plugin/
│   ├── plugin.json          # plugin manifest
│   └── marketplace.json     # marketplace entry for distribution
├── skills/
│   ├── plexable-identity/         # who Plexable is, who it serves
│   ├── plexable-voice/            # tone, vocabulary, sentence rhythm
│   ├── plexable-brand-visuals/    # color, type, layout rules
│   └── plexable-messaging/        # pitches, proof points, outbound
└── README.md

Add more skills over time — anything Plexable-specific that Claude should know.

---

Installing it (one-time, per teammate)

The plugin lives in a private GitHub repo. Each teammate needs gh authenticated to that org.

1. Open Claude Code in any project.
2. Add the Plexable marketplace:

   /plugin marketplace add <your-private-repo-url>
   

   Example: /plugin marketplace add github.com/plexable/plexable-plugin
3. Install the plugin:

   /plugin install plexable@plexable
   

4. Confirm it's active:

   /plugin
   

The plugin's skills become available in every Claude Code session, in any project.

---

Updating the plugin (the part you asked about)

You and the team can push updates as often as you like. The flow:

For an editor (you / the team member making changes)

1. git clone this repo locally.
2. Edit a skills/*/SKILL.md file, or add a new skill folder.
3. Bump the version in .claude-plugin/plugin.json (and in marketplace.json).
4. Commit and push.

   git add .
   git commit -m "voice: add rule about em-dashes"
   git push
   

For every other teammate (to pull the update)

/plugin update plexable

That's it — Claude immediately uses the new version. No reinstall.

---

Adding a new skill

1. Create a folder under skills/, e.g. skills/plexable-case-studies/.
2. Add a SKILL.md with YAML frontmatter:

   ---
   name: plexable-case-studies
   description: Use when writing or reviewing a Plexable case study — defines structure, required sections, tone, and metric standards.
   ---
   
   # Plexable Case Studies
   ...
   

3. Description rule: Start with "Use when…" and describe triggering conditions, not the skill's workflow. This is how Claude decides to load the skill.
4. Commit, push, bump version, teammates run /plugin update plexable.

---

Writing good Plexable skills (style guide)

• One skill per topic. Don't lump "voice + visuals" together.
• Lead each skill with a one-line "what this is."
• Use tables for rules teammates need to scan.
• Include both DOs and DON'Ts — what to avoid is often more valuable.
• Quote exact phrases, hex codes, metrics — Claude won't make them up if you give it the canonical source.
• When something changes (new tagline, new color), update the skill first, then announce to the team.

---

Maintainers

• @ahmed (initial scaffold)
• Add teammates here as they take ownership of specific skills.

TODO

• Fill in real color hex codes, typography names in plexable-brand-visuals.
• Add plexable-case-studies skill with full structure template.
• Add plexable-proposals skill with the proposal template.
• Decide on a versioning cadence (per-change vs. weekly).

plexable