E
envoydev/claude-kit
Shared Claude Code rules, skills and settings for envoydev's plugin repos, synced into each
更新 2026-11-19
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 0 ★ · envoydev/claude-kit · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-15 · 最近见到 2026-11-20 · 共见到 6 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
envoydev/claude-kit;我们收录于 2026-11-15;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# claude-kit
以下摘录自该仓库的 README(片段)
The Claude Code rules, skills and settings that envoydev's plugin repos share - alfred-code,
alfred-mods and alfred-tools -
kept once here and copied into each repo's .claude/ by a sync script.
It is maintainer tooling: nothing here ships to the people who install the plugins. The plugin catalog itself lives in
plugins-marketplaces.
## What is shared
| Path | What it is |
| shared/.claude/rules/ | auto-run, execution (a template), javascript, typescript, refining-plans, skill-authoring, superpowers-location |
| shared/.claude/skills/ | auto-run, javascript, typescript, ts-js-testing, npm, markdown-style, plugin-packaging, refining-plans, skill-authoring, solve-task (a template), the eight repo-audit- audits |
| shared/settings.base.json | the secret-file deny list, the plugins every repo enables, autoCompactWindow - merged into each repo's .claude/settings.json |
| shared/mcp.json | the MCP servers every repo gets (context7) - merged into each repo's .mcp.json by name, the repo's own servers kept; the file is machine-local and git-ignored, so each machine runs the sync |
A shared file ending in .tmpl is a template: it lands without the suffix, each {{key}} filled from the repo's own
.claude/kit/repo.json (a string, or an array of lines). That is how solve-task and execution.md stay one flow
while each repo names its own checks, commit rule and sibling scope. A key a repo does not define stops its sync before
anything is written. The lock holds the filled file's hash, so a local edit fails kit:check as any other does.
The repo-audit- skills are one generic copy each. What they audit in a repo comes from that repo's repo.json
audit map, one entry per kind (skills, agents, rules, hooks, claude-md, plugins, system, usage):
roots (the paths audited), checks (the commands that are its mechanical gate) and notes (its own registries,
graders and catalogs, one sentence each). A kind with no entry is reported as nothing to audit.
Each repo keeps its own CLAUDE.md, its repo- rules and skills, plugin-handling.md and repo.json: they name
that repo's layout, commands and release path.
## Use
The repos sit beside this one (../alfred-code, ../alfred-mods, ../alfred-tools).
bash
npm run check # what a sync would change in each repo, nothing written; exit 1 on a difference
npm run sync # write the shared files, .claude/kit/lock.json and .claude/kit/check.mjs into each repo
alfred-mods and alfred-tools -
kept once here and copied into each repo's .claude/ by a sync script.
It is maintainer tooling: nothing here ships to the people who install the plugins. The plugin catalog itself lives in
plugins-marketplaces.
## What is shared
| Path | What it is |
| shared/.claude/rules/ | auto-run, execution (a template), javascript, typescript, refining-plans, skill-authoring, superpowers-location |
| shared/.claude/skills/ | auto-run, javascript, typescript, ts-js-testing, npm, markdown-style, plugin-packaging, refining-plans, skill-authoring, solve-task (a template), the eight repo-audit- audits |
| shared/settings.base.json | the secret-file deny list, the plugins every repo enables, autoCompactWindow - merged into each repo's .claude/settings.json |
| shared/mcp.json | the MCP servers every repo gets (context7) - merged into each repo's .mcp.json by name, the repo's own servers kept; the file is machine-local and git-ignored, so each machine runs the sync |
A shared file ending in .tmpl is a template: it lands without the suffix, each {{key}} filled from the repo's own
.claude/kit/repo.json (a string, or an array of lines). That is how solve-task and execution.md stay one flow
while each repo names its own checks, commit rule and sibling scope. A key a repo does not define stops its sync before
anything is written. The lock holds the filled file's hash, so a local edit fails kit:check as any other does.
The repo-audit- skills are one generic copy each. What they audit in a repo comes from that repo's repo.json
audit map, one entry per kind (skills, agents, rules, hooks, claude-md, plugins, system, usage):
roots (the paths audited), checks (the commands that are its mechanical gate) and notes (its own registries,
graders and catalogs, one sentence each). A kind with no entry is reported as nothing to audit.
Each repo keeps its own CLAUDE.md, its repo- rules and skills, plugin-handling.md and repo.json: they name
that repo's layout, commands and release path.
## Use
The repos sit beside this one (../alfred-code, ../alfred-mods, ../alfred-tools).
bash
npm run check # what a sync would change in each repo, nothing written; exit 1 on a difference
npm run sync # write the shared files, .claude/kit/lock.json and .claude/kit/check.mjs into each repo
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/envoydev-claude-kit/)
- 来源
- github · https://github.com/envoydev/claude-kit
- 按领域浏览
- 开源项目
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。