Installation
Installation takes four steps: add the marketplace, install the plugins you want, activate them, and sign in to Jira and Figma. The steps below are the install section of the repository README, rendered here so the two never drift apart. Check the prerequisites first.
tsh-product-design is still an empty scaffold. Installing it works, but it
contributes no components yet, so an empty component list after installing it is
expected, not a broken install. Every other plugin ships real skills.
Step 1 — add the marketplace
Run this inside any Claude Code session. It registers the catalog so you can browse it; nothing is installed yet.
/plugin marketplace add TheSoftwareHouse/agentic-collections
The repo is public, so no GitHub authentication is needed. Alternatives if the
owner/repo shorthand fails:
/plugin marketplace add git@github.com:TheSoftwareHouse/agentic-collections.git
/plugin marketplace add https://github.com/TheSoftwareHouse/agentic-collections.git
/plugin marketplace add https://github.com/TheSoftwareHouse/agentic-collections.git#some-branch
/plugin marketplace add ./agentic-collections # from a local clone
The catalog is registered for you, in every project by default. It takes a scope of its own — run this from a repo's root to register it for that repo only:
claude plugin marketplace add TheSoftwareHouse/agentic-collections --scope project
--scope takes user, project or local, and means the same thing here as it does
for plugins in Step 2.
Step 2 — install the plugins you want
Copy just the lines you need:
# Core — everyone
/plugin install tsh-core@tsh-agentic-collections
# Disciplines — pick the one that matches your job
/plugin install tsh-product-engineering@tsh-agentic-collections
/plugin install tsh-product-testing@tsh-agentic-collections
/plugin install tsh-product-management@tsh-agentic-collections
/plugin install tsh-product-design@tsh-agentic-collections
/plugin install tsh-platform-engineering@tsh-agentic-collections
# Stacks — pick what the project is built on
/plugin install tsh-stack-frontend@tsh-agentic-collections
/plugin install tsh-stack-nodejs@tsh-agentic-collections
/plugin install tsh-stack-serverless@tsh-agentic-collections
/plugin install tsh-stack-python@tsh-agentic-collections
/plugin install tsh-stack-php@tsh-agentic-collections
/plugin install tsh-stack-aws@tsh-agentic-collections
/plugin install tsh-stack-gcp@tsh-agentic-collections
/plugin install tsh-stack-azure@tsh-agentic-collections
Each install asks you to pick a scope:
| Scope | Who gets it | Where it's written |
|---|---|---|
| User | You, in every project | your user settings |
| Project | Everyone working on this repo | the repo's .claude/settings.json — committed, so it travels with the repo |
| Local | You, in this repo only | .claude/settings.local.json — keep it out of git |
Pick User if you're installing for yourself. Pick Project to give a whole team the plugin via the repo. Pick Local to try one out in a single repo without committing anything.
The three plugin families usually want different answers, and it's worth being deliberate about it:
- Core travels with you — User scope, same as your discipline plugin. It depends on neither your role nor the repo, so it should follow you everywhere.
- Discipline plugins travel with you — User scope. Your job doesn't change from repo to repo.
- Stack plugins travel with the repo — Project scope. The repo already knows what it's written in, so everyone working on it should get the same guidance, and nobody should carry another stack's skills around.
Prefer the shell (for onboarding scripts, or to skip the interactive prompt):
claude plugin install tsh-product-testing@tsh-agentic-collections --scope user
claude plugin install tsh-product-testing@tsh-agentic-collections --scope project
claude plugin install tsh-product-testing@tsh-agentic-collections --scope local
Three things the table doesn't say:
- Scope is resolved against your current directory. Run
projectandlocalinstalls from the target repo's root, not from wherever your session started. - To confine a plugin to one project, scope both. The marketplace has its own scope (Step 1). Scope only the install and you've still registered the catalog everywhere.
- Scopes stack. A committed project set is a starting point, not a cage —
anyone can add their own plugins on top at
userorlocalscope, and both sets load together.
local scope is only private if you keep the file out of git; nothing adds it for
you. Add .claude/settings.local.json to your .gitignore — this repo's
.gitignore does exactly that.
Installing never copies plugin files into your project. Everything lives in
~/.claude/plugins/marketplaces/, whatever the scope — scope decides which projects
load a plugin, not where it's stored.
You can also browse instead of typing names: run /plugin, go to the Discover
tab, and press Enter on a plugin to see its details and install it.
Step 3 — activate
Read the install summary:
Plugin is now active.→ you're done.Run /reload-plugins to activate.→ run that command:
/reload-plugins
If it warns that reloading will re-read the conversation, rerun it as
/reload-plugins --force. The reload summary counts only commands/ directories,
so 0 skills is normal and doesn't mean anything failed.
Step 4 — sign in to Jira and Figma, once per machine
tsh-core bundles three MCP servers. Two need one interactive login each: the
Atlassian one, so Claude reads and updates Jira work items and Confluence pages
directly, and the Figma one, so it reads designs — layout, variables, components and a
rendered export — instead of working from a description. The third, Context7, serves
library documentation and needs no sign-in.
/mcp
Pick atlassian, finish the browser sign-in, then do the same for figma. You're
done — on this machine, for every project. Every call then runs under your own
account and grants nothing you could not already open in Jira or Figma yourself.
Atlassian Cloud only; Figma works on all seats and plans. Skip either and that server
simply shows as needing authentication; nothing else breaks, though the UI
verification gate in tsh-product-engineering will report VERIFICATION NOT RUN
rather than judging a design it cannot read.
Two things deliberately left out, both documented in
plugins/tsh-core/README.md with an opt-in command:
Bitbucket, because the Atlassian server covers it only under API-token
authentication that needs an org admin to enable first, and Figma's desktop
server, because it is a separate local endpoint that fails for anyone not running
the desktop app and needs a Dev or Full seat on a paid plan.
After installing
- Skills and agents are namespaced by plugin. See First steps for how to invoke them.
- Teams can declare the marketplace and a plugin set in a committed
.claude/settings.json; the README section Onboarding a whole project team at once has the exact shape. - To pick up new plugins and new versions, see Staying current; to remove plugins, see Removing plugins.
- If something does not show up, see Troubleshooting.