ima-claude 2.20.0 → 2.26.0

package/plugins/ima-claude/skills/discourse-admin/SKILL.md

@@ -5,37 +5,22 @@ description: "Discourse admin API for site settings, configuration export/import
 
 # Discourse Admin API
 
-Manage Discourse site configuration programmatically via the REST API. Export settings, apply environment configs, manage groups and user fields — without clicking through the admin UI.
+Manage Discourse site configuration via REST API. Export settings, apply environment configs, manage groups/user fields without clicking through admin UI.
 
-## When to Use This Skill
+**Not this skill**: For Discourse plugin development (Ruby/Rails/Ember), use `discourse` skill.
 
-- Exporting or importing Discourse site settings
-- Deploying configuration to staging or production environments
-- Bulk-updating site settings via API
-- Managing groups, categories, or custom user fields programmatically
-- Config-as-code workflows for Discourse
+## Setup
 
-**Not this skill**: For Discourse *plugin development* (Ruby/Rails/Ember), use the `discourse` skill instead.
-
-## Quick Start
-
-**Prerequisites**: Configure environments in `~/.claude/discourse-environments.json`:
+Configure `~/.claude/discourse-environments.json`:
 ```json
 {
-  "local": {
-    "url": "http://localhost:4200",
-    "api_key": "your-local-api-key",
-    "api_username": "system"
-  },
-  "staging": {
-    "url": "https://staging.community.example.com",
-    "api_key": "staging-key",
-    "api_username": "system"
-  }
+  "local": { "url": "http://localhost:4200", "api_key": "...", "api_username": "system" },
+  "staging": { "url": "https://staging.community.example.com", "api_key": "...", "api_username": "system" }
 }
 ```
 
-**Run commands**:
+## Commands
+
 ```bash
 python3 ~/.claude/skills/discourse-admin/scripts/discourse-admin.py export
 python3 ~/.claude/skills/discourse-admin/scripts/discourse-admin.py import base.json staging-overlay.json
@@ -45,85 +30,48 @@ python3 ~/.claude/skills/discourse-admin/scripts/discourse-admin.py set disable_
 python3 ~/.claude/skills/discourse-admin/scripts/discourse-admin.py envs
 ```
 
-## Environment Resolution
+## Environment Resolution (priority order)
 
-Resolved via priority chain (same pattern as `wp-local`):
-
-1. `--env` flag on command line
-2. `$DISCOURSE_ENV` environment variable
+1. `--env` flag
+2. `$DISCOURSE_ENV` env var
 3. `.discourse-env` file in project root or parents
 4. Falls back to `"local"`
 
 ```bash
-# Explicit env
 python3 discourse-admin.py --env staging export
-
-# Env var (set in Kitty terminal config)
-export DISCOURSE_ENV=staging
-python3 discourse-admin.py export
-
-# Project file
-echo "staging" > .discourse-env
-python3 discourse-admin.py export
 ```
 
-**Credentials** stored in `~/.claude/discourse-environments.json` (not in repo, not in env vars).
-API keys are managed at `/admin/api/keys` in each Discourse instance.
-
 ## Config-as-Code Workflow
 
-### Step 1: Export Non-Default Settings
-
 ```bash
+# 1. Export non-default settings (~50-100 settings, not 500+)
 python3 discourse-admin.py export discourse-base.json
-```
 
-Exports only settings where value differs from default — typically 50-100 settings, not 500+.
+# 2. Structure overlays:
+#   config/discourse-base.json
+#   config/discourse-staging.json
+#   config/discourse-production.json
 
-### Step 2: Create Environment Overlays
+# 3. Preview changes
+python3 discourse-admin.py --env staging import base.json staging.json --dry-run
+python3 discourse-admin.py --env staging diff base.json
 
-```
-config/
-  discourse-base.json          # Non-default settings from local
-  discourse-staging.json       # Staging overrides
-  discourse-production.json    # Production overrides
+# 4. Apply
+python3 discourse-admin.py --env staging import discourse-base.json discourse-staging.json
 ```
 
-**Staging overlay example** (`discourse-staging.json`):
+Staging overlay example:
 ```json
 {
   "title": "[STAGING] Community Forum",
-  "site_description": "Staging environment — do not use for real discussions",
   "disable_emails": "yes",
   "notification_email": "noreply-staging@example.com",
   "discourse_connect_provider_secrets": "staging.example.com|staging-secret-here"
 }
 ```
 
