From straion
Validates code, specifications, and tasks against project rules using Straion's semantic matching. Use when checking compliance, validating PRs, reviewing specs against rules, or when user asks "does this meet rules", "check compliance", "validate this".
How this skill is triggered — by the user, by Claude, or both
Slash command
/straion:validating-rulesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Receive description of what to validate (spec, task, or code)
straion find-rules — see ../shared/STRAION_CLI.md| Level | What | Check Against |
|---|---|---|
| Spec | PRDs, ADRs, RFCs | Architecture, security, design principles |
| Task | Implementation tasks | Technical rules, API contracts, testing |
| Code | Actual changes | Coding standards, security, performance |
For each rule returned by the CLI:
## Rules Validation Report
### Summary
[X rules checked, Y compliant, Z issues]
### Compliant ✅
- **RULE-123**: [Rule summary] — ✅ [What was done correctly]
### Partial Compliance ⚠️
- **RULE-456**: [Rule summary] — ⚠️ [What's missing]
- **Recommendation**: [Specific fix]
### Violations ❌
- **RULE-789**: [Rule summary] — ❌ [The violation]
- **Risk**: [Impact]
- **Fix**: [Concrete solution]
When violations are found:
npx claudepluginhub straion-dev/straion-claude-marketplace --plugin straionVerifies Claude Code adherence to project instruction rules via conformance checks on codebase structure, imports, configs or session history analysis with alignkit.
Enforces AI-First SDLC compliance rules including zero technical debt policy, 10 mandatory logging points, and standardized workflows. Use for code quality checks, architecture validation, or compliance decisions.