ima-claude 2.20.0 → 2.26.0

package/plugins/ima-claude/skills/mcp-vestige/SKILL.md

@@ -5,19 +5,19 @@ description: "Cognitive memory engine with semantic search, spaced repetition, a
 
 # Vestige MCP - Cognitive Memory Engine
 
-**Replaces Memory MCP.** Vestige is a Rust-based cognitive memory system with FSRS-6 spaced repetition, semantic search, prediction error gating, and codebase awareness.
+Rust-based cognitive memory system with FSRS-6 spaced repetition, semantic search, prediction error gating, and codebase awareness. Replaces Memory MCP.
 
-## Architecture (3-Tier Memory)
+## 3-Tier Memory Architecture
 
-| System | Role | Lifecycle | Example |
-|--------|------|-----------|---------|
-| **Vestige** | Neural memory — decisions, preferences, patterns, bugs, learnings | Fades if unused (FSRS-6 decay) | "We chose JWT over sessions because..." |
-| **Qdrant** | Permanent library — reference material, standards, PRDs, architecture docs | Persistent forever | "Our payment system uses Accept.js with ARB" |
-| **Serena Memory** | Project workbench — session state, task progress | Project-scoped, survives git ops | "Currently on task 3/5, next: write tests" |
+| System | Role | Lifecycle |
+|--------|------|-----------|
+| **Vestige** | Neural memory — decisions, preferences, patterns, bugs | Fades if unused (FSRS-6 decay) |
+| **Qdrant** | Permanent library — standards, PRDs, architecture docs | Persistent forever |
+| **Serena Memory** | Project workbench — session state, task progress | Project-scoped |
 
 ## Session Start Protocol (REQUIRED)
 
-At session start, BEFORE asking questions:
+Run BEFORE asking questions:
 
 ```
 mcp__vestige__search query: "{project-name}" limit: 5
@@ -25,14 +25,11 @@ mcp__vestige__search query: "user-eric preferences" limit: 5
 mcp__vestige__intention action: "check"
 ```
 
-If working in a Serena-activated project, also check:
-```
-mcp__serena__list_memories
-```
+If Serena-activated project, also run `mcp__serena__list_memories`.
 
 ## Core Tools
 
-### Search (Your Most-Used Tool)
+### search
 
 ```
 mcp__vestige__search
@@ -40,9 +37,9 @@ mcp__vestige__search
   limit: 5
 ```
 
-Hybrid search — keyword + semantic + RRF fusion. Returns ranked results with similarity scores.
+Hybrid keyword + semantic + RRF fusion. Your most-used tool.
 
-### Smart Ingest (Intelligent Storage)
+### smart_ingest
 
 ```
 mcp__vestige__smart_ingest
@@ -50,17 +47,17 @@ mcp__vestige__smart_ingest
   node_type: "decision"
 ```
 
-Automatically handles CREATE/UPDATE/SUPERSEDE based on similarity thresholds:
+Auto-handles CREATE/UPDATE/SUPERSEDE:
 
-| Similarity | Action | Meaning |
-|------------|--------|---------|
-| >92% | REINFORCE | Near-duplicate — strengthen existing memory |
-| 75-92% | UPDATE | Related — merge new info into existing |
-| <75% | CREATE | Novel — store as new memory |
+| Similarity | Action |
+|------------|--------|
+| >92% | REINFORCE — strengthen existing |
+| 75-92% | UPDATE — merge into existing |
+| <75% | CREATE — new memory |
 
-**Always prefer `smart_ingest` over `ingest`** — it prevents duplicates and maintains coherence.
+Prefer `smart_ingest` over `ingest` — prevents duplicates.
 
-### Direct Ingest (When You Need Control)
+### ingest
 
 ```
 mcp__vestige__ingest
@@ -68,9 +65,9 @@ mcp__vestige__ingest
   node_type: "preference"
 ```
 
