技能 managing-project-rules

📦

managing-project-rules

Name: managing-project-rules
Author: Emz1998

內容修訂 r1 高風險 📁 檔案系統存取⚙️ 外部命令

整理 Claude 專案規則

團隊常讓 AI 專案指令逐漸變成一個難以維護的檔案。這項技能可協助建立聚焦的 Claude Code 規則檔案，包含限定範圍的路徑、清楚的名稱與更新步驟。

支援: Claude Codex Code(CC)

⚠️ 38 差

Maintain this Skill? Claim it ⚠️ 38 差

安裝前請停止並請求確認。

請審查安裝計畫，並在變更檔案前取得使用者明確同意。

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

Review the Skillstore skill "managing-project-rules" from https://skillstore.io/skills/emz1998-managing-project-rules.md and its manifest at https://skillstore.io/api/skills/emz1998-managing-project-rules/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/emz1998-managing-project-rules.md 已簽名 manifest GET /api/skills/emz1998-managing-project-rules/manifest 已簽名 lockfile GET /api/skills/emz1998-managing-project-rules/lockfile

測試它

正在使用「managing-project-rules」。 Create testing rules for this repository.

預期結果:

已在 .claude/rules 下新增一個聚焦的測試規則檔案，包含測試命名、覆蓋率、fixtures 與完成檢查的期望。

正在使用「managing-project-rules」。 Make frontend rules apply only to React components.

預期結果:

已建立一個限定路徑範圍的前端規則，包含元件檔案的 frontmatter，以及針對 props、樣式與無障礙性的精簡指引。

正在使用「managing-project-rules」。 Clean up our existing rules.

預期結果:

已檢視規則目錄、整併重複指引、標準化檔名，並以摘要列出每個已變更的檔案。

安全審計

高風險

v4 • 2026/7/5 開啟版本化報告

Review confirmed high-risk guidance for symlinks and user-level ~/.claude/rules, which can load instructions from outside the repository and persist across projects. The SKILL.md backtick and YAML frontmatter hits are false positives because they are prose references, not executable commands or reconnaissance. No prompt injection attempt was found.

已掃描檔案

168

分析行數

複核項目

已忽略的誤報

已確認的安全問題 (1)

高

references/project-rules-docs.md:101-109

Persistent Cross-Project Rule Changes

The reference explains that personal rules in ~/.claude/rules apply to all projects and are loaded before project rules. A skill that creates or updates these files could make persistent instruction changes outside the current repository unless it requires explicit approval.

The cited documentation directly states the global rule path and cross-project loading behavior. The risk depends on how the skill uses the reference, but the persistence behavior is explicit.

能力複核項目 (6)

這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。

高

references/project-rules-docs.md:101

Hidden file in home directory

You can create personal rules that apply to all your projects in `~/.claude/rules/`:

The reference describes creating rules in ~/.claude/rules that apply across projects, which can persist AI behavior outside the current workspace. This is documentation rather than direct execution, so confidence is high but not absolute.

高

references/project-rules-docs.md:104

Hidden file in home directory

~/.claude/rules/

The listed ~/.claude/rules path is a hidden home-directory location used for global rule loading. Editing it can affect future sessions and projects beyond the user-visible project scope.

高

references/project-rules-docs.md:91

Symlink creation

ln -s ~/shared-claude-rules .claude/rules/shared

The ln -s example links a home-directory rules folder into .claude/rules. That can cause rule loading from outside the repository and can bypass normal project-boundary review.

高

references/project-rules-docs.md:94

Symlink creation

ln -s ~/company-standards/security.md .claude/rules/security.md

The command links an external home-directory file into project rules, making outside content part of Claude memory. This can unexpectedly load sensitive or unreviewed instructions.

中

references/project-rules-docs.md:101

Hidden file access

You can create personal rules that apply to all your projects in `~/.claude/rules/`:

The guidance points to ~/.claude/rules as a place for personal rules, which is hidden filesystem access with cross-project impact. It is legitimate Claude configuration but still a real persistence risk.

中

references/project-rules-docs.md:104

Hidden file access

~/.claude/rules/

The explicit ~/.claude/rules directory reference can lead an agent to inspect or modify hidden user-level configuration. The risk is contextual but real because those files influence future Claude behavior.

風險因素

📁 檔案系統存取 (6)

references/project-rules-docs.md:101 references/project-rules-docs.md:104 references/project-rules-docs.md:101 references/project-rules-docs.md:104 references/project-rules-docs.md:91 references/project-rules-docs.md:94

⚙️ 外部命令 (5)

SKILL.md:6 SKILL.md:14 SKILL.md:15 SKILL.md:30 SKILL.md:45

審計單位: codex 檢視審計紀錄 →

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/emz1998-managing-project-rules/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/emz1998-managing-project-rules/security.svg)](https://skillstore.io/skills/emz1998-managing-project-rules?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/emz1998-managing-project-rules?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emz1998-managing-project-rules/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/emz1998-managing-project-rules.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

學術引用 (APA · BibTeX · CFF)

APA 引用

Emz1998. (2026). managing-project-rules security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emz1998-managing-project-rules/audits/4

BibTeX 引用

@techreport{emz1998-emz1998-managing-project-rules-2026,
  author = {Emz1998},
  title = {managing-project-rules security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/emz1998-managing-project-rules/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "managing-project-rules security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "Emz1998"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/emz1998-managing-project-rules/audits/4"
identifiers:
  - type: other
    value: "skillstore:emz1998-managing-project-rules:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

建立團隊編碼標準

將分散的團隊偏好轉換為聚焦的規則檔案，涵蓋風格、測試、安全性與審查期望。

將規則限定到檔案路徑

加入 frontmatter，讓 API、前端或測試規則只在 Claude Code 處理相符路徑時套用。

改進現有規則集

更新現有 .claude/rules 檔案，同時保留有用段落、移除重複內容並改善檔名。

試試這些提示

建立基本規則

Create a Claude Code project rule for our testing expectations. Keep it focused, use a descriptive filename, and place it in .claude/rules.

更新現有規則

Review the existing .claude/rules files and update the coding style guidance. Preserve useful content, remove duplicates, and summarize every change.

加入路徑特定指引

Create path-specific Claude Code rules for files under src/api. Include frontmatter, API validation expectations, and a concise completion summary.

重整規則庫

Audit our .claude/rules directory, propose a topic-based structure, then update the files after approval. Keep one topic per file and avoid global rule changes.