-### Step 3: Preview Changes (Dry Run)
-
-```bash
-# Show what would change
-python3 discourse-admin.py --env staging import base.json staging.json --dry-run
-
-# Compare remote vs desired
-python3 discourse-admin.py --env staging diff base.json
-```
-
-### Step 4: Apply Config
-
-```bash
-python3 discourse-admin.py --env staging import discourse-base.json discourse-staging.json
-```
-
-Uses bulk_update endpoint (single request). Falls back to individual updates if bulk fails.
-
 ## Site Settings API
 
-The primary endpoint for config-as-code. ~500+ settings covering email, SSO, branding, security, etc.
-
-### Key Endpoints
-
 | Method | Path | Purpose |
 |--------|------|---------|
 | GET | `/admin/site_settings.json` | List all settings |
@@ -131,51 +79,44 @@ The primary endpoint for config-as-code. ~500+ settings covering email, SSO, bra
 | PUT | `/admin/site_settings/{name}.json` | Update single setting |
 | PUT | `/admin/site_settings/bulk_update.json` | Update multiple (undocumented, source-verified) |
 
-**Setting categories:** `required`, `basic`, `users`, `email`, `login`, `security`, `onboarding`, `spam`, `rate_limits`, `developer`, `embedding`, `legal`, `branding`, `uncategorized`
-
-## When to Load Reference Files
-
-### Full API Reference
-**File**: `references/api-endpoints.md`
-**Load when**: You need exact parameters, response formats, or edge cases for any admin endpoint (groups, categories, users, user fields, site texts, API keys).
-
-### Known Gotchas
-**File**: `references/gotchas.md`
-**Load when**: Hitting unexpected behavior, 404s, or working with a specific Discourse version. Contains breaking changes across versions and endpoint migration history.
-
-### Staging Defaults
-**File**: `references/staging-defaults.md`
-**Load when**: Setting up a new staging environment. Contains recommended safe defaults and a pre-deploy checklist.
+Categories: `required`, `basic`, `users`, `email`, `login`, `security`, `onboarding`, `spam`, `rate_limits`, `developer`, `embedding`, `legal`, `branding`, `uncategorized`
 
 ## Common Staging Settings
 
-| Setting | Staging Value | Why |
-|---------|--------------|-----|
-| `disable_emails` | `yes` | Prevent sending real emails |
+| Setting | Value | Why |
+|---------|-------|-----|
+| `disable_emails` | `yes` | Prevent real emails |
 | `title` | `[STAGING] ...` | Visual distinction |
 | `notification_email` | staging address | Don't spam real inbox |
-| `discourse_connect_provider_secrets` | staging domains | SSO only for staging WP sites |
-| `enable_local_logins` | `true` | Allow direct login for testing |
+| `discourse_connect_provider_secrets` | staging domains | SSO for staging only |
+| `enable_local_logins` | `true` | Direct login for testing |
 | `min_password_length` | `6` | Easier test accounts |
 | `invite_only` | `true` | Prevent public signups |
 
 ## Rate Limiting
 
-- Admin API rate limits are site-setting driven (not hardcoded)
 - Two independent limiters: IP-based (`max_reqs_per_ip_mode`) and API-key-based (`max_admin_api_reqs_per_minute`, default 60)
-- max=0 means BLOCK ALL (not unlimited) — use high numbers like 6000
-- Must flush Redis rate limit keys after changing rate limit config
+- `max=0` means BLOCK ALL (not unlimited) — use high numbers like 6000
+- Flush Redis rate limit keys after changing rate limit config
+
+## Reference Files
 
