paint-objects
Skill17 starsChanged 7 months agoMITView on GitHub
Use when drawing or updating chart objects in MQL5 for this workspace. Follow the local rules for choosing the right object type, anchoring it to the correct candle, updating existing objects safely, and forcing chart redraw when needed.
In this repository12 other files it gives its agents.
- analyzeSkill
- candles-and-seriesSkill
- captions-davinciSkill
- compile-mql5Skill
- edit-davinciSkill
- expert-advisorsSkill
- forgeSkill
- gitSkill
- interfaceSkill
- optimizationSkill
- orquestateSkill
- run-backtestsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when creating or editing MQL5 code that paints chart objects with ObjectCreate, ObjectMove, or ObjectSetInteger.
- Very specific: line 14
Use OBJ_RECTANGLE for zones, gaps, ranges, and areas with top and bottom.
- Distinctive: line 15
Do not simulate a zone with two trend lines when the intent is a filled area.
- Distinctive: line 16
Use lines only when the user explicitly wants a line-based drawing.
- Distinctive: line 22
If the drawing is based on a multi-candle pattern, confirm which candle defines the start time.
- Very specific: line 37
Do not assume ObjectCreate will succeed repeatedly with the same name.
- Distinctive: line 39
If the object does not exist, create it.
- Very specific: line 40
If the object already exists, update it with ObjectMove.
- Distinctive: line 41
Keep object names stable and deterministic.
- Distinctive: line 59
After painting or updating objects, force a chart refresh when needed.
- Very specific: line 61
Call ChartRedraw(chart_id) after a batch of object updates.
- Distinctive: line 62
Do not assume the chart will visibly refresh immediately on its own.
- Distinctive: line 66
When painted objects do not appear, check these points before changing strategy logic:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paint Objects
Use this skill when creating or editing MQL5 code that paints chart objects with ObjectCreate, ObjectMove, or ObjectSetInteger.
Object Choice
Choose the object type that matches the visual requirement.
- Use
OBJ_RECTANGLEfor zones, gaps, ranges, and areas with top and bottom. - Do not simulate a zone with two trend lines when the intent is a filled area.
- Use lines only when the user explicitly wants a line-based drawing.
Anchoring
Anchor the object to the correct candle and prices.
- If the drawing is based on a multi-candle pattern, confirm which candle defines the start time.
- For the FVG case in this workspace, the rectangle must start at candle 1, the oldest candle in the 3-candle pattern.
- For zones, use the upper price as the top and the lower price as the bottom.
Example pattern for FVG:
datetime start_time = StructToTime(time);
datetime end_time = start_time + (duration_minutes * 60);
ObjectCreate(chart_id, rect_name, OBJ_RECTANGLE, 0, start_time, high, end_time, low);Repainting And Updates
Do not assume ObjectCreate will succeed repeatedly with the same name.
- If the object does not exist, create it.
- If the object already exists, update it with
ObjectMove. - Keep object names stable and deterministic.
Pattern:
if(ObjectFind(chart_id, object_name) < 0)
{
ObjectCreate(chart_id, object_name, OBJ_RECTANGLE, 0, start_time, high, end_time, low);
}
else
{
ObjectMove(chart_id, object_name, 0, start_time, high);
ObjectMove(chart_id, object_name, 1, end_time, low);
}Visibility
After painting or updating objects, force a chart refresh when needed.
- Call
ChartRedraw(chart_id)after a batch of object updates. - Do not assume the chart will visibly refresh immediately on its own.
Validation
When painted objects do not appear, check these points before changing strategy logic:
- The object name is not colliding with an existing object unexpectedly.
- Existing objects are updated with
ObjectMoveinstead of recreated blindly. ChartRedraw(...)is called after painting.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

