@rubix0270/arboris 1.0.2 → 1.0.4

package/prisma/skills/ios-icon-gen/scripts/iconify_gen.sh

@@ -1,235 +0,0 @@
-#!/bin/bash
-#
-# Generate iOS icon imagesets from Iconify API (275k+ open source icons)
-# Uses: curl (download SVG) + sips (SVG->PNG conversion, built into macOS)
-#
-# Usage:
-#   iconify_gen.sh <icon-id> <asset-name> [options]
-#   iconify_gen.sh search <query> [--prefix <collection>] [--limit <n>]
-#
-# Examples:
-#   iconify_gen.sh mdi:receipt-text-outline myExpenseIcon
-#   iconify_gen.sh search "business card"
-#   iconify_gen.sh search receipt --prefix mdi
-
-set -euo pipefail
-
-API_BASE="https://api.iconify.design"
-readonly CURL_OPTS=(--fail --silent --show-error --connect-timeout 10 --max-time 30)
-
-# Defaults
-SIZE=68
-COLOR="8E8E93"
-OUTPUT="/tmp/icons"
-LIMIT=20
-
-require_value() {
-    local flag="$1"
-    local value="${2-}"
-    if [[ -z "$value" || "$value" == --* ]]; then
-        echo "ERROR: ${flag} requires a value" >&2
-        exit 1
-    fi
-}
-
-usage() {
-    cat <<'EOF'
-Usage:
-  iconify_gen.sh <icon-id> <asset-name> [options]    Generate an icon imageset
-  iconify_gen.sh search <query> [options]             Search for icons
-  iconify_gen.sh preview <icon-id>                    Download preview SVG
-  iconify_gen.sh collections                          List popular icon collections
-
-Generate Options:
-  --size <pt>       Base size in points (default: 68)
-  --color <hex>     Color hex without # (default: 8E8E93)
-  --output <dir>    Output directory (default: /tmp/icons)
-
-Search Options:
-  --prefix <name>   Filter by collection (e.g., mdi, lucide, tabler, ph)
-  --limit <n>       Max results (default: 20)
-
-Icon ID Format: <collection>:<icon-name>
-  Examples: mdi:receipt-text-outline, lucide:credit-card, ph:address-book
-
-Popular Collections:
-  mdi      Material Design Icons (7400+ icons)
-  lucide   Lucide (1700+ icons)
-  tabler   Tabler Icons (6000+ icons)
-  ph       Phosphor (9000+ icons)
-  ri       Remix Icon (2800+ icons)
-  carbon   Carbon (2100+ icons)
-EOF
-    exit 0
-}
-
-search_icons() {
-    local query="$1"
-    shift
-    local prefix=""
-
-    while [[ $# -gt 0 ]]; do
-        case "$1" in
-            --prefix) require_value --prefix "${2-}"; prefix="$2"; shift 2 ;;
-            --limit) require_value --limit "${2-}"; LIMIT="$2"; shift 2 ;;
-            *) shift ;;
-        esac
-    done
-
-    local encoded_query
-    encoded_query="$(python3 -c "import urllib.parse, sys; print(urllib.parse.quote(sys.argv[1]))" "$query")"
-    local url="${API_BASE}/search?query=${encoded_query}&limit=${LIMIT}"
-    if [[ -n "$prefix" ]]; then
-        url="${url}&prefix=${prefix}"
-    fi
-
-    local response
-    response=$(curl "${CURL_OPTS[@]}" "$url") || { echo "ERROR: Search request failed"; exit 1; }
-
-    local total
-    total=$(echo "$response" | python3 -c "import sys,json; print(json.load(sys.stdin).get('total',0))")
-
-    echo "Found ${total} icons for '${query}':"
-    echo ""
-    echo "$response" | python3 -c "
-import sys, json
-data = json.load(sys.stdin)
-for icon in data.get('icons', []):
-    print(f'  {icon}')
-"
-    echo ""
-    echo "Generate with: iconify_gen.sh <icon-id> <asset-name>"
-    echo "Preview with:  iconify_gen.sh preview <icon-id>"
-}
-
-list_collections() {
-    echo "Popular Iconify collections:"
-    echo ""
-    local resp
-    resp=$(curl "${CURL_OPTS[@]}" "${API_BASE}/collections") || { echo "ERROR: Failed to fetch collections list"; exit 1; }
-    echo "$resp" | python3 -c "
-import sys, json
-data = json.load(sys.stdin)
-popular = ['mdi','lucide','tabler','ph','ri','carbon','solar','heroicons','bi','octicon','ion','fe','charm','ci','iconoir','basil','uil','mingcute','flowbite','mynaui']
-for k in popular:
-    if k in data:
-        v = data[k]
-        name = v.get('name','')
-        total = v.get('total',0)
-        print(f'  {k:12s} {name} ({total} icons)')
-"
-    echo ""
-    echo "Full list: https://icon-sets.iconify.design/"
-}
-
-preview_icon() {
-    local icon_id="$1"
-    local collection="${icon_id%%:*}"
-    local name="${icon_id#*:}"
-    local url="${API_BASE}/${collection}/${name}.svg?width=136&height=136&color=%23${COLOR}"
-    local outfile="/tmp/iconify_preview_${collection}_${name}.svg"
-
-    curl "${CURL_OPTS[@]}" "$url" -o "$outfile" || { echo "ERROR: Icon '${icon_id}' not found"; exit 1; }
-    echo "Preview SVG: ${outfile}"
-    echo "URL: ${url}"
-
-    # Also convert to PNG for visual check
-    local pngfile="/tmp/iconify_preview_${collection}_${name}.png"
-    sips -s format png "$outfile" --out "$pngfile" >/dev/null 2>&1 || echo "WARNING: sips conversion failed; PNG may be incorrect"
-    echo "Preview PNG: ${pngfile}"
-}
-
-generate_icon() {
-    local icon_id="$1"
-    local asset_name="$2"
-    shift 2
-
-    while [[ $# -gt 0 ]]; do
-        case "$1" in
-            --size) require_value --size "${2-}"; SIZE="$2"; shift 2 ;;
-            --color) require_value --color "${2-}"; COLOR="$2"; shift 2 ;;
-            --output) require_value --output "${2-}"; OUTPUT="$2"; shift 2 ;;
-            *) shift ;;
-        esac
-    done
-
-    local collection="${icon_id%%:*}"
-    local name="${icon_id#*:}"
-    local imageset_dir="${OUTPUT}/${asset_name}.imageset"
-
-    mkdir -p "$imageset_dir"
-
-    echo "Generating ${asset_name} from Iconify '${icon_id}':"
-
-    local scales=("1:${SIZE}" "2:$((SIZE * 2))" "3:$((SIZE * 3))")
-
-    for scale_info in "${scales[@]}"; do
-        local scale="${scale_info%%:*}"
-        local px="${scale_info#*:}"
-        local suffix=""
-        [[ "$scale" != "1" ]] && suffix="@${scale}x"
-
-        local svg_url="${API_BASE}/${collection}/${name}.svg?width=${px}&height=${px}&color=%23${COLOR}"
-        local svg_file="${imageset_dir}/${asset_name}${suffix}.svg"
-        local png_file="${imageset_dir}/${asset_name}${suffix}.png"
-
-        curl "${CURL_OPTS[@]}" "$svg_url" -o "$svg_file" || { echo "ERROR: Failed to download icon '${icon_id}'"; exit 1; }
-        sips -s format png "$svg_file" --out "$png_file" >/dev/null 2>&1 || echo "WARNING: sips conversion may have failed for ${svg_file}"
-        rm "$svg_file"
-
-        echo "  ${asset_name}${suffix}.png (${px}x${px})"
-    done
-
-    # Write Contents.json
-    cat > "${imageset_dir}/Contents.json" <<JSONEOF
-{
-  "images" : [
-    {
-      "filename" : "${asset_name}.png",
-      "idiom" : "universal",
-      "scale" : "1x"
-    },
-    {
-      "filename" : "${asset_name}@2x.png",
-      "idiom" : "universal",
-      "scale" : "2x"
-    },
-    {
-      "filename" : "${asset_name}@3x.png",
-      "idiom" : "universal",
-      "scale" : "3x"
-    }
-  ],
-  "info" : {
-    "author" : "xcode",
-    "version" : 1
-  }
-}
-JSONEOF
-
-    echo "Output: ${imageset_dir}/"
-}
-
-# Main
-[[ $# -eq 0 ]] && usage
-[[ "$1" == "--help" || "$1" == "-h" ]] && usage
-
-case "$1" in
-    search)
-        shift
-        [[ $# -eq 0 ]] && { echo "Usage: iconify_gen.sh search <query>"; exit 1; }
-        search_icons "$@"
-        ;;
-    preview)
-        shift
-        [[ $# -eq 0 ]] && { echo "Usage: iconify_gen.sh preview <icon-id>"; exit 1; }
-        preview_icon "$1"
-        ;;
-    collections)
-        list_collections
-        ;;
-    *)
-        [[ $# -lt 2 ]] && { echo "Usage: iconify_gen.sh <icon-id> <asset-name> [options]"; exit 1; }
-        generate_icon "$@"
-        ;;
-esac

package/prisma/skills/iterative-retrieval/SKILL.md

@@ -1,212 +0,0 @@
----
-name: iterative-retrieval
-description: Pattern for progressively refining context retrieval to solve the subagent context problem
-metadata:
-  origin: ECC
----
-
-# Iterative Retrieval Pattern
-
-Solves the "context problem" in multi-agent workflows where subagents don't know what context they need until they start working.
-
-## When to Activate
-
-- Spawning subagents that need codebase context they cannot predict upfront
-- Building multi-agent workflows where context is progressively refined
-- Encountering "context too large" or "missing context" failures in agent tasks
-- Designing RAG-like retrieval pipelines for code exploration
-- Optimizing token usage in agent orchestration
-
-## The Problem
-
-Subagents are spawned with limited context. They don't know:
-- Which files contain relevant code
-- What patterns exist in the codebase
-- What terminology the project uses
-
-Standard approaches fail:
-- **Send everything**: Exceeds context limits
-- **Send nothing**: Agent lacks critical information
-- **Guess what's needed**: Often wrong
-
-## The Solution: Iterative Retrieval
-
-A 4-phase loop that progressively refines context:
-
-```
-┌─────────────────────────────────────────────┐
-│                                             │
-│   ┌──────────┐      ┌──────────┐            │
-│   │ DISPATCH │─────│ EVALUATE │            │
-│   └──────────┘      └──────────┘            │
-│        ▲                  │                 │
-│        │                  ▼                 │
-│   ┌──────────┐      ┌──────────┐            │
-│   │   LOOP   │─────│  REFINE  │            │
-│   └──────────┘      └──────────┘            │
-│                                             │
-│        Max 3 cycles, then proceed           │
-└─────────────────────────────────────────────┘
-```
-
-### Phase 1: DISPATCH
-
-Initial broad query to gather candidate files:
-
-```javascript
-// Start with high-level intent
-const initialQuery = {
-  patterns: ['src/**/*.ts', 'lib/**/*.ts'],
-  keywords: ['authentication', 'user', 'session'],
-  excludes: ['*.test.ts', '*.spec.ts']
-};
-
-// Dispatch to retrieval agent
-const candidates = await retrieveFiles(initialQuery);
-```
-
-### Phase 2: EVALUATE
-
-Assess retrieved content for relevance:
-
-```javascript
-function evaluateRelevance(files, task) {
-  return files.map(file => ({
-    path: file.path,
-    relevance: scoreRelevance(file.content, task),
-    reason: explainRelevance(file.content, task),
-    missingContext: identifyGaps(file.content, task)
-  }));
-}
-```
-
-Scoring criteria:
-- **High (0.8-1.0)**: Directly implements target functionality
-- **Medium (0.5-0.7)**: Contains related patterns or types
-- **Low (0.2-0.4)**: Tangentially related
-- **None (0-0.2)**: Not relevant, exclude
-
-### Phase 3: REFINE
-
-Update search criteria based on evaluation:
-
-```javascript
-function refineQuery(evaluation, previousQuery) {
-  return {
-    // Add new patterns discovered in high-relevance files
-    patterns: [...previousQuery.patterns, ...extractPatterns(evaluation)],
-
-    // Add terminology found in codebase
-    keywords: [...previousQuery.keywords, ...extractKeywords(evaluation)],
-
-    // Exclude confirmed irrelevant paths
-    excludes: [...previousQuery.excludes, ...evaluation
-      .filter(e => e.relevance < 0.2)
-      .map(e => e.path)
-    ],
-
-    // Target specific gaps
-    focusAreas: evaluation
-      .flatMap(e => e.missingContext)
-      .filter(unique)
-  };
-}
-```
-
-### Phase 4: LOOP
-
-Repeat with refined criteria (max 3 cycles):
-
-```javascript
-async function iterativeRetrieve(task, maxCycles = 3) {
-  let query = createInitialQuery(task);
-  let bestContext = [];
-
-  for (let cycle = 0; cycle < maxCycles; cycle++) {
-    const candidates = await retrieveFiles(query);
-    const evaluation = evaluateRelevance(candidates, task);
-
-    // Check if we have sufficient context
-    const highRelevance = evaluation.filter(e => e.relevance >= 0.7);
-    if (highRelevance.length >= 3 && !hasCriticalGaps(evaluation)) {
-      return highRelevance;
-    }
-
-    // Refine and continue
-    query = refineQuery(evaluation, query);
-    bestContext = mergeContext(bestContext, highRelevance);
-  }
-
-  return bestContext;
-}
-```
-
-## Practical Examples
-
-### Example 1: Bug Fix Context
-
-```
-Task: "Fix the authentication token expiry bug"
-
-Cycle 1:
-  DISPATCH: Search for "token", "auth", "expiry" in src/**
-  EVALUATE: Found auth.ts (0.9), tokens.ts (0.8), user.ts (0.3)
-  REFINE: Add "refresh", "jwt" keywords; exclude user.ts
-
-Cycle 2:
-  DISPATCH: Search refined terms
-  EVALUATE: Found session-manager.ts (0.95), jwt-utils.ts (0.85)
-  REFINE: Sufficient context (2 high-relevance files)
-
-Result: auth.ts, tokens.ts, session-manager.ts, jwt-utils.ts
-```
-
-### Example 2: Feature Implementation
-
-```
-Task: "Add rate limiting to API endpoints"
-
-Cycle 1:
-  DISPATCH: Search "rate", "limit", "api" in routes/**
-  EVALUATE: No matches - codebase uses "throttle" terminology
-  REFINE: Add "throttle", "middleware" keywords
-
-Cycle 2:
-  DISPATCH: Search refined terms
-  EVALUATE: Found throttle.ts (0.9), middleware/index.ts (0.7)
-  REFINE: Need router patterns
-
-Cycle 3:
-  DISPATCH: Search "router", "express" patterns
-  EVALUATE: Found router-setup.ts (0.8)
-  REFINE: Sufficient context
-
-Result: throttle.ts, middleware/index.ts, router-setup.ts
-```
-
-## Integration with Agents
-
-Use in agent prompts:
-
-```markdown
-When retrieving context for this task:
-1. Start with broad keyword search
-2. Evaluate each file's relevance (0-1 scale)
-3. Identify what context is still missing
-4. Refine search criteria and repeat (max 3 cycles)
-5. Return files with relevance >= 0.7
-```
-
-## Best Practices
-
-1. **Start broad, narrow progressively** - Don't over-specify initial queries
-2. **Learn codebase terminology** - First cycle often reveals naming conventions
-3. **Track what's missing** - Explicit gap identification drives refinement
-4. **Stop at "good enough"** - 3 high-relevance files beats 10 mediocre ones
-5. **Exclude confidently** - Low-relevance files won't become relevant
-
-## Related
-
-- [The Longform Guide](https://x.com/affaanmustafa/status/2014040193557471352) - Subagent orchestration section
-- `continuous-learning` skill - For patterns that improve over time
-- Agent definitions bundled with ECC (manual install path: `agents/`)

package/prisma/skills/ito-basket-compare/SKILL.md

@@ -1,64 +0,0 @@
----
-name: ito-basket-compare
-description: Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.
-metadata:
-  origin: ECC
----
-
-# Itô Basket Compare
-
-Use this skill to compare a basket, theme, or market set against a user's
-knowledge base, portfolio notes, research memo, CRM context, or stated thesis.
-
-This skill is read-only. It does not recommend trades. It helps a user inspect
-fit, exposure, assumptions, and missing context before they decide what to do.
-
-## Guardrails
-
-- Do not provide investment advice or tell the user to buy, sell, hold, hedge,
-  lever, or size a trade.
-- Do not execute, prepare, or submit orders.
-- Do not use private documents unless the user explicitly points to them.
-- Use `ITO_API_KEY` only for read-only Itô basket/market data after explicit
-  user request.
-- If comparing against financials, preserve privacy and summarize only the
-  fields needed for the comparison.
-
-## Comparison Modes
-
-### Basket vs Knowledge Base
-
-1. Identify the basket theme and underliers.
-2. Retrieve the user's relevant notes, docs, or memory snippets.
-3. Map each underlier to claims, sources, uncertainties, and stale assumptions.
-4. Return aligned signals, conflicting signals, and missing research.
-
-### Basket vs Portfolio Notes
-
-1. Parse the user's watchlist, holdings summary, or exposure notes.
-2. Compare themes, geographies, time horizons, and event outcomes.
-3. Flag concentration, correlation, and duplicated narrative exposure.
-4. Avoid recommendations; phrase output as inspection and questions.
-
-### Basket vs Financial Context
-
-1. Accept only user-provided or explicitly selected financial context.
-2. Identify liquidity, drawdown, time-horizon, and constraint mismatches.
-3. Ask for missing constraints instead of guessing.
-
-## Output Contract
-
-Use this structure:
-
-1. Basket summary
-2. Comparison target
-3. Matches
-4. Conflicts or stale assumptions
-5. Missing context
-6. User-action checklist
-
-End with:
-
-```text
-This comparison is informational and not investment or trading advice.
-```

package/prisma/skills/ito-data-atlas-agent/SKILL.md

@@ -1,64 +0,0 @@
----
-name: ito-data-atlas-agent
-description: Design background Data Atlas style agents for Itô basket research, market discovery, parameter drafting, and human-in-the-loop editing. Use for architecture and workflow planning, not live order execution.
-metadata:
-  origin: ECC
----
-
-# Itô Data Atlas Agent
-
-Use this skill to design an agent that watches data sources, builds candidate
-prediction-market baskets, drafts parameter changes, and hands the result to a
-human for review.
-
-This skill describes architecture and workflow. It does not run live trading.
-
-## Guardrails
-
-- Keep all execution behind explicit human approval.
-- Require `ITO_API_KEY` only for read-only Itô data access unless a separate
-  private implementation explicitly adds execution controls.
-- Do not persist private user data unless the target repo already has a storage
-  contract and the user asks for it.
-- Do not expose private strategy logic, venue credentials, or local paths in
-  public docs.
-
-## Architecture Pattern
-
-Use four lanes:
-
-1. Research collector: public web, X, GitHub, venue docs, API metadata, and
-   Itô read endpoints when gated access exists.
-2. Basket drafter: turns sources into candidate underliers, weights, rules, and
-   questions.
-3. Risk reviewer: checks data freshness, venue limits, resolution ambiguity,
-   compliance notes, and prompt-injection exposure.
-4. Human editor: opens a chat or UI state where the user can approve, reject,
-   adjust, or ask for more research.
-
-## Workflow
-
-1. Define the user objective and excluded actions.
-2. List data sources and access requirements.
-3. Draft a basket spec with provenance for every underlier.
-4. Produce editable parameters rather than executable orders.
-5. Store an audit trail: inputs, model output, sources, and human decision.
-
-## Useful Skill Chains
-
-- `deep-research` for source collection.
-- `x-api` for current social/event signal.
-- `ito-market-intelligence` for venue and underlier context.
-- `ito-basket-compare` for user knowledge-base matching.
-- `prediction-market-risk-review` before any execution-capable integration.
-
-## Output Contract
-
-Return an implementation-ready workflow spec with:
-
-- data sources
-- access gates
-- agent roles
-- human approval points
-- storage/audit boundary
-- non-goals

package/prisma/skills/ito-market-intelligence/SKILL.md

@@ -1,61 +0,0 @@
----
-name: ito-market-intelligence
-description: Research prediction-market events, venues, underliers, liquidity, and news context for Itô basket workflows. Use for read-only market intelligence, API-gated Itô exploration, and source-grounded prediction-market briefings without investment advice or live trading.
-metadata:
-  origin: ECC
----
-
-# Itô Market Intelligence
-
-Use this skill when a user wants prediction-market context, event discovery,
-venue comparison, basket theme exploration, or an Itô API-backed market brief.
-
-This is a public teaser skill. It can work with public sources by default. Any
-Itô-backed data call requires explicit API access through `ITO_API_KEY`.
-
-## Guardrails
-
-- Do not provide investment, legal, tax, or trading advice.
-- Do not place, cancel, route, or simulate live orders.
-- Do not infer the user's financial situation unless they provide it.
-- Treat Polymarket, Kalshi, Itô, X, Exa, GitHub, and web data as source inputs,
-  not as truth by themselves.
-- Separate facts, market-implied signals, and your interpretation.
-
-## Workflow
-
-1. Clarify the market theme, venue, geography, and time horizon.
-2. Gather public market data from venue docs/APIs or source-grounded research.
-3. If `ITO_API_KEY` is present and the user explicitly asks for Itô data, call
-   only read endpoints and state that access is gated.
-4. Normalize event, underlier, liquidity, fee, resolution, and data-latency
-   differences across venues.
-5. Produce a decision brief:
-   - market/event summary
-   - available venues and underliers
-   - liquidity and data-quality caveats
-   - relevant news/source context
-   - open questions before any user action
-
-## Useful Skill Chains
-
-- Use `deep-research` or `exa-search` for source discovery.
-- Use `x-api` for public social signal discovery when X access is configured.
-- Use `market-research` for market sizing, competitors, or business use cases.
-- Use `prediction-market-risk-review` before any workflow touches user capital,
-  portfolio data, or execution-capable credentials.
-
-## Output Contract
-
-Default to a compact brief with source links and a clear caveat:
-
-```text
-This is market intelligence, not investment or trading advice.
-```
-
-If access is missing, say:
-
-```text
-Itô live basket/API data requires gated access. Request an ITO_API_KEY before
-using Itô-backed reads.
-```