-## Quick Reference (Manual curl)
+| File | Load When |
+|------|-----------|
+| `references/api-endpoints.md` | Need exact params, response formats, or edge cases (groups, categories, users, user fields, site texts, API keys) |
+| `references/gotchas.md` | Hitting 404s, unexpected behavior, or working with specific Discourse versions |
+| `references/staging-defaults.md` | Setting up new staging environment |
+
+## Quick Reference (curl)
 
 ```bash
 # List all settings
 curl -s -H "Api-Key: $KEY" -H "Api-Username: system" "$URL/admin/site_settings.json"
 
-# Get email settings only
+# Get email settings
 curl -s -H "Api-Key: $KEY" -H "Api-Username: system" "$URL/admin/site_settings/category/email.json"
 
-# Update a single setting
+# Update single setting
 curl -s -X PUT -H "Api-Key: $KEY" -H "Api-Username: system" \
   -H "Content-Type: application/json" \
   -d '{"disable_emails": "yes"}' \
@@ -186,7 +127,4 @@ curl -s -H "Api-Key: $KEY" -H "Api-Username: system" "$URL/groups.json"
 
 # List custom user fields
 curl -s -H "Api-Key: $KEY" -H "Api-Username: system" "$URL/admin/config/user_fields.json"
-
-# List categories
-curl -s -H "Api-Key: $KEY" -H "Api-Username: system" "$URL/categories.json"
 ```

package/plugins/ima-claude/skills/docs-organize/SKILL.md

@@ -5,250 +5,110 @@ description: "Three-tier documentation organization system - Active (permanent)
 
 # Documentation Organization System
 
-A structured approach to documentation organization that separates permanent, historical, and ephemeral content with clear navigation and lifecycle management.
+Three-tier structure separating permanent, historical, and ephemeral content.
 
-## When to Use This Skill
+## Tiers
 
-- Starting a new project and setting up documentation structure
-- Reorganizing existing scattered documentation files
-- Need clear separation between active docs and historical reference
-- Want local-only working documents that won't clutter git
-- Improving documentation discoverability and navigation
-- Establishing documentation standards for a team
-
-## Core Philosophy
-
-**Three-Tier Documentation**:
-- **Active**: Current, permanent documentation used daily (committed to git)
-- **Archive**: Historical reference, completed phases, deprecated patterns (committed to git)
-- **Transient**: Ephemeral working documents, investigation logs, spike results (git-ignored)
-
-**Key Principles**:
-- **Clear Lifecycle**: Documents flow from transient → active → archive
-- **Theme Organization**: Group by function (architecture, development, integrations, features, operations)
-- **Navigation First**: README files at every level for discoverability
-- **Minimal Clutter**: Root directory stays clean, no scattered MD files
+| Tier | Purpose | Git |
+|------|---------|-----|
+| **Active** | Current docs used daily | committed |
+| **Archive** | Historical reference, completed phases | committed |
+| **Transient** | Working docs, spikes, investigation logs | git-ignored |
 
 ## Folder Structure
 
 ```
 docs/
 ├── README.md                          # Central navigation hub
-├── active/                            # Current permanent documentation
-│   ├── README.md                      # Active docs overview
+├── active/
+│   ├── README.md
 │   ├── architecture/                  # System design, plugins, dependencies
-│   │   └── README.md
 │   ├── development/                   # Testing, code standards, patterns
-│   │   ├── README.md
-│   │   └── testing-guides/            # Phase-specific test suites
-│   ├── integrations/                  # Third-party system connections
-│   │   ├── README.md
-│   │   └── [integration-name]/        # Per-integration documentation
-│   ├── features/                      # Feature-specific documentation
-│   │   └── [feature-name]/            # Per-feature documentation
+│   │   └── testing-guides/
+│   ├── integrations/                  # Third-party connections
+│   │   └── [integration-name]/
+│   ├── features/
+│   │   └── [feature-name]/
 │   ├── operations/                    # Security, troubleshooting, deployment
-│   │   └── README.md
 │   └── reference/                     # Templates, quick commands, standards
-│       └── README.md
-├── archive/                           # Historical documentation
-│   ├── README.md                      # Archive overview & browsing guide
-│   └── [YYYY-phase-name]/             # Completed phases/milestones
+├── archive/
+│   ├── README.md
+│   └── [YYYY-phase-name]/
 │       └── README.md                  # Phase summary with outcomes
-└── transient/                         # Ephemeral working documents
-    ├── .gitignore                     # Excludes *.md from git
-    └── README.md                      # Transient usage guide
+└── transient/
+    ├── .gitignore                     # Excludes *.md (keeps README.md)
+    └── README.md
 ```
 