-Bypasses dedup logic. Use only when you specifically want to force a new entry.
+Bypasses dedup. Use only when forcing a new entry.
 
-### Memory (Retrieve/Remove/Check)
+### memory
 
 ```
 mcp__vestige__memory
@@ -80,7 +77,7 @@ mcp__vestige__memory
 
 Actions: `get`, `remove`, `check_state`
 
-## Codebase Tools
+### codebase
 
 ```
 mcp__vestige__codebase
@@ -88,20 +85,18 @@ mcp__vestige__codebase
   pattern_type: "architecture"
 ```
 
-Store codebase patterns and architectural decisions. Pattern types: `architecture`, `pattern`, `convention`, `dependency`.
+Pattern types: `architecture`, `pattern`, `convention`, `dependency`
 
-## Feedback Tools
+### Feedback
 
 ```
 mcp__vestige__promote_memory id: "{memory-id}"
 mcp__vestige__demote_memory id: "{memory-id}"
 ```
 
-Strengthen or weaken memories based on relevance. Use when:
-- **Promote**: Memory proved useful, user referenced it, decision confirmed
-- **Demote**: Memory outdated, user contradicted it, no longer relevant
+Promote when memory proved useful. Demote when outdated or contradicted.
 
-## Intention Tools
+### intention
 
 ```
 mcp__vestige__intention
@@ -112,66 +107,48 @@ mcp__vestige__intention
 
 Actions: `set`, `check`, `complete`, `cancel`
 
-Set reminders and future triggers that surface automatically at session start.
-
-## Session & Maintenance Tools
+## Maintenance Tools
 
 | Tool | Purpose |
 |------|---------|
-| `session_checkpoint` | Batch-save an entire session's work |
+| `session_checkpoint` | Batch-save entire session |
 | `find_duplicates` | Detect and merge redundant memories |
 | `consolidate` | Run FSRS-6 decay and maintenance |
-| `importance_score` | 4-channel scoring (novelty, arousal, reward, attention) |
-| `memory_timeline` | Browse memories chronologically |
-| `health_check` | System health with warnings |
+| `memory_timeline` | Browse chronologically |
+| `health_check` | System health warnings |
 
-## Proactive Behavior Rules
+## Proactive Behavior (MUST, not suggestions)
 
-**These are MUST behaviors, not suggestions:**
-
-### 1. Session Start: Search for Context
-When beginning work on any project, **automatically search** for relevant context:
-```
-mcp__vestige__search query: "{project-name}"
-mcp__vestige__search query: "user-eric"
-mcp__vestige__intention action: "check"
-```
-
-### 2. During Work: Store Decisions As They Happen
-When ANY of these occur, **immediately store without being asked**:
+### Store immediately — no prompting needed
 
 | Event | Action |
 |-------|--------|
-| User states a preference | `smart_ingest` with node_type: "preference" |
-| Architectural decision made | `smart_ingest` with node_type: "decision" |
-| Bug root cause identified | `smart_ingest` with node_type: "bug" |
-| Pattern chosen over alternatives | `smart_ingest` with node_type: "pattern" |
-| User corrects your approach | `smart_ingest` with node_type: "preference" |
+| User states preference | `smart_ingest` node_type: "preference" |
+| Architectural decision | `smart_ingest` node_type: "decision" |
+| Bug root cause identified | `smart_ingest` node_type: "bug" |
+| Pattern chosen over alternatives | `smart_ingest` node_type: "pattern" |
+| User corrects your approach | `smart_ingest` node_type: "preference" |
 | Codebase pattern discovered | `codebase` with appropriate pattern_type |
-| `/workflows:compound` creates solution | `smart_ingest` with node_type: "pattern" (root cause + insight) |
-| `/workflows:plan` research completes | `smart_ingest` with node_type: "decision" (approach chosen) |
-| `/workflows:review` finds P1/P2 | `smart_ingest` with node_type: "pattern" (finding summary) |
 
