Rupay

myself

[Rupay @l_rupay]

Gnfc chart analysis- learning

1-2-3 pattern formation. Yet to cross 3 stage.

@dmdsplyinvestor

[Royal Challengers Bengaluru @RCBTweets]

RCB win by 2️⃣3️⃣ runs.

It’s okay guys…. But don’t do it again!

[Rupay @l_rupay]

@JaySym_Ai Any update

[Mr. Quant (Jacob) @QuantIndicator]

It just keeps happening...

Something about 5min Hammers + 1min Divergence.

Except this time $ES also had a 15min Engulfing + 5min divergence.

4X confirmation for another 40 points.

TV took down this indicator after I published it... If you want the source code Like & DM me! I'll send it to you for free.

[Rupay @l_rupay]

@Rayner_Teo yes

[Rupay @l_rupay]

@Minato_MMXM Trade journal

[Minato💛 @Minato_MMXM]

After months of building… we finally decided this.

We’re giving the Gameify Trade Journal software FREE to all traders.

Like, Retweet and Comment “Trade Journal” I’ll send it to you. Make sure you follow me so I can directly DM you.

[Deepak @Deepak07_Trader]

Position sizing is the only edge you fully control.

You don’t blow up because of a bad view.
You blow up because the size was too big for the uncertainty.

Small size will make mistake as lessons and large size will damage you.
The negative working is not about the strategy or the trade mistake, it is about your nervous system is not ready for that size and thus you fail.

[Mаղʝմռα𝗍𝗁 Տ @ChikouTrader]

If you are losing Money in #Intraday Trading,

then you should read this !

[sameer kohli @SameerSmirkohli]

Personally tracking few setups for coming days ahead... #LICI Follow rules for reward,
#nifty #banknifty #sensex #breakoutstocks @stockstix @Rxanirudh1988 @_chartitude @BaapofOption #Crudeoil #inflation #russia #silver #TradeDeal #Trump #gold #crypto

[Rupay @l_rupay]

@karthik_raj2000 Mentorship

[Dan Go @CoachDanGo]

One of the greatest cheat codes in life is to never get offended. Train yourself to have a thick skin. Don't take things personally. Let others disagree with you. Being easily offended means you're easily manipulated. Want more peace? Avoid getting offended.

[BURKOV @burkov]

Before Claude Code, there were frontend developers, backend developers, full stack developers, DevOps, Java developers, Python developers, mobile developers, iOS developers, Android developers, data scientists, machine learning engineers, and plenty of others.

Since Claude Code, there are only shit coders and computer scientists left.

A computer scientist is the one who takes responsibility, while a shit coder is the one who doesn't.

[Rupay @l_rupay]

@AskCoachKev shred

[Rupay @l_rupay]

@hunterhammonds yes

[Rupay @l_rupay]

@Deishma dm

[Himanshu sharma @pheonix_trader]

📌"5 🌟🌟🌟🌟🌟 TRADING SETUP"🚀🚀

🟩Take a screenshot or printout & stick to your trading wall & Try to find these 5 Star Trading setups & try to trade only these kind of setups (Provided Market environment is favorable )

Your Trading will improve drastically 👇

Like , Repost

Follow @pheonix_trader for more such content

[0xSero @0xSero]

How I use Codex:

step 1:

- Setup GPT-5.2-XHIGH and tell it to read every files under what directory I want to work in
- Have it produce a map of the code, and a scope that is relevant to the big goal I want to accomplish
- Have it make a directory called /tasks where it makes 1 https://t.co/d9GHgqU4NH file in a sequence

step 2:

- Switch to gpt-5.2-codex-xhigh
- Attach the scope, the rules, and the https://t.co/d9GHgqU4NH
- Push the same message but change the number https://t.co/aqxZlaiq3F

The scope is the big picture. What we are trying to do, what it touches, why we made certain decisions etc..

The rules file is the instructions it has to follow during development:

1. checkout new branch when starting a task
2. complete the task as described, attempt to reduce code not make more for older projects.
3. run type-check, lint, full test suite (not deleting or skipping tests), commit and push
4. update documentation

Each task will take between 15 minutes and 1 hour, you can stack them on top each other so codex only sees 1 per turn.

2-24 hour runs depending on how well you specify
all code is typically functional
improved, cleaner code,

[Suresh K @SureshKBN]

Did you see the LTF chart?
Very good float. You rarely get these kinds of setups maybe once in 1 year.

Last time I saw something similar was RK Forge.
Look at the support it got around the 21-day EMA.

Learn TA at least support, resistance, and moving averages.
No excuses.
No one can teach you this except the market.
Plenty of free videos on YouTube, and AI can help too.

[Rafael Bittencourt @rafaelobitten]

Codex is trully amazing!

23 hours, working nonstop, delivering all the project’s pending sprints! GPT-5.2-Codex xhigh is amazing. I don’t need to keep telling it what to do every time. If I give it a set of sprints, it just executes. You just need to know how to control this monster!
@thsottiaux
@gdb

This is the first section from my https://t.co/7Ytm9ayFIl

# Global Rules (Must Follow)

You are a world-class software engineer and software architect.

Your motto is:

> **Every mission assigned is delivered with 100% quality and state-of-the-art execution — no hacks, no workarounds, no partial deliverables and no mock-driven confidence. Mocks/stubs may exist in unit tests for I/O boundaries, but final validation must rely on real integration and end-to-end tests.**

You always:

- Deliver end-to-end, production-like solutions with clean, modular, and maintainable architecture.
- Take full ownership of the task: you do not abandon work because it is complex or tedious; you only pause when requirements are truly contradictory or when critical clarification is needed.
- Are proactive and efficient: you avoid repeatedly asking for confirmation like “Can I proceed?” and instead move logically to next steps, asking focused questions only when they unblock progress.
- Follow the full engineering cycle for significant tasks: **understand → design → implement → (conceptually) test → refine → document**, using all relevant tools and environment capabilities appropriately.
- Respect both functional and non-functional requirements and, when the user’s technical ideas are unclear or suboptimal, you propose better, modern, state-of-the-art alternatives that still satisfy their business goals.
- Manage context efficiently and avoid abrupt, low-value interruptions; when you must stop due to platform limits, you clearly summarize what was done and what remains.