Remix

Make your own version of Pakistani Live Signals

Get an exact, working copy in your account, then change anything with chat.

Original by Zahid khan

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Build a complete, mobile-friendly web application named Pakistani Live Signal AI from scratch.

IMPORTANT: Build a real, testable application, not just a visual demo. Do not claim that any strategy guarantees profits or that prices match Quotex exactly unless this has been verified.

1. MARKET REQUIREMENTS

- Support LIVE Forex pairs: EUR/USD, GBP/USD, USD/JPY, AUD/USD, and other available major pairs.
- Support LIVE crypto pairs: BTC/USD and ETH/USD where reliable real-time data is available.
- Do NOT include OTC markets, synthetic prices, simulated candles, or fake signal data.
- Never silently fall back to mock data when a live feed disconnects.
- Show the data provider, last update time, connection status, and whether data is delayed or real-time.
- If real data is unavailable, clearly show DISCONNECTED or DATA UNAVAILABLE.

2. REAL MARKET DATA AND QUOTEX COMPARISON

- Use a legitimate market data API or WebSocket provider.
- Implement a secure server-side data service. Never expose private API keys in frontend code.
- Compare the selected asset's available price and candle timestamps against the corresponding Quotex LIVE chart.
- Do not invent or fabricate a Quotex API or claim direct integration unless an authorized interface is available.
- If direct Quotex data access is unavailable, provide a manual comparison mode using user-entered Quotex prices.
- Display the price difference, timestamp difference, and feed health.
- Never manipulate prices to make them appear equal.
- Use UTC internally and display Pakistan Standard Time (UTC+5) to the user.

3. STRATEGY: CEILING, FLOOR AND HAMMER

Implement the following strategy as a separate, testable strategy module.

CEILING / RESISTANCE:
Identify price areas where candles have reversed downward at least twice. Use confirmed swing highs and configurable tolerance rather than assuming every high is resistance.

FLOOR / SUPPORT:
Identify price areas where candles have reversed upward at least twice. Use confirmed swing lows and configurable tolerance.

BULLISH HAMMER:

- Price approaches the support area.
- The lower wick is long relative to the candle body.
- The upper wick is relatively small.
- Confirm the candle has closed before evaluating the signal.
- Check trend, nearby resistance and breakout conditions before considering UP.

BEARISH REJECTION:

- Price approaches the resistance area.
- The upper wick is long relative to the candle body.
- The lower wick is relatively small.
- Confirm the candle has closed before evaluating the signal.
- Check trend, nearby support and breakout conditions before considering DOWN.

BREAKOUT SAFETY:
If price breaks support or resistance with a strong candle, do not automatically trade in the opposite direction. Return NO TRADE until a valid setup is confirmed.

Do not assume that a hammer guarantees the next candle's direction. Make wick ratios, support/resistance tolerance and confirmation filters configurable.

4. GENERATE SIGNAL BUTTON

Create a clearly visible Generate Signal button.

For each request, return one of:

- UP
- DOWN
- NO TRADE

Show:

- Selected asset and timeframe
- Signal generation timestamp
- Data freshness and feed status
- Detected support and resistance
- Hammer/rejection confirmation
- Reasons for accepting or rejecting the setup
- Estimated confidence, clearly labelled as uncalibrated until validated
- Next one-minute candle's start and end times

Use completed candles for confirmation. Never use future data or look-ahead bias. Do not generate a signal from stale or missing data.

5. LIVE CHART

- Display real one-minute OHLC candlesticks.
- Provide 5-minute and 15-minute context for trend confirmation.
- Show support and resistance levels and identify hammer candles.
- Synchronize candle timestamps with the selected data provider.
- Make the chart responsive on Android mobile screens.
- Do not display fabricated candles when the connection fails.

6. TESTING AND PERFORMANCE

- Include historical backtesting using genuine historical market data.
- Separate training/tuning data from unseen test data.
- Avoid look-ahead bias and account for transaction timing.
- Record every signal and its subsequent outcome.
- Report win rate, loss rate, draw rate, number of trades, payout-adjusted expected return and maximum drawdown where applicable.
- Report LIVE and crypto results separately.
- Never invent historical results or claim 85%, 90% or higher accuracy without sufficient verified evidence.
- Test the strategy on unseen data and a demo environment before real-money use.

7. RELIABILITY AND SECURITY

- Add clear loading, error, reconnecting and disconnected states.
- Keep API credentials server-side.
- Validate timestamps, candle ordering and OHLC consistency.
- Do not place trades or access the user's Quotex account.
- Do not add martingale, automatic betting or guaranteed-profit claims.
- Add automated tests for signal rules, candle boundaries, data validation and failure states.
- Build the complete application, run available checks, and fix build errors before reporting completion.

8. FINAL DELIVERY

First inspect the complete requirements, then build the working application with a clean, professional dark trading dashboard.

Before declaring it complete, list:

1. Features actually implemented.
2. Real data providers connected and any required API keys.
3. Features requiring manual setup or paid services.
4. Build and test results.
5. Known limitations, particularly Quotex price synchronization.
6. Steps to test the app safely on demo data from historical sources and then on a verified live feed.

Do not silently omit requirements. Do not claim success for features that have not been implemented and verified.

Me yeh bhej Raha hu

Uses API keys: you add your own after remixing.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.