-## Implementation Guide
-
-### Step 1: Create Folder Structure
+## Setup
 
 ```bash
-# Create main structure
 mkdir -p docs/{active,archive,transient}
-
-# Create active subdirectories
 mkdir -p docs/active/{architecture,development,integrations,features,operations,reference}
 mkdir -p docs/active/development/testing-guides
-
-# Create .gitignore for transient
-echo '# Exclude all markdown files in transient/
-*.md
+echo '*.md
 !README.md' > docs/transient/.gitignore
 ```
 
-### Step 2: Create Navigation Hub (docs/README.md)
-
-Use template: [`templates/docs-README.md`](templates/docs-README.md)
-
-Customize the Quick Navigation table for your project's key files.
-
-### Step 3: Create Active Section README (docs/active/README.md)
+Templates: [`templates/docs-README.md`](templates/docs-README.md) · [`templates/active-README.md`](templates/active-README.md) · [`templates/archive-README.md`](templates/archive-README.md) · [`templates/phase-archive-README.md`](templates/phase-archive-README.md) · [`templates/transient-README.md`](templates/transient-README.md) · [`templates/section-README.md`](templates/section-README.md)
 
-Use template: [`templates/active-README.md`](templates/active-README.md)
+## Document Lifecycle
 
-### Step 4: Create Archive README (docs/archive/README.md)
-
-Use template: [`templates/archive-README.md`](templates/archive-README.md)
-
-For completed phases, use: [`templates/phase-archive-README.md`](templates/phase-archive-README.md)
-
-### Step 5: Create Transient README and .gitignore
-
-- **docs/transient/README.md**: Use [`templates/transient-README.md`](templates/transient-README.md)
-- **docs/transient/.gitignore**: Use [`templates/transient-gitignore`](templates/transient-gitignore)
+```
+TRANSIENT ──▶ ACTIVE ──▶ ARCHIVE
+git-ignored    committed   committed
+```
 
-### Step 6: Create Section READMEs
+**Transient → Active**: planning becomes guide, investigation becomes troubleshooting doc, spike becomes ADR
 
-For each `active/` subdirectory, use: [`templates/section-README.md`](templates/section-README.md)
+**Active → Archive**: phase complete, feature deprecated, pattern replaced
 
-## Document Lifecycle Workflow
+**Direct to Archive**: completed work docs, phase summaries, historical reviews
 
-```
-┌─────────────┐     ┌─────────────┐     ┌─────────────┐
-│  TRANSIENT  │ ──▶ │   ACTIVE    │ ──▶ │   ARCHIVE   │
-│             │     │             │     │             │
-│ • Planning  │     │ • Stable    │     │ • Complete  │
-│ • Research  │     │ • Reference │     │ • Historical│
-│ • Spikes    │     │ • Standards │     │ • Deprecated│
-└─────────────┘     └─────────────┘     └─────────────┘
-   git-ignored        committed           committed
-```
+## Theme Categories
 
-### Lifecycle Triggers
-
-**Transient → Active**:
-- Planning becomes implementation guide
-- Investigation findings become troubleshooting docs
-- Spike results become architecture decisions
-
-**Active → Archive**:
-- Phase/milestone completed
-- Feature deprecated with replacement
-- Pattern replaced with better approach
-
-**Direct to Archive** (skip transient):
-- Completed work documentation
-- Phase summaries with outcomes
-- Historical code reviews
-
-## Theme Categories Reference
-
-### `architecture/`
-- Plugin/module architecture
-- Dependency management
-- System design decisions
-- Refactoring roadmaps
-
-### `development/`
-- Testing infrastructure (PHPUnit, Jest, etc.)
-- Code examples and patterns
-- Development standards
-- Template patterns
-
-### `integrations/`
-- Third-party API connections
-- Webhook handling
-- Data sync patterns
-- Authentication flows
-
-### `features/`
-- Feature-specific documentation
-- User workflows
-- Configuration options
-- Feature flags
-
-### `operations/`
-- Security best practices
-- Troubleshooting guides
-- Deployment procedures
-- Monitoring setup
-
-### `reference/`
-- Quick command cheatsheets
-- Template files
-- Brand/style guidelines
-- Onboarding materials
+| Dir | Content |
+|-----|---------|
+| `architecture/` | Plugin/module architecture, system design, refactoring roadmaps |
+| `development/` | Testing infrastructure, code examples, standards |
+| `integrations/` | Third-party APIs, webhooks, auth flows |
+| `features/` | Feature docs, user workflows, config options |
+| `operations/` | Security, troubleshooting, deployment, monitoring |
+| `reference/` | Cheatsheets, templates, brand guidelines, onboarding |
 
 ## Quality Gates
 
