菜单
This skill should be used when the user asks to "install best practice rules", "set up project rules", "add project rules and commands", "set up project conventions", or scaffold-project reaches the rules step. Installs the proven MACSTACK rule set (.claude/rules) and core commands into a project.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Agents-Store/claude-plugins --skill best-practices命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
This skill should be used when the user reports a problem with macstack-dev or the MACSTACK standard — "this skill did the wrong thing", "the schema is missing a field", "the passport for X is wrong", "send macstack feedback", "improve the schema based on my edit", "fix the macstack plugin" — and the fix must land in the right source (plugin, schema repo, or registry repo).
This skill should be used when the user asks to "set up Infisical for this project", "create .infisical.json", "pull the env keys", "wire the env", "sync secrets", or scaffold-project reaches the env step. Creates .infisical.json, pulls .env.prod/.env.dev, ensures every key from macstack.json resources.accesses exists, and installs the mandatory secrets scripts and commands.
This skill should be used when the user asks to "scaffold the project from macstack.json", "create the project working files", "generate project files from the spec", "build the project from macstack.json", or after a macstack.json is validated and the working tree must be built. Creates project files strictly in the prototype → stack plugins → dev plugins order.
基于 SOC 职业分类
| name | best-practices |
| description | This skill should be used when the user asks to "install best practice rules", "set up project rules", "add project rules and commands", "set up project conventions", or scaffold-project reaches the rules step. Installs the proven MACSTACK rule set (.claude/rules) and core commands into a project. |
Every MACSTACK project ships the same battle-tested .claude/rules/ set and core
commands (proven in a production orchestrator). Install them at scaffold time; adapt
wording to the project, never drop a rule silently.
.claude/rules/Create each file; content = a short version of the rule + the WHY:
safety.md — Never: commit secrets (.env, tokens, .mcp.json with values),
any in TypeScript, display names instead of resource IDs in MCP calls, deleting
production data without confirmation, hardcoded URLs/tokens. Always: validate at
boundaries, handle 401/404/429/500 on external calls, env vars for credentials,
created_at/updated_at on every table, batch endpoints for >10 records.secrets-env-sync.md — Infisical = the source of truth; local .env* are
working copies; changed env → /secrets-push; before a deploy/push →
/env-audit; push is an upsert (never deletes); never commit .env* (see the
infisical-env skill).commit-after-task.md — Conventional Commits (type(scope): summary), small
frequent commits after each finished unit of work; body explains WHAT/WHY;
committing ≠ pushing (pushing is a separate explicit action).search-first.md — Part A: reuse before building (codebase → dependencies →
from scratch); Part B: 2+ failed attempts / unfamiliar API → search official docs
(Context7 → llms.txt → web), do not keep guessing.external-api-docs.md — before writing code against a third-party SDK/API,
verify usage against official docs (an llms.txt map of the stack's services);
training data goes stale.project-conventions.md — naming: TS PascalCase/camelCase/kebab files; DB
snake_case, FK {table}_id, booleans is_*/has_*, timestamps *_at; workflows
[Domain] - [Action] - [Trigger]; kebab API URLs.macstack-sync.md (specific to the standard) — macstack.json is a living
specification: any stack change (new software/workflow/entity/interface) is
accompanied by a macstack.json update + lint in the same commit; the definition
of done includes the spec sync.If the project deploys to a PaaS (dokploy/coolify) — also add deploy-verify.md
(a deploy is done only when the build is done + containers are healthy + logs are
clean + the domain returns 200).
.claude/commands/| Command | What it does |
|---|---|
commit.md | Conventional commit per the commit-after-task rule |
pr.md | Create a PR (body: what/why, work-item link) |
secrets-sync.md, secrets-push.md, env-audit.md, setup-tokens.md | from the infisical-env skill |
update-context.md | update macstack.json + CLAUDE.md + .env.example after stack changes (sync analog) |
macstack-lint.md | run the lint skill |
Ensure CLAUDE.md: (1) has the "Stack Specification" section → macstack.json; (2) lists the rules as MANDATORY, one line each; (3) stays short (<100 lines) — details live in rules/skills/macstack.json, not in CLAUDE.md.