菜单
Manage matter workspaces: new, list, switch, close, or detach to practice-level. Turkish-law adaptation preserves the original matter isolation function while adding client, vekalet, UYAP-if-applicable, mediation, confidentiality, and conflicts-status fields.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | matter-workspace |
| description | Manage matter workspaces: new, list, switch, close, or detach to practice-level. Turkish-law adaptation preserves the original matter isolation function while adding client, vekalet, UYAP-if-applicable, mediation, confidentiality, and conflicts-status fields. |
| argument-hint | <new | list | switch | close | none> [slug] |
Birden fazla müvekkil veya dosyada çalışan kullanıcılar için bağlam izolasyonu sağlar. Bu skill hukuki strateji üretmez; diğer skill'lere hangi dosya bağlamında çalıştıklarını söyler.
/commercial-legal:matter-workspace new <slug> - create a matter workspace./commercial-legal:matter-workspace list - list active and archived matters./commercial-legal:matter-workspace switch <slug> - set active matter./commercial-legal:matter-workspace close <slug> - archive, never delete./commercial-legal:matter-workspace none - detach to practice-level context.Read ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md and confirm ## Matter workspaces.
If disabled, explain that in-house users normally work at practice-level:
Dosya çalışma alanları kapalı. Kurum içi hukuk müşavirliği olarak yapılandırıldığınız için eklenti genel pratik bağlamında çalışır. Birden fazla müvekkil veya şirketle çalışıyorsanız
/commercial-legal:cold-start-interview --redoile özel/pratik ayarını güncelleyin.
Dispatch on $ARGUMENTS.
Show proposed changes and confirm before writing.
~/.claude/plugins/config/claude-for-legal/commercial-legal/
├── CLAUDE.md
└── matters/
├── <slug>/
│ ├── matter.md
│ ├── history.md
│ ├── notes.md
│ └── outputs/
└── _archived/
Keep repo paths in English unless the full plugin has been renamed.
new <slug>matter.md.history.md.notes.md.matter.md Template[WORK-PRODUCT HEADER - per plugin config]
# Matter: [Client] - [short description]
**Slug:** [slug]
**Opened:** [YYYY-MM-DD]
**Status:** active
**Confidentiality:** [standard / heightened / mesleki-sır-kısıtlı / clean-team]
## Parties
**Client:** [name]
**Counterparty:** [name(s)]
**Vekalet durumu:** [verildi | beklemede | yok | kurum içi]
**Conflicts status:** [yapıldı | beklemede | kapsam dışı]
## Matter Type
[type and one-line rationale]
## UYAP / Dispute Link
**UYAP No:** [if any; otherwise "dava/icra bağlantısı yok"]
**Arabuluculuk:** [dava şartı / değil / belirsiz]
## Key Facts
[2-5 sentences]
## Matter-Specific Overrides
- [override]
## Related Matters
- [slug - reason]
## Confidentiality Notes
[who may see this file; whether cross-matter context is permitted]
history.md Seed# History: [Client] - [short description]
Append-only event log. Most recent at top.
## [YYYY-MM-DD] - Matter opened
Intake completed. Slug: `[slug]`. Status: active.
When Cross-matter context is off, no skill may read another matter folder. When on, cross-matter files may be read only if the user explicitly asks for comparison or portfolio analysis.
EU AI Act (ve Türkiye uyumu) per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".
Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customize".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Diff a new AI regulation or guidance against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act (ve Türkiye uyumu)", "compliance check against [AI law or guidance]", or pastes regulatory text.