-**Recognition patterns** — store when you hear:
-- "I prefer..." / "I like..." / "I always..." / "I never..."
+Recognition phrases — store when you hear:
+- "I prefer..." / "I always..." / "I never..."
 - "Let's go with X because..." / "We chose X over Y"
-- "The reason this failed was..." / "Root cause:"
-- "From now on..." / "Going forward..."
-- "That's not how we do it" / "Actually, we..."
-
-### 3. Session End: Capture Learnings
-Before ending significant sessions:
-- What decisions were made that should persist?
-- What did you learn about the user's preferences?
-- Set any intentions for future work?
-
-### 4. Before Asking Questions You Might Already Know
-Before asking "What framework do you use?" or "How do you prefer X?", **search first**:
+- "Root cause:" / "The reason this failed was..."
+- "From now on..." / "That's not how we do it"
+
+### Before asking questions, search first
+
 ```
 mcp__vestige__search query: "preference {topic}"
 ```
 
-## Node Types Reference
+### Session end — capture before closing
+
+- What decisions persist?
+- What preferences were revealed?
+- Set intentions for next session?
+
+## Node Types
 
 | Type | Use For |
 |------|---------|
@@ -185,75 +162,57 @@ mcp__vestige__search query: "preference {topic}"
 
 ## Memory States
 
-Vestige manages memory lifecycle automatically via FSRS-6:
-
 | State | Meaning |
 |-------|---------|
-| **Active** | Readily accessible, frequently retrieved |
-| **Dormant** | Stored but weakly retrievable — promote if still relevant |
-| **Silent** | Deeply encoded, temporarily inaccessible |
-| **Unavailable** | Naturally decayed or removed |
-
-Memories that are searched for get reinforced. Unused memories naturally decay. This prevents knowledge bloat without manual cleanup.
+| Active | Readily accessible |
+| Dormant | Weakly retrievable — promote if still relevant |
+| Silent | Deeply encoded, temporarily inaccessible |
+| Unavailable | Decayed or removed |
 
 ## Decision Logic
 
-**Will it fade if we stop referencing it? That determines where it goes.**
-
 ```
-IF knowledge that should strengthen with use, fade if unused
-   (preferences, decisions, patterns, bugs, learnings):
-    → Vestige smart_ingest (neural memory — decays naturally)
-ELSE IF reference material that should never be forgotten
-   (wiki, standards, PRDs, architecture docs, code samples):
-    → Qdrant qdrant-store (permanent library)
+IF knowledge that strengthens with use, fades if unused
+   (preferences, decisions, patterns, bugs):
+    → Vestige smart_ingest
+ELSE IF reference material that must never be forgotten
+   (standards, PRDs, architecture docs):
+    → Qdrant qdrant-store
 ELSE IF session state or project progress:
-    → Serena write_memory (project workbench)
-ELSE IF future reminder or intention:
+    → Serena write_memory
+ELSE IF future reminder:
     → Vestige intention
 ELSE IF codebase architecture pattern:
     → Vestige codebase
 ELSE IF searching for prior context:
-    → Vestige search (semantic + keyword)
+    → Vestige search
 ```
 
 ## What NOT to Store
 
-- Temporary debugging steps (use Serena session state instead)
+- Temporary debugging steps (use Serena session state)
 - One-off fixes unlikely to recur
-- Information already in project docs (CLAUDE.md, README)
-- Sensitive data (credentials, API keys)
-- Session progress (use Serena for that)
+- Info already in CLAUDE.md or README
+- Credentials, API keys
+- Session progress (use Serena)
 
 ## Migration from Memory MCP
 
-Vestige replaces Memory MCP. The mapping:
-
 | Memory MCP | Vestige Equivalent |
 |------------|-------------------|
-| `search_nodes` | `search` (semantic + keyword hybrid) |
+| `search_nodes` | `search` |
 | `open_nodes` | `search` with specific name |
