Lw11

.claude/commands/standardize-sections.md

@@ -0,0 +1,36 @@
+---
+description: Analyze and standardize section titles across documentation pages
+---
+
+You are analyzing documentation to identify inconsistent section titles and propose standardization.
+
+## Process
+
+1. **Scan the specified documentation directory** for common section patterns
+2. **Identify variants** of similar sections:
+   - "Common Tasks" vs "Common Use Cases" vs "Use Cases" vs "Using X"
+   - "Getting Started" vs "Quick Start" vs "Starting Out"
+   - "Configuration" vs "Setup" vs "Setting Up"
+3. **Count occurrences** of each variant
+4. **Propose a standard** based on:
+   - Most common usage
+   - Clarity and scannability
+   - Consistency with existing conventions
+5. **Present findings** with:
+   - Current state (all variants found)
+   - Recommended standard
+   - Files that need updating
+   - Example transformations
+
+## Output Format
+
+Provide a structured report:
+- Section name variants found
+- Frequency of each variant
+- Recommended standard title
+- List of files needing updates
+- Risk assessment (breaking changes, link updates needed, etc.)
+
+## Example Usage
+
+When user runs `/standardize-sections docs/prevention`, analyze all prevention docs for section title inconsistencies and propose standardization.

.claude/skills/batch-edit.md

@@ -0,0 +1,49 @@
+# Batch Edit Helper
+
+When you need to make the same type of change across multiple files, this skill helps plan and execute the changes systematically.
+
+## When to Use
+
+- Terminology changes across multiple files
+- Section title standardization
+- Link updates after restructuring
+- Formatting consistency improvements
+
+## Process
+
+1. **Planning Phase**
+   - Use Grep to find all instances
+   - Categorize instances (preserve vs replace)
+   - Identify edge cases
+   - Create todo list with one item per file
+
+2. **Execution Phase**
+   - Read each file before editing
+   - Make replacements systematically
+   - Update todo list after each file
+   - Track progress visibly
+
+3. **Verification Phase**
+   - Use git diff to review changes
+   - Check for unintended replacements
+   - Verify links still work
+   - Commit with detailed message
+
+## Best Practices
+
+- Always use Grep first to understand scope
+- Read files before editing (required by Edit tool)
+- Make one logical change per commit
+- Use todo list to track progress across files
+- Group related changes together
+- Provide detailed commit messages explaining rationale
+
+## Example
+
+User: "Replace all instances of 'foo' with 'bar' in the docs"
+
+1. Grep for 'foo' to see all uses
+2. Categorize: generic foo (replace) vs FooClass (preserve) vs foo() (evaluate)
+3. Create todo list with each file
+4. Execute replacements file by file
+5. Commit with explanation of what was changed and why

.claude/skills/check-terminology.md

@@ -0,0 +1,34 @@
+# Documentation Terminology Consistency Checker
+
+When invoked, analyze documentation for terminology conflicts where the same word is used with different meanings in different contexts.
+
+## Process
+
+1. Identify domain-specific terms that may conflict with product-specific features
+2. Search for all uses of potentially ambiguous terms
+3. Categorize uses into:
+   - Product-specific technical terms (should be preserved)
+   - Generic uses (candidates for replacement)
+   - Contextual uses (need case-by-case evaluation)
+4. Propose alternative terminology with pros/cons
+5. Present findings in a structured format with:
+   - Current usage patterns
+   - Potential confusion points
+   - Recommended alternatives
+   - Implementation strategy (hybrid, wholesale replacement, etc.)
+
+## Example Scenarios
+
+- "Policy" used for both Guardrails Policies and generic security policies
+- "Resource" used for both Guardrails Resources and cloud resources
+- "Control" used for both Guardrails Controls and generic security controls
+- "Rule" used for both specific enforcement rules and generic guidelines
+
+## Output Format
+
+Provide a structured analysis with:
+- Term being analyzed
+- Distinct contexts where it appears
+- Frequency in each context
+- Recommended approach (preserve, replace, hybrid)
+- Specific replacement suggestions with rationale