Skip to content

Plugin with MCP server

Software Engineering (Claude Plugins)

A Claude Code plugin with agents and skills for code review, debugging, documentation, security auditing and payment integration guidance, bundling an optional Perplexity MCP server.

  • Community
  • Runs locally
  • API key

Repository and documentation last checked Built from public product pages and documentation. SourcesClaim this listing

Not listed in the ecommerce MCP directory

Ecommerce is incidental to what it does.

Browse the MCP servers that are listed

ecommerceguide summary

Software Engineering (Claude Plugins) bundles engineering workflows (code review, debugging, documentation generation) into a plugin collection for Claude Code. The repository targets engineering leads at ecommerce companies running Claude Code, giving them reusable prompts and scaffolding for common tasks rather than ad-hoc instructions. Useful for CTOs standardizing how internal teams apply AI to pull requests, incident triage, and documentation upkeep across commerce codebases.

Why it stands out

Open-source, forkable prompt bundle rather than a hosted product, so teams own and customize the workflows.

What Software Engineering (Claude Plugins) does

ecommerceguide editorial
  • Apply reusable prompt templates for code review across pull requests
  • Run structured debugging sessions with consistent context-gathering steps
  • Generate and maintain repository documentation tied to actual code
  • Standardize AI-assisted engineering workflows across distributed commerce teams
  • Install as open-source plugins, modify prompts to match conventions

How ecommerce teams could use it

ecommerceguide editorial

Illustrative scenarios written by ecommerceguide from the product's documented capabilities. They are not customer case studies.

  1. Headless DTC brand, 8-person engineering team

    CTO wants every PR against the Next.js storefront to get a first-pass AI review before human review; installs the code-review plugin into the team's Claude Code setup and tunes prompts to flag Shopify API misuse and accessibility regressions

    Intended outcomeCuts human review time per PR and catches recurring junior-dev mistakes before they reach staging

  2. Marketplace platform, 25-engineer org split across three squads

    Platform lead standardizes debugging and incident-triage prompts so every on-call engineer gathers the same logs, traces, and service context when paging Claude during a Sev-2

    Intended outcomePost-incident reviews show more consistent root-cause write-ups and fewer missed context items across squads

  3. B2B commerce SaaS engineering team of four

    Founding engineer installs the documentation plugin to auto-maintain READMEs and API docs tied to the actual code

    Intended outcomeInternal docs stay closer to current behaviour instead of drifting for months

Who it suits

ecommerceguide editorial

Best for

You're an engineering lead already running Claude Code and want shared, version-controlled prompt scaffolding for reviews, debugging, and docs instead of each engineer rolling their own.

Probably not for

Your team does not use Claude Code, or if you need a managed product with SSO, audit logs, and vendor support rather than an open-source plugin collection you maintain yourself.

Business size
Any stage, 3 to 50 engineersValue scales with team size since the point is standardizing workflows across engineers, but the plugins are lightweight enough for a small founding team and adoption is gated by Claude Code usage rather than GMV.

Technical details

From the vendor's own pages

From the server's repository, documentation and MCP directory listings.

Transport
stdio (local)
Authentication
API keyexport PPLX_API_KEY="your-perplexity-api-key"
Package
sgaunet/claude-plugins
Language
Shell
Licence
MIT
Repository last updated
24 Sep 2026

Connect Software Engineering (Claude Plugins)

Third-party data

Setup documented for

Install command
/plugin marketplace add sgaunet/claude-plugins

Command as listed on the repository README, not tested by ecommerceguide. Check the repository README (opens in a new tab) for configuration and credentials before running it.

Sources

ecommerceguide profiles are built from public product information and written for ecommerce teams. We do not test products, and paying never changes where a listing ranks.

Also listed on Build with Claude.

See something incorrect? Report an update