-| `create_entities` | `smart_ingest` (auto-dedup) |
-| `add_observations` | `smart_ingest` (auto-UPDATE on similarity) |
-| `create_relations` | Not needed — spreading activation via semantic similarity |
+| `create_entities` | `smart_ingest` |
+| `add_observations` | `smart_ingest` |
+| `create_relations` | Not needed (spreading activation via semantic similarity) |
 | `read_graph` | `memory_timeline` or `search` |
-| `delete_*` | `memory` with action: "remove" or `demote_memory` |
+| `delete_*` | `memory` action: "remove" or `demote_memory` |
 
 ## Setup
 
-Install Vestige MCP:
-
 ```bash
-# Via cargo (Rust required)
 cargo install vestige-mcp
-
-# Or download binary from releases
-# https://github.com/samvallad33/vestige/releases
-```
-
-Configure in Claude Code:
-```bash
 claude mcp add --scope user vestige -- vestige-mcp
 ```
 
-Configuration is stored in `~/.config/vestige/` (global) or `.vestige/` (per-project).
+Config: `~/.config/vestige/` (global) or `.vestige/` (per-project).

package/plugins/ima-claude/skills/php-authnet/SKILL.md

@@ -5,14 +5,12 @@ description: "Authorize.Net PHP SDK patterns for payment processing, CIM profile
 
 # Authorize.Net PHP SDK
 
-Patterns and reference for the `authorizenet/authorizenet` PHP SDK (^2.0). PHP-only — no JavaScript, Python, Ruby, or Node patterns.
+Patterns for `authorizenet/authorizenet` PHP SDK (^2.0). PHP-only.
 
-**Companion skills**: `php-fp` (core FP patterns), `php-fp-wordpress` (WordPress integration)
+**Companion skills**: `php-fp`, `php-fp-wordpress`
 
 ## Architecture: Three-Layer FP Pattern
 
-Authorize.Net integration follows a strict three-layer separation:
-
 ```
 [Pure Builders]  →  [SDK Adapter (Impure)]  →  [Pure Parsers]
    plain arrays         SDK objects + I/O          result arrays
@@ -20,7 +18,7 @@ Authorize.Net integration follows a strict three-layer separation:
 
 ### Layer 1: Pure Request Builders
 
-Normalize input into plain arrays. No SDK imports, no `date()`, no side effects.
+Normalize input to plain arrays. No SDK imports, no `date()`, no side effects.
 
 ```php
 <?php declare(strict_types=1);
