Data & Analytics

'"Provides Combine multiple models for improved prediction accuracy and

'"Provides Monitor production ML models for drift, decay, and performance

'"Implements create actionable trading features from raw market data

'"Provides Explainable AI for understanding and trusting trading model

'"Provides Detect anomalous market behavior, outliers, and potential

'''''Provides Comprehensive algorithm selection guide u2014 choose, implement,

**Role**: Step 2.7 — After the research plan is written, fetch a lightweight 8-metric snapshot for each `peer_tickers[]` so that the Mode C Peer Comparison table renders with real `[Portal]` Grade B numbers instead of `[Est] peer reference` placeholders. **Triggered by**: market-router Step 2.7 (Mode C and Mode D only — never Mode A or Mode B) **Reads**: `output/runs/{run_id}/{ticker}/research-plan.json` → `peer_tickers[]` **Writes**: `output/runs/{run_id}/peers/{TICKER}.json` (run-local) AND...

Governance metrics dashboard — coverage by category, cross-reference density, compliance readiness, and project comparison across all working projects

[COMMUNITY] Generate a public algorithm transparency notice complying with Article L311-3-1 CRPA (Loi République Numérique) for French public administration algorithmic decisions

Discover external data sources (APIs, datasets, open data portals) to fulfil project requirements

API de Produtos Vendidos da Tray. Utilize quando o desenvolvedor precisar consultar o histórico de vendas e analytics de produtos vendidos na loja. API somente leitura com filtros de data.

Capture high-quality screenshots with MCP tools. Use when the user asks to take a screenshot, show the screen, capture a window, document UI evidence, collect before/after images, inspect browser output, or verify a desktop app visually with WinForms MCP, WinApp MCP, browser screenshots, image previews, annotations, or screenshot diffs.

Reuse lower-level SIL libraries before writing custom helpers in FieldWorks. Use this whenever a task touches file or directory I/O, locked-file retries, paths or URIs, writing systems, keyboards, LCM caches/project IDs/service locators, linked files/media/config paths, localization, LIFT/import/export, FLExBridge or Chorus sync/merge flows, analytics/telemetry, morphology or NLP, scripture/Paratext integration, or SIL test helpers. Even for small fixes, check the package families and repo pa...

Verify changes with a weighted, repository-grounded rubric and explicit hard gates.

Review changes for correctness, style, and risk; propose fixes or follow-ups.

PowerShell best practices for scripts used in FieldWorks (dev scripts & CI helpers). Use when writing or modifying PowerShell scripts in scripts/ or Build/Agent/.

Plan and design a change set. Define scope, constraints, risks, and acceptance signals before implementation.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Create a change and generate all artifacts needed for implementation in one go. Use when the user wants the preferred OpenSpec fast path for a new proposal.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.