seapowers

✨ Shared Claude Code skills, plugins, and workflows for the SEA.AI team ✨

🧩 Available Skills and Plugins

Skills

Skill	Description	Source
📝 pull-request	SEA.AI PR template with What/Why/How/Testing sections	Internal
⚛️ react-best-practices	React & Next.js performance optimization (57 rules across 8 categories)	Vercel Labs

Plugins

Coming soon! External plugin sources support is in development.

💡 What are Skills?

Claude Code skills are reusable prompt-based instructions that standardize how AI assists with common development tasks — think of them as muscle memory for your AI pair programmer. Instead of every developer explaining the same context over and over, skills encode team knowledge once and share it everywhere.

📁 Repository Structure

seapowers/                             # Repository root
├── .claude-plugin/
│   └── marketplace.json               # Makes it installable
├── .github/
│   └── workflows/
│       └── sync-upstream-skills.yml   # Weekly upstream sync
├── seapowers/                         # Self-contained plugin directory
│   ├── .claude-plugin/
│   │   └── plugin.json                # Plugin metadata
│   └── skills/
│       └── my-skill/
│           └── SKILL.md
├── upstream-skills.json               # Manifest of vendored upstream skills
└── README.md

🚀 Installation

Install globally (all projects)

Run these commands inside Claude Code:

/plugin marketplace add sea-ai/seapowers
/plugin install seapowers@sea-ai

Tip

After installing, run /plugin marketplace and enable auto-update for the sea-ai marketplace so you automatically get new skills as they're added.

This writes the following to your ~/.claude/settings.json — you can also add it manually:

{
  "extraKnownMarketplaces": {
    "sea-ai": {
      "source": {
        "source": "github",
        "repo": "SEA-AI/seapowers"
      }
    }
  },
  "enabledPlugins": {
    "seapowers@sea-ai": true
  }
}

Install per-project

Add this to your project's .claude/settings.json so every team member gets the skills automatically when working in that repo:

{
  "extraKnownMarketplaces": {
    "sea-ai": {
      "source": {
        "source": "github",
        "repo": "SEA-AI/seapowers"
      }
    }
  },
  "enabledPlugins": {
    "seapowers@sea-ai": true
  }
}

Enable only specific skills

If you only need certain skills, pass an array of skill names instead of true (works in both global and project settings):

{
  "enabledPlugins": {
    "seapowers@sea-ai": ["react-best-practices"]
  }
}

🔄 Upstream Syncing

Some skills are vendored from external repos. Instead of fetching at runtime, we keep a local copy that's automatically synced via a weekly GitHub Action.

The manifest lives in upstream-skills.json and supports two entry types:

Directory entry — syncs an entire directory from an upstream repo using a tarball download + rsync:

{
  "name": "react-best-practices",
  "type": "directory",
  "repo": "vercel-labs/agent-skills",
  "branch": "main",
  "src": "skills/react-best-practices",
  "dest": "seapowers/skills/react-best-practices",
  "license": "MIT",
  "upstream_repo": "https://github.com/vercel-labs/agent-skills"
}

File entry — syncs a single file via its raw URL (the default when type is omitted):

{
  "name": "my-skill",
  "url": "https://raw.githubusercontent.com/owner/repo/main/path/to/SKILL.md",
  "dest": "skills/my-skill/SKILL.md",
  "license": "MIT",
  "upstream_repo": "https://github.com/owner/repo"
}

The sync workflow runs weekly and opens a PR when upstream content changes. To add a new upstream skill, append an entry to the manifest using the appropriate format.

🤝 Contributing

Adding a Skill

1. Create a new directory in seapowers/skills/ with a SKILL.md file
2. Follow the skill format from the Claude Code docs
3. Open a PR and let the team review

Got a workflow that saves you time? A prompt pattern that keeps Claude on track? Ship it! The bar is low — if it helped you twice, it'll help someone else too.

🤷 Why?

Because nobody should have to explain our deploy process to Claude from scratch every Monday morning.