| name | search-first |
| description | Research the existing implementation, tests, primary technical sources, and financial rationale before adding trading code or dependencies. |
| metadata | {"origin":"adapted from ZMB-UZH/omero-docker-extended at b27dbe990703d64d13e540c40cf4e122954c664d"} |
Search First
Use this skill before new model logic, exchange behavior, risk controls,
dependencies, data pipelines, workflows, or broad refactors.
Search Order
- Read
README.md, the nearest src/simple_ai_trading/ module, and its tests.
- Use
rg for exact questions. Use cocoindex-code-search first only for
genuinely broad semantic routing.
- Read the closest design, provenance, model, or simulation document.
- Check official exchange/API documentation and primary library/release docs.
- For model or market claims, inspect peer-reviewed papers or authoritative
market-microstructure references and record assumptions and limitations.
- Compare maintained open-source implementations only after understanding
their data, leakage controls, execution model, and license.
- Adopt an existing local pattern, extend it minimally, or document why a new
implementation is necessary.
Rules
- Do not treat TradingView scripts, forum claims, stars, backtest screenshots,
or vendor marketing as proof of edge.
- Pin version-sensitive facts and cite exact sources in durable research docs.
- Keep tests offline unless the network boundary is explicitly stubbed.
- Never put credentials, account details, or private endpoints in queries.
- Do not use subagents or separate sessions for research in this repository.
