菜单
Check your CLAUDE.md for completeness and issues. Identifies missing sections, stale references, and gaps that might bite you later.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | validate |
| description | Check your CLAUDE.md for completeness and issues. Identifies missing sections, stale references, and gaps that might bite you later. |
| allowed-tools | Read, Glob, Grep |
/scs-vibe:validate. Never auto-invoke based on project state or conversation context.You are validating the user's structured context (CLAUDE.md) for completeness, accuracy, and usefulness.
Critical (warn if missing):
Recommended (suggest if missing):
Check for generic/placeholder content:
Check for specificity:
Verify referenced files/directories exist:
Check for outdated patterns:
If healthcare template detected:
If fintech template detected:
Provide a clear report:
## SCS Context Validation Report
### Summary
- Overall Status: [Good / Needs Work / Critical Issues]
- CLAUDE.md Location: [path]
- Last Modified: [if detectable]
### Critical Issues
[List any critical problems that should be fixed immediately]
### Warnings
[List issues that should be addressed]
### Suggestions
[List nice-to-have improvements]
### What's Good
[Acknowledge what's working well]
### Recommended Actions
1. [Most important fix]
2. [Second priority]
3. [Third priority]
User: /scs-vibe:validate
You: "Let me check your context..."
[Read CLAUDE.md and scan project]
You:
## Context Check
### Status: Needs Work
- Location: ./CLAUDE.md
- Lines: 45
### Issues
1. **No Constraints section** - Claude won't know the boundaries
2. **Vague tech stack** - Says "PostgreSQL" but not how it's accessed
### Suggestions
1. Add "Patterns We Avoid" - stops Claude from repeating mistakes
2. `/src/api` is mentioned but doesn't exist (stale?)
### What's Good
- Clear system overview
- Specific file paths for key components
### Quick Fixes
1. Add 2-3 constraints Claude should respect
2. Be specific: "PostgreSQL 15 via Prisma ORM"
3. Remove or fix the /src/api reference
Want me to help fix any of these?
Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.
Conversational drafting for a specific concern area when documentation doesn't exist. Ask targeted questions and generate draft SCDs.
Initialize structured context for this project. Scaffolds .scs/ with all 11 concern bundles, scans the project, and recommends where to start.
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concerns, and compilation sync status.
Add known compliance or regulatory standards (HIPAA, SOC2, PCI, CHAI, GDPR) to your project context. Copies pre-built standards SCDs from the plugin's standards library.
Check structure and surface issues for human review. Validates YAML, references, concern coverage, and compilation status.