Skip to content
Back to search

vibes-skills

MarketplaceWorks with Claude CodeGitHub

Claude Code skills for vibe coding with a proper lifecycle: plan, design, build, simplify, security audit, Playwright tests and a release checklist.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/imranhc0--vibes/badge.svg)](/listings/imranhc0--vibes)

HTML

<a href="/listings/imranhc0--vibes"><img src="/api/listings/imranhc0--vibes/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Pick one method. Installing the same skills two ways makes each one load twice.

Claude Code plugin (recommended)

/plugin install vibes --marketplace imranhc0/vibes

On Claude Code older than 2.1.275:

/plugin marketplace add imranhc0/vibes
/plugin install vibes@vibes-skills

Restart Claude Code afterwards. Plugin skills are namespaced: `/vibes:vibes`, `/vibes:vibes-plan`, `/vibes:vibes-test` and so on.

npx

Uses the open-source [`skills`](https://github.com/vercel-labs/skills) installer. Needs Node.js 22.20 or later.

# All skills, for every project (~/.claude/skills/)
npx skills add imranhc0/vibes -g -a claude-code

# All skills, for the current project only (.claude/skills/)
npx skills add imranhc0/vibes -a claude-code

# One skill
npx skills add imranhc0/vibes --skill vibes-security-audit -a claude-code

Leave out `-a claude-code` to pick agents interactively. Set `DISABLE_TELEMETRY=1` to turn off the installer's anonymous usage data.

Manual copy

git clone https://github.com/imranhc0/vibes.git
mkdir -p ~/.claude/skills
cp -r vibes/skills/* ~/.claude/skills/

Use `<your-repo>/.claude/skills/` instead of `~/.claude/skills/` to install for one project only, and commit it so your team gets the skills too.

With npx or a manual copy, skills have no namespace: `/vibes`, `/vibes-plan`, `/vibes-test` and so on. Start a new Claude Code session to load them.

Claude.ai (your personal account)

Skills you upload to claude.ai are private to your account. They also load in Claude Code when you're signed in with the same account (Claude Code 2.1.273 or later). If you use claude.ai skills, don't also install the plugin or npx copy, or the skills will load twice.

1. Build one zip per skill. Each zip holds the skill's folder:

   git clone https://github.com/imranhc0/vibes.git && cd vibes
   mkdir -p dist && cd skills
   for s in */; do s=${s%/}; zip -r "../dist/$s.zip" "$s"; done

2. On claude.ai, open **Settings → Capabilities** and turn on **Code execution and file creation**. 3. Go to **Customize → Skills**, click **+**, then **Create skill → Upload a skill**, and choose a zip from `dist/`. Repeat for each skill. 4. Make sure each skill's toggle is on.

To update a skill, delete the old one (open it, turn off its toggle, then **… → Delete**) and upload the new zip. On a personal plan, skills can't be shared with other people; Team and Enterprise plans can share them across the organization.

The audit, simplify and test skills need to see your code and run commands, so they work best in Claude Code.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "name": "vibes-skills",
  3. "owner": {
  4. "name": "Md Imran Hossen"
  5. },
  6. "metadata": {
  7. "description": "The vibes skills for Claude Code."
  8. },
  9. "plugins": [
  10. {
  11. "name": "vibes",
  12. "source": "./",
  13. "description": "Vibe coding with a proper lifecycle: plan, design, build, simplify, security-audit, test and a release-readiness checklist."
  14. }
  15. ]
  16. }
