Skip to content
Back to search

sarkhans-claude-starter

MarketplaceWorks with Claude CodeGitHub

Sarkhan’s Claude Starter for Claude Code

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sarkhandigitech--sarkhans-claude-starter/badge.svg)](/listings/sarkhandigitech--sarkhans-claude-starter)

HTML

<a href="/listings/sarkhandigitech--sarkhans-claude-starter"><img src="/api/listings/sarkhandigitech--sarkhans-claude-starter/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.

These steps run a script from the network that findsafeskills does not scan.

1. Put the app in Applications

Open the downloaded `Sarkhans-Claude-Starter.dmg` and drag **Sarkhan’s Claude Starter** onto the **Applications** folder. If your Mac account has no admin rights, drag it into the **Applications** folder inside your home folder instead (Finder → Go → Home; create a folder named `Applications` if it isn't there).

2. Allow it once

The app isn't notarized by Apple (that needs a paid Apple developer account). That's why macOS asks you to confirm it **once**, the first time you open it. Apps from developers who pay Apple for notarization show a simple **Open** button instead.

**macOS 15 Sequoia, macOS 26 Tahoe and macOS 27 Golden Gate (the current version)** 1. Double-click **Sarkhan’s Claude Starter** in Applications. macOS says the app was not opened. Click **Done**, not Move to Trash. 2. Open the **Apple menu** → **System Settings** → **Privacy & Security**. 3. Scroll all the way down to **Security**. Next to the message that the app was blocked to protect your Mac, click **Open Anyway**. 4. In the next window click **Open Anyway** again and confirm with your password or Touch ID. The app opens.

The **Open Anyway** button appears only after step 1 and stays for about an hour. If you don't see it, do step 1 again.

**macOS 13 Ventura and macOS 14 Sonoma** Right-click (or Control-click) the app in Applications → **Open** → **Open**.

After this, the app opens normally with a double-click. Updates install themselves from inside the app and don't ask again.

3. Set it up

The app opens a short setup screen: - **Node.js**, **Git** and **Claude Code**: press the button if one is missing and finish the installer. - **Projects folder**: choose the folder with your projects. - **Claude's language**: the language Claude explains things in.

Then select your projects and press **Set up**. **Open in Claude Code** in a project's panel opens Terminal there and starts Claude.

Updates

The app checks for new versions when it opens, every 30 minutes, and when you switch back to it. When one is available, an **Update to x.y.z** button appears: it downloads the new version, replaces the app and restarts. If the app's folder needs admin rights, macOS asks for your password. Set-up projects get new rules automatically.

For developers: install from Terminal

If you're comfortable with Terminal, this one line installs or reinstalls the latest version without the approval step:

curl -fsSL https://raw.githubusercontent.com/sarkhandigitech/sarkhans-claude-starter/main/install.sh | bash

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 · 23 lines
  1. {
  2. "name": "sarkhans-claude-starter",
  3. "description": "Sarkhan’s Claude Starter for Claude Code",
  4. "owner": {
  5. "name": "sarkhandigitech"
  6. },
  7. "plugins": [
  8. {
  9. "name": "sarkhans-starter",
  10. "source": "./plugins/sarkhans-starter",
  11. "description": "Guardrails, rules, specialist agents and skills for professional work with Claude Code: third-eye reports, no invented APIs, safe git, design lock, database review.",
  12. "version": "4.10.0"
  13. },
  14. {
  15. "name": "modern-web-guidance",
  16. "source": {
  17. "source": "github",
  18. "repo": "GoogleChrome/modern-web-guidance"
  19. },
  20. "description": "Modern web platform guidance for coding agents by Google Chrome (Apache-2.0): accessibility, performance, security and modern HTML/CSS. Installed together with sarkhans-starter."
  21. }
  22. ]
  23. }
README.md · README · 162 lines · 1 finding marked
  1. <p align="center"><img src="brand/logo.svg" width="128" height="128" alt="Sarkhan’s Claude Starter logo"></p>
  2. # Sarkhan’s Claude Starter
  3. Rules Claude Code can't skip, a team of specialist agents, and a report on every change — for projects in any language, with extra support for TypeScript/Next.js, Go, PHP (Laravel/Symfony), Python (Django/FastAPI), Rust, Java/Kotlin, .NET, Ruby, Dart/Flutter, Swift and Docker.
  4. Project site: **https://sarkhandigitech.github.io/sarkhans-claude-starter/**
  5. ## Get it
  6. ### Option 1: Claude Code plugin (Windows, Linux, macOS)
  7. Run these two commands in a terminal, then start Claude Code:
  8. ```bash
  9. claude plugin marketplace add sarkhandigitech/sarkhans-claude-starter
  10. claude plugin install sarkhans-starter@sarkhans-claude-starter
  11. ```
  12. The rules, agents, skills and guardrails then work in every project. Skills are named like `/sarkhans-starter:verify`. [More about the plugin](#claude-code-plugin-windows-linux-macos)
  13. ### Option 2: Mac app
  14. ### [Download Sarkhan’s Claude Starter for Mac](https://github.com/sarkhandigitech/sarkhans-claude-starter/releases/latest/download/Sarkhans-Claude-Starter.dmg)
  15. macOS 13 or newer, Apple Silicon and Intel, always the latest version. [How to install](#install-on-a-mac).
  16. The app adds what the plugin can't: one-click setup for all your projects with the right rules for each stack, a work mode per project, team rules you pick with a click, a weekly report of what the guardrails stopped, and automatic updates.
  17. ## What's inside
  18. - **Guardrails that block**, not just instructions: hooks stop comments in code, invented imports, pushes to main, AI mentions in commits, secret files and unsafe code.
  19. - **Work modes** per project (Lite / Standard / Strict) and a team of specialist agents for bigger work, with reviewers that keep project memory.
  20. - **Guardrail report**: the app shows what the rules stopped this week in each project.
  21. - **Security testing**: `/security-audit` reads the code for holes, `/pentest` attacks your running app on localhost or a staging server you name, proves each hole with a real request and turns it into a regression test. A hook keeps security tools away from every other host. For pull requests there's a ready [GitHub workflow](examples/github) with Anthropic's security review.
  22. - **Modern web know-how**: Google Chrome's [Modern Web Guidance](https://github.com/GoogleChrome/modern-web-guidance) comes with every web project and with the plugin, so Claude looks up current HTML, CSS, accessibility, performance and security practice before writing UI code.
  23. - **Team rules**: share your team's conventions from one folder; choose a default team, or a different team per project. Works in the app and in the plugin.
  24. - Third-eye reports, design lock, database review, kickoff for new projects, and about 2,800 tokens of rules per session.
  25. - What it does and how it works: [`claude-web-starter/README.md`](claude-web-starter/README.md)
  26. - Internals, CLI contract, Windows porting notes: [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md)
  27. ## Requirements
  28. - To use: macOS 13+ and Claude Code with a Claude Pro, Max, Team or Enterprise plan (the free plan doesn't include Claude Code). Claude Code, Node.js and Git can be installed from inside the app.
  29. - To build the app: Xcode Command Line Tools (`xcode-select --install`).
  30. ## Install on a Mac
  31. ### 1. Put the app in Applications
  32. Open the downloaded `Sarkhans-Claude-Starter.dmg` and drag **Sarkhan’s Claude Starter** onto the **Applications** folder.
  33. If your Mac account has no admin rights, drag it into the **Applications** folder inside your home folder instead (Finder → Go → Home; create a folder named `Applications` if it isn't there).
  34. ### 2. Allow it once
  35. The app isn't notarized by Apple (that needs a paid Apple developer account). That's why macOS asks you to confirm it **once**, the first time you open it. Apps from developers who pay Apple for notarization show a simple **Open** button instead.
  36. **macOS 15 Sequoia, macOS 26 Tahoe and macOS 27 Golden Gate (the current version)**
  37. 1. Double-click **Sarkhan’s Claude Starter** in Applications. macOS says the app was not opened. Click **Done**, not Move to Trash.
  38. 2. Open the **Apple menu** → **System Settings** → **Privacy & Security**.
  39. 3. Scroll all the way down to **Security**. Next to the message that the app was blocked to protect your Mac, click **Open Anyway**.
  40. 4. In the next window click **Open Anyway** again and confirm with your password or Touch ID. The app opens.
  41. The **Open Anyway** button appears only after step 1 and stays for about an hour. If you don't see it, do step 1 again.
  42. **macOS 13 Ventura and macOS 14 Sonoma**
  43. Right-click (or Control-click) the app in Applications → **Open** → **Open**.
  44. After this, the app opens normally with a double-click. Updates install themselves from inside the app and don't ask again.
  45. ### 3. Set it up
  46. The app opens a short setup screen:
  47. - **Node.js**, **Git** and **Claude Code**: press the button if one is missing and finish the installer.
  48. - **Projects folder**: choose the folder with your projects.
  49. - **Claude's language**: the language Claude explains things in.
  50. Then select your projects and press **Set up**. **Open in Claude Code** in a project's panel opens Terminal there and starts Claude.
  51. ### Updates
  52. The app checks for new versions when it opens, every 30 minutes, and when you switch back to it. When one is available, an **Update to x.y.z** button appears: it downloads the new version, replaces the app and restarts. If the app's folder needs admin rights, macOS asks for your password. Set-up projects get new rules automatically.
  53. ### For developers: install from Terminal
  54. If you're comfortable with Terminal, this one line installs or reinstalls the latest version without the approval step:
  55. ```bash
  56. curl -fsSL https://raw.githubusercontent.com/sarkhandigitech/sarkhans-claude-starter/main/install.sh | bash
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 77 on GitHub
  57. ```
  58. ## Claude Code plugin (Windows, Linux, macOS)
  59. The rules, agents, skills and guardrails also ship as a Claude Code plugin, for people who don't use the Mac app:
  60. ```bash
  61. claude plugin marketplace add sarkhandigitech/sarkhans-claude-starter
  62. claude plugin install sarkhans-starter@sarkhans-claude-starter
  63. ```
  64. Skills are namespaced (`/sarkhans-starter:verify`). In projects set up with the app, the project's own copy wins and the plugin stays out of the way. The plugin in `plugins/` is generated: run `node scripts/build-plugin.mjs` after changing `claude-web-starter/template`.
  65. ## Team rules
  66. Team rules are your team's own conventions (API style, naming, review habits) that Claude follows next to the starter's rules.
  67. **1. Make the team folder once.** Copy [`examples/team-rules`](examples/team-rules) into a git repository your team shares and edit it:
  68. - `rules/*.md`: one short Markdown file per topic. Claude reads them in every session, so keep them brief.
  69. - `team.json` (optional): `name`, plus defaults for new projects: `preset` (`lite`, `standard`, `strict`), `responseLanguage` and `skills`.
  70. **2. Choose which projects use it.** A computer can know several teams. One of them can be the *default team*: every project uses it unless that project has its own choice (another team, or no team).
  71. | | Mac app | Plugin (any system) | Installer in a terminal |
  72. |---|---|---|---|
  73. | See what is set | Settings → Team rules | `/sarkhans-starter:team` | `node install.mjs --teams` |
  74. | Team for every project | Settings → Team rules → Default team | `/sarkhans-starter:team set-default <folder>` | `node install.mjs --set-team <folder>` |
  75. | Team for one project | Project page → Team | `/sarkhans-starter:team use <folder>` | `node install.mjs <project> --team <folder>` |
  76. | No team in one project | Project page → Team → No team | `/sarkhans-starter:team none` | `node install.mjs <project> --no-team` |
  77. | Back to the default | Project page → Team → Default team | `/sarkhans-starter:team default` | `node install.mjs <project> --default-team` |
  78. In the plugin you can also just describe it, in your own language: `/sarkhans-starter:team use our backend rules in ~/work/backend-team for this project`.
  79. **3. Keep it up to date.** Pull the team repository as usual. The Mac app notices the change and updates the projects by itself. The plugin reads the folder at the start of every Claude Code session. With the installer, run it again for the project with `--force`.
  80. Good to know:
  81. - The choice is saved on your computer (`~/.claude-starter/settings.json`), not in the project, so teammates can keep the team folder wherever they like.
  82. - With the app or the installer, a project gets the rules as `.claude/rules/team-*.md`. The plugin writes nothing into the project and gives Claude the rules when a session starts. After changing the team in the plugin, start a new session or run `/clear`.
  83. - In the plugin, `preset` and `responseLanguage` from `team.json` apply to projects that have no `.claude/hooks/config.json` of their own.
  84. ## Publishing an update
  85. Releases are automatic. Every merge to `main` that changes `claude-web-starter/VERSION` builds the app on GitHub (Actions → **Release**) and publishes it on this repository's Releases page. The download link and everyone's **Update** button then point to it. The app checks for new versions when it opens, every 30 minutes, and when you switch back to it. After an update, set-up projects get the new rules automatically, but only when the rules actually changed. Merges that don't change the version publish nothing.
  86. 1. Make the change on a branch, bump `claude-web-starter/VERSION` (e.g. `4.5.4` → `4.5.5`) and add a `## 4.5.5` section to `CHANGELOG.md`. That section becomes the release notes people see in the app, so write it for users.
  87. 2. Open a pull request and **Merge** it on GitHub.
  88. 3. Wait about 5 minutes. The new version is behind the download link and in everyone's app.
  89. Only the owner and invited collaborators can push. Visitors can read and download, nothing else. Never commit secrets.
  90. To retry a release by hand: Actions → Release → **Run workflow** (it publishes only if that version doesn't exist yet).
  91. ## Building locally (optional)
  92. Needs Xcode Command Line Tools (`xcode-select --install`):
  93. ```bash
  94. UPDATE_REPO=owner/repo ./macos-app/build-app.sh # → dist/Sarkhans-Claude-Starter.dmg + .zip
  95. ./macos-app/build-app.sh --dev # development app that recompiles the Swift source on launch
  96. ```
  97. To skip the "Open Anyway" step for everyone, sign and notarize with an Apple Developer ID (paid Apple Developer account):
  98. ```bash
  99. xcrun notarytool store-credentials claude-starter --apple-id you@company.com --team-id TEAMID
  100. NOTARY_PROFILE=claude-starter ./macos-app/build-app.sh
  101. ```
  102. Without the app:
  103. ```bash
  104. node claude-web-starter/install.mjs ~/path/to/project
  105. node claude-web-starter/install.mjs --help
  106. ```
  107. ## Repository layout
  108. | Folder | Content |
  109. |---|---|
  110. | `claude-web-starter/` | installer (Node), project template, rules, skills, agents, hooks, stack packs, skill catalog |
  111. | `macos-app/` | SwiftUI app source (`Sources/`), launcher, Info.plist, icon, `build-app.sh`, `make-shareable.sh`, `update-repo.txt` |
  112. | `plugins/`, `.claude-plugin/` | the generated Claude Code plugin and its marketplace |
  113. | `scripts/` | `build-plugin.mjs` and the plugin's own files |
  114. | `site/` | the project site (GitHub Pages) |
  115. | `examples/team-rules/` | a team rules folder to copy |
  116. | `examples/github/` | a workflow for Anthropic's security review on every pull request |
  117. | `.github/workflows/` | release when `VERSION` changes on `main`, build check on pull requests, site deploy |
  118. | `docs/` | architecture and porting guide |
  119. ## Contributing
  120. - Every release bumps `claude-web-starter/VERSION` (app and rules share one version number).
  121. - Test hooks with the stdin examples in `docs/ARCHITECTURE.md`.
  122. - Third-party skills from the catalog are downloaded from their own repositories at install time and keep their own licenses; they are not part of this repository.
  123. ## License
  124. [MIT](LICENSE). Privacy: [PRIVACY.md](PRIVACY.md). Security reports: [SECURITY.md](SECURITY.md). Sarkhan’s Claude Starter is an independent project and isn't affiliated with Anthropic.

Ratings and comments

Sign in to rate this skill.

Sign in

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