@@ -37,7 +35,7 @@ function build_charge_request(array $payment_data): array {
 
 ### Layer 2: SDK Adapter (Impure)
 
-All `use net\authorize\api\...` imports confined here. Builds SDK objects, executes requests, normalizes responses to plain arrays. Never throws — catches exceptions and returns error arrays.
+All `use net\authorize\api\...` imports confined here. Builds SDK objects, executes requests, normalizes responses to plain arrays. Never throws — catches exceptions, returns error arrays.
 
 ```php
 <?php declare(strict_types=1);
@@ -57,8 +55,6 @@ function sdk_charge_customer(array $payment_data, array $credentials): array {
         $merchant_auth->setName($credentials['api_login_id']);
         $merchant_auth->setTransactionKey($credentials['transaction_key']);
 
-        // ... build SDK objects from plain array ...
-
         $controller = new AnetController\CreateTransactionController($request);
         $response = $controller->executeWithApiResponse($credentials['api_url']);
 
@@ -67,7 +63,6 @@ function sdk_charge_customer(array $payment_data, array $credentials): array {
         return [
             'result_code'    => $response->getMessages()->getResultCode(),
             'transaction_id' => $response->getTransactionResponse()?->getTransId(),
-            // ... normalize all fields to plain values ...
         ];
     } catch (\Exception $e) {
         return array_merge($null_response, [
@@ -80,7 +75,7 @@ function sdk_charge_customer(array $payment_data, array $credentials): array {
 
 ### Layer 3: Pure Response Parsers
 
-Interpret normalized arrays into standard `['success' => bool, ...]` results. No SDK dependencies.
+Interpret normalized arrays into `['success' => bool, ...]` results. No SDK dependencies.
 
 ```php
 <?php declare(strict_types=1);
@@ -96,23 +91,22 @@ function parse_charge_response(array $response): array {
 }
 ```
 
-### SDK Orchestrator Pattern
+### Orchestrator
 
-Thin glue connecting adapter to parser — no business logic:
+Thin glue — no business logic:
 
 ```php
 function charge_customer_via_sdk(array $payment_data, array $credentials): array {
-    $normalized = sdk_charge_customer($payment_data, $credentials);
-    return parse_charge_response($normalized);
+    return parse_charge_response(sdk_charge_customer($payment_data, $credentials));
 }
 ```
 
 ## SDK Namespace Reference
 
 ```php
-use net\authorize\api\contract\v1 as AnetAPI;    // Data types (request/response objects)
-use net\authorize\api\controller as AnetController; // Controllers (execute requests)
-use net\authorize\api\constants\ANetEnvironment;   // SANDBOX / PRODUCTION URLs
+use net\authorize\api\contract\v1 as AnetAPI;       // Data types (request/response objects)
+use net\authorize\api\controller as AnetController;  // Controllers (execute requests)
+use net\authorize\api\constants\ANetEnvironment;     // SANDBOX / PRODUCTION URLs
 ```
 
 ## Authentication
@@ -123,22 +117,19 @@ $merchant_auth->setName($credentials['api_login_id']);
 $merchant_auth->setTransactionKey($credentials['transaction_key']);
 ```
 
-**Credential storage**: Use `wp-config.php` constants first, options table as fallback.
+**Credential storage**: `wp-config.php` constants first, options table as fallback.
 
 ```php
-// Constants-first pattern
 $api_login = defined('IMA_PAYMENTS_API_LOGIN_ID')
     ? IMA_PAYMENTS_API_LOGIN_ID
     : get_option('ima_payments_api_login_id', '');
 ```
 
-**Environment switching**:
+**Environment**:
 
 ```php
-// Sandbox
-$controller->executeWithApiResponse(ANetEnvironment::SANDBOX);
-// Production
-$controller->executeWithApiResponse(ANetEnvironment::PRODUCTION);
+$controller->executeWithApiResponse(ANetEnvironment::SANDBOX);    // Sandbox
+$controller->executeWithApiResponse(ANetEnvironment::PRODUCTION);  // Production
 ```
 
 ## Transaction Types
@@ -151,24 +142,20 @@ $controller->executeWithApiResponse(ANetEnvironment::PRODUCTION);
 | Refund | `refundTransaction` | Refund settled transaction |
 | Void | `voidTransaction` | Cancel unsettled transaction |
 
-## Accept.js Integration (PCI Compliance)
+## Accept.js Integration
 
-Accept.js tokenizes card data client-side. The server never sees raw card numbers — only opaque payment nonces (valid 15 minutes).
-
-**Server-side token consumption**:
+Accept.js tokenizes card data client-side — server never sees raw card numbers. Nonces valid 15 minutes.
 
 ```php
 $opaque_data = new AnetAPI\OpaqueDataType();
-$opaque_data->setDataDescriptor('COMMON.ACCEPT.INAPP.PAYMENT');
+$opaque_data->setDataDescriptor('COMMON.ACCEPT.INAPP.PAYMENT'); // always this value
 $opaque_data->setDataValue($payment_nonce);
 
 $payment_type = new AnetAPI\PaymentType();
 $payment_type->setOpaqueData($opaque_data);
 ```
 
-**Data descriptor** is always `'COMMON.ACCEPT.INAPP.PAYMENT'` for Accept.js tokens.
-
-## Quick Reference: Common Operations
+## Common Operations
 
 ### Charge with Accept.js Token
 
@@ -176,7 +163,7 @@ $payment_type->setOpaqueData($opaque_data);
 $transaction_request = new AnetAPI\TransactionRequestType();
 $transaction_request->setTransactionType('authCaptureTransaction');
 $transaction_request->setAmount($amount);
-$transaction_request->setPayment($payment_type); // from Accept.js opaque data
+$transaction_request->setPayment($payment_type);
 ```
 
 ### Charge Stored CIM Profile
@@ -195,12 +182,12 @@ $transaction_request->setAmount($amount);
 $transaction_request->setProfile($profile_to_charge);
 ```
 
-### Refund a Settled Transaction
+### Refund Settled Transaction
 
 ```php
 $credit_card = new AnetAPI\CreditCardType();
 $credit_card->setCardNumber('XXXX1234'); // last 4 digits
-$credit_card->setExpirationDate('XXXX');  // literal 'XXXX'
+$credit_card->setExpirationDate('XXXX'); // literal 'XXXX'
 
 $payment = new AnetAPI\PaymentType();
 $payment->setCreditCard($credit_card);
@@ -212,7 +199,7 @@ $tx->setRefTransId($original_transaction_id);
 $tx->setPayment($payment);
 ```
 
-### Void an Unsettled Transaction
+### Void Unsettled Transaction
 
 ```php
 $tx = new AnetAPI\TransactionRequestType();
@@ -222,14 +209,11 @@ $tx->setRefTransId($transaction_id);
 
 ## Error Handling
 
-### Response Structure
-
-AuthNet responses have two levels of messages:
-
-1. **Top-level**: `$response->getMessages()` — API-level success/failure
+Responses have two message levels:
+1. **Top-level**: `$response->getMessages()` — API success/failure
 2. **Transaction-level**: `$tresponse->getErrors()` / `$tresponse->getMessages()` — transaction result
 
-Always check both. A transaction can fail (`tresponse->getErrors()`) even when the API call succeeds (`result_code === 'Ok'`).
+Always check both. Transaction can fail even when API call succeeds.
 
 ### Common Error Codes
 
@@ -244,32 +228,15 @@ Always check both. A transaction can fail (`tresponse->getErrors()`) even when t
 
 ### E00039 Duplicate Profile Recovery
 
-AuthNet includes the existing profile ID in the error text:
-
 ```php
 function extract_profile_id_from_error(string $error_text): string|false {
     return preg_match('/ID\s+(\d+)/', $error_text, $m) ? $m[1] : false;
 }
 ```
 
-## When to Load Reference Files
-
-### Full API Reference
-**File**: `references/api-reference.md`
-**Load when**:
-- Need complete SDK class/method listings
-- Working with CIM customer profiles (create, update, delete, payment profiles)
-- Working with ARB recurring billing (subscriptions, schedules, trials)
-- Need webhook event types and HMAC-SHA512 signature validation
-- Working with transaction reporting API
-- Need response code tables or field constraints
-- Implementing refunds, voids, or auth-only flows
-
-### Sandbox & Testing Guide
-**File**: `references/sandbox-testing.md`
-**Load when**:
-- Setting up sandbox environment or test credentials
-- Need test card numbers and expected responses
-- Debugging sandbox-specific issues (CIM→ARB propagation delay)
-- Writing PHPUnit tests for payment functions
-- Need sandbox vs production behavioral differences
+## Reference Files
+
+| File | Load when |
+|------|-----------|
+| `references/api-reference.md` | Complete SDK class/method listings; CIM profiles; ARB subscriptions; webhooks + HMAC-SHA512; reporting API; response codes; refunds/voids/auth-only |
+| `references/sandbox-testing.md` | Sandbox setup; test card numbers; sandbox vs production differences; CIM→ARB propagation delay; PHPUnit patterns |