-Before adding documentation, verify:
-
-1. ✅ **Correct Location**: Active vs. Archive vs. Transient
-2. ✅ **Theme Match**: Right subdirectory for the content
-3. ✅ **Navigation Updated**: README links added
-4. ✅ **Cross-References**: Related docs linked
-5. ✅ **Date Included**: "Last Updated" at bottom
-6. ✅ **Naming Convention**: UPPER_SNAKE_CASE.md or lowercase-kebab/
+1. Correct tier: Active vs. Archive vs. Transient
+2. Right subdirectory for content theme
+3. README links updated
+4. Related docs cross-referenced
+5. Naming convention: `UPPER_SNAKE_CASE.md` or `lowercase-kebab/`
 
 ## Migration Checklist
 
-When applying this pattern to existing projects:
-
-- [ ] Create folder structure with `mkdir -p` commands
-- [ ] Create `.gitignore` in transient/
-- [ ] Create hub README at `docs/README.md`
-- [ ] Create section READMEs in each active/ subdirectory
-- [ ] Create archive README with naming conventions
-- [ ] Create transient README with workflow guidance
-- [ ] Move existing documentation to appropriate locations
+- [ ] Create folder structure
+- [ ] Create `transient/.gitignore`
+- [ ] Create `docs/README.md` navigation hub
+- [ ] Create section READMEs in each `active/` subdirectory
+- [ ] Move existing docs to correct locations
 - [ ] Update project CLAUDE.md/README.md references
-- [ ] Verify all internal links work
+- [ ] Verify all internal links
 - [ ] Clean up root-level scattered MD files
 
-## Integration with Project Files
-
-### Update Root CLAUDE.md
-
-Add documentation hub reference:
-```markdown
-**📚 Key Documentation:**
-- **[📖 Documentation Index](docs/README.md)** - Central hub for all documentation
-- [Testing Guide](docs/active/development/testing-guides/) - Test setup
-- [Architecture](docs/active/architecture/) - System design
-```
-
-### Update Navigation References
-
-Change scattered references from:
-```markdown
-[Testing](TESTING.md)
-[Security](docs/SECURITY_GUIDE.md)
-```
+## Root CLAUDE.md Reference
 
-To centralized structure:
 ```markdown
-[Testing](docs/active/development/testing-guides/TESTING.md)
-[Security](docs/active/operations/SECURITY_GUIDE.md)
+**Key Documentation:**
+- [Documentation Index](docs/README.md) - Central hub
+- [Testing](docs/active/development/testing-guides/)
+- [Architecture](docs/active/architecture/)
 ```
 
-## Success Metrics
-
-Documentation organization is successful when:
-
-- **Discoverability**: New team members find docs within 2 clicks from hub
-- **Cleanliness**: Root directory has no scattered MD files
-- **Currency**: Active docs are up-to-date with implementation
-- **Lifecycle**: Clear workflow from planning to archive
-- **Navigation**: README at every level provides guidance
-
-## Anti-Patterns to Avoid
-
-❌ **Scattered root files**: MD files in project root instead of /docs/
-❌ **Flat structure**: All docs in single /docs/ folder without themes
-❌ **Missing READMEs**: Subdirectories without navigation guides
-❌ **Broken links**: References to moved/deleted files
-❌ **Stale transient**: Investigation logs never cleaned up
-❌ **Over-archiving**: Active docs moved to archive prematurely
-❌ **Under-archiving**: Completed phase docs never archived
-
-## Related Patterns
-
-- **CLAUDE.md**: Project-level quick reference (references this structure)
-- **ADR (Architecture Decision Records)**: Can live in `active/architecture/adr/`
-- **Changelogs**: Can live in `active/reference/CHANGELOG.md`
-- **API Documentation**: Can live in `active/reference/api/`
-
----
+## Anti-Patterns
 
-**Last Updated**: 2025-01-20
+- Scattered MD files in project root
+- Flat `/docs/` with no theme subdirs
+- Subdirectories without README navigation
+- Stale transient docs never cleaned up
+- Active docs archived prematurely
+- Completed phase docs never archived