Article
Codex Prompt Template for Singapore Broker and Chart Data Workflows
Use a Codex prompt template for Singapore broker and chart-data workflows with SGX, US market, provider, export, and compliance boundaries.
Codex can help inspect a broker and chart-data workflow, but the prompt has to define the job carefully. For Singapore traders, the prompt should name the market, provider, broker assumption, export fields, and advice boundary.
Quick Answer
A Singapore broker chart-data prompt should ask Codex to inspect structure: market, broker or provider, symbol mapping, session fields, notes, levels, labels, drawings, export format, missing fields, and unsupported assumptions.
Use Singapore workflow hub as the wider workflow hub, Using Codex or Claude Code With IBKR Chart Data for the global IBKR workflow, and IBKR Singapore Chart Workflow for SGX and US Market Review for the Singapore IBKR version.
What the Prompt Should Not Ask
Do not ask Codex to decide whether to buy, sell, size, hold, or automate a trade. That changes the task from workflow review into advice or trading instruction, which is outside this use case.
A safer prompt asks Codex to find missing fields, identify unclear assumptions, suggest schema names, flag data-lineage gaps, and create a review checklist for the trader to inspect manually.
Singapore Prompt Template
Use this structure as a starting point: Review this Singapore technical trading chart-data workflow. The workflow uses [broker or provider], [market], [symbol set], [timeframe], [session], and [export format]. Inspect whether the fields preserve market, symbol, SGT review time, session, levels, labels, drawings, notes, invalidation context, provider assumptions, and broker-data boundaries. Return missing fields, schema risks, and a safer review checklist. Do not recommend trades, brokers, securities, position sizes, tax treatment, CPF or SRS actions, or strategies.
Edit the prompt for the trader's actual setup. If the workflow compares brokers, use IBKR Singapore vs Tiger Brokers vs Moomoo: API and Chart Workflow Fit before turning the prompt into a recurring review process.
Fields Codex Can Review
Codex is useful when the input has a concrete artifact: a JSON schema, CSV layout, export sample, note template, or broker-data checklist. It is weaker when the prompt is just a broad market question.
Give Codex samples from MyLinedChart exports, broker records, or a small manual table, then ask for review of structure and assumptions.
| Field Area | Codex Task | Human Check |
|---|---|---|
| Market and session | Find missing SGX, US, and SGT fields | Confirm actual session logic |
| Provider assumptions | Flag undocumented provider behavior | Verify with broker or data provider |
| Symbol mapping | Compare chart, broker, and export names | Test with real symbols |
| Chart context | Check notes, levels, labels, drawings | Confirm trading definitions |
| Output boundary | Keep output as checklist or schema review | Reject trade instructions |
Limits and Claims to Keep Clear
This prompt pattern is educational. It does not provide investment, trading, tax, legal, CPF, SRS, or financial advice and does not recommend brokers or securities.
MyLinedChart does not guarantee SGX data, broker API access, exchange entitlements, TradingView support, SGD checkout behavior, or automatic trading.
FAQ
What should a Singapore Codex broker prompt include?
Include market, broker or provider, symbol set, timeframe, session, SGT review time, export format, chart fields, provider assumptions, and explicit advice boundaries.
Should Codex recommend trades from Singapore broker data?
No. Use Codex for workflow structure, missing-field checks, schema review, and documentation, not for trade recommendations.
How does MyLinedChart support the prompt?
MyLinedChart can provide structured chart context such as notes, levels, drawings, labels, and exports that Codex can inspect.
Sample Structured Chart-Data Exports
Review how chart drawings, annotations, OHLC, volume, and execution context become reusable structured data.