README.md · README · 147 lines
  1. # vibes
  2. Agent skills for vibe coding with a proper software lifecycle. Describe a feature, and Claude takes it through plan, design, build, simplify, security audit, tests and a release-readiness checklist, then tells you what was and wasn't checked.
  3. ```
  4. /plugin install vibes --marketplace imranhc0/vibes
  5. ```
  6. Then, in a new Claude Code session:
  7. ```
  8. /vibes:vibes add a notes page where signed-in users can create, edit and delete their own notes
  9. ```
  10. ## Skills
  11. | Skill | What it does |
  12. |---|---|
  13. | [`vibes`](skills/vibes/SKILL.md) | The main workflow. Sizes the request, runs each phase in order, loops back on failed audits or tests, and writes a final report. |
  14. | [`vibes-plan`](skills/vibes-plan/SKILL.md) | Interviews you in rounds until every decision is settled, and records the domain glossary and decision records as they come up. |
  15. | [`vibes-design`](skills/vibes-design/SKILL.md) | Visual design direction: palette, typography, layout and copy that don't look templated. |
  16. | [`vibes-react`](skills/vibes-react/SKILL.md) | 70 React and Next.js performance rules, ranked by impact. |
  17. | [`vibes-simplify`](skills/vibes-simplify/SKILL.md) | Simplifies the code changed in this session without changing behaviour, then re-runs your checks. |
  18. | [`vibes-security-audit`](skills/vibes-security-audit/SKILL.md) | Static security review of your latest changes, with findings ranked by severity and evidence. |
  19. | [`vibes-test`](skills/vibes-test/SKILL.md) | Explores the running app, then writes and runs Playwright UI and API tests. |
  20. Every skill also works on its own. Everything the workflow needs is in this repo; there's nothing else to install.
  21. ## Requirements
  22. - [Claude Code](https://docs.claude.com/en/docs/claude-code) 2.1.275 or later for the one-line plugin install
  23. - A git repository to work in
  24. - For `vibes-test`: Node.js, or Python with `pytest-playwright`. The skill asks before installing Playwright.
  25. - Optional security tools: `gitleaks`, `semgrep`, `bandit`, `gosec`, `npm audit`, `pip-audit`. The audit uses whichever are installed and lists the ones it couldn't run.
  26. ## Install
  27. Pick one method. Installing the same skills two ways makes each one load twice.
  28. ### Claude Code plugin (recommended)
  29. ```
  30. /plugin install vibes --marketplace imranhc0/vibes
  31. ```
  32. On Claude Code older than 2.1.275:
  33. ```
  34. /plugin marketplace add imranhc0/vibes
  35. /plugin install vibes@vibes-skills
  36. ```
  37. Restart Claude Code afterwards. Plugin skills are namespaced: `/vibes:vibes`, `/vibes:vibes-plan`, `/vibes:vibes-test` and so on.
  38. ### npx
  39. Uses the open-source [`skills`](https://github.com/vercel-labs/skills) installer. Needs Node.js 22.20 or later.
  40. ```bash
  41. # All skills, for every project (~/.claude/skills/)
  42. npx skills add imranhc0/vibes -g -a claude-code
  43. # All skills, for the current project only (.claude/skills/)
  44. npx skills add imranhc0/vibes -a claude-code
  45. # One skill
  46. npx skills add imranhc0/vibes --skill vibes-security-audit -a claude-code
  47. ```
  48. Leave out `-a claude-code` to pick agents interactively. Set `DISABLE_TELEMETRY=1` to turn off the installer's anonymous usage data.
  49. ### Manual copy
  50. ```bash
  51. git clone https://github.com/imranhc0/vibes.git
  52. mkdir -p ~/.claude/skills
  53. cp -r vibes/skills/* ~/.claude/skills/
  54. ```
  55. Use `<your-repo>/.claude/skills/` instead of `~/.claude/skills/` to install for one project only, and commit it so your team gets the skills too.
  56. With npx or a manual copy, skills have no namespace: `/vibes`, `/vibes-plan`, `/vibes-test` and so on. Start a new Claude Code session to load them.
  57. ### Claude.ai (your personal account)
  58. Skills you upload to claude.ai are private to your account. They also load in Claude Code when you're signed in with the same account (Claude Code 2.1.273 or later). If you use claude.ai skills, don't also install the plugin or npx copy, or the skills will load twice.
  59. 1. Build one zip per skill. Each zip holds the skill's folder:
  60. ```bash
  61. git clone https://github.com/imranhc0/vibes.git && cd vibes
  62. mkdir -p dist && cd skills
  63. for s in */; do s=${s%/}; zip -r "../dist/$s.zip" "$s"; done
  64. ```
  65. 2. On claude.ai, open **Settings → Capabilities** and turn on **Code execution and file creation**.
  66. 3. Go to **Customize → Skills**, click **+**, then **Create skill → Upload a skill**, and choose a zip from `dist/`. Repeat for each skill.
  67. 4. Make sure each skill's toggle is on.
  68. To update a skill, delete the old one (open it, turn off its toggle, then **… → Delete**) and upload the new zip. On a personal plan, skills can't be shared with other people; Team and Enterprise plans can share them across the organization.
  69. The audit, simplify and test skills need to see your code and run commands, so they work best in Claude Code.
  70. ## Usage
  71. ```
  72. /vibes <what you want built>
  73. ```
  74. vibes picks a track and tells you which phases it will run:
  75. - **Full**: a new feature, page, endpoint or app. Runs every phase.
  76. - **Small**: a bug fix or a contained change. Writes a short plan itself and skips design unless the UI changes.
  77. - **Single phase**: `vibes plan`, `vibes design`, `vibes audit`, `vibes simplify`, `vibes test` or `vibes checklist`.
  78. It stops once to confirm the plan with you, then works through the rest. It never commits, pushes or deploys unless you ask, and it flags changes that need a human reviewer: auth, tenant isolation, secrets, billing, personal data and destructive migrations.
  79. | # | Phase | Skill | Output |
  80. |---|---|---|---|
  81. | 1 | Plan | `vibes-plan` | `.vibes/plan.md`, plus `GLOSSARY.md` and `docs/adr/` when needed |
  82. | 2 | Design (UI only) | `vibes-design` | design notes, UI code |
  83. | 3 | Build | `vibes-react` for React / Next.js, stack rules otherwise | code changes |
  84. | 4 | Simplify | `vibes-simplify` | cleaner code, same behaviour |
  85. | 5 | Security audit | `vibes-security-audit` | `.vibes/security-audit.md` |
  86. | 6 | Test | `vibes-test` | test files, `.vibes/test-report.md` |
  87. | 7 | Fix loop | phases 3 to 6, up to 3 rounds | |
  88. | 8 | Release readiness | built-in checklist | `.vibes/checklist.md` |
  89. | 9 | Report | | summary in chat |
  90. vibes asks whether you want `.vibes/` committed as a record or added to `.gitignore`.
  91. ## Update and uninstall
  92. | Installed with | Update | Uninstall |
  93. |---|---|---|
  94. | Plugin | `claude plugin marketplace update vibes-skills`, then `claude plugin update vibes@vibes-skills` | `claude plugin uninstall vibes@vibes-skills` |
  95. | npx | `npx skills update` | `npx skills remove vibes vibes-plan vibes-design vibes-react vibes-simplify vibes-security-audit vibes-test` (add `-g` if installed globally) |
  96. | Manual copy | `git pull` in your clone, then copy again | delete the `vibes*` folders from your skills directory |
  97. | Claude.ai | delete and re-upload | **Customize → Skills**, open the skill, **… → Delete** |
  98. Restart Claude Code after any of these.
  99. ## Contributing
  100. See [CONTRIBUTING.md](CONTRIBUTING.md).
  101. ## License
  102. [MIT](LICENSE). Some skills include their own license file in their folder.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.