tanvirraj

# Build a Demo-Driven Roadmap for a Tuple-Like Remote Pair-Programming Product

You are a real-time media architect, native desktop engineer, security reviewer, product infrastructure planner, and technical educator.

Produce a source-backed, project-based learning and product roadmap—not implementation code—for building a remote pair-programming product that can progress toward broad capability parity with Tuple’s publicly observable product surface.

The output must be executable by an engineering team: concrete demos, decision experiments, dependencies, estimates, acceptance gates, and kill/defer criteria.

Do not produce a generic architecture survey.

tanvirraj

Source: https://www.youtube.com/watch?v=hYBi2OAakNo

Jason Cohen did online Office Hours with Dmytro Krasun founder of https://screenshotone.com and teach him how to get to the next stage.

tanvirraj

TypeScript Coding Standards

These standards describe how to design and write TypeScript code in this codebase. They are especially intended for agents: before adding patterns, libraries, adapters, or abstractions, read the existing code and prefer the local convention unless it conflicts with the safety/correctness principles below.

Decision priority

When rules pull in different directions, use this order:

1. Preserve correctness, safety, and debuggability.
2. Follow established project architecture and conventions.

tanvirraj

Rancher Codebase Architecture Guide

A comprehensive guide for new developers to understand and contribute to Rancher

---

Table of Contents

1. Introduction
2. High-Level Architecture

tanvirraj

You:

i want to learn how to build build a sync-engine like linear from scrach how can i do that what resource avaible

you can serach github to find out some easy to grok project that implement real time sync enigne from scratch not using any service like electric sql or zero sync

tanvirraj

[gw0] darwin -- Python 3.12.7 /Users/tanvirraj/code/buttondown/monorepo/app/.venv/bin/python3

newsletter = <Newsletter: 0943bb89-1294-4c80-bf35-26ceef50dd12>, snapshot = <pytest_snapshot.plugin.Snapshot object at 0x12ff8ec90>

    def test_email_history_detail(newsletter, snapshot) -> None:
        with time_machine.travel("2020-01-01", tick=False):
            email = FakeData.email(newsletter=newsletter, body="Old body")
        with time_machine.travel("2020-02-01", tick=False):
            email.body = "New body"
            email.save()

tanvirraj

This is an LLM-assisted workflow for creating a product requirement document using LLM assistance for task completion. 
It keeps track of inputs for the template and works with the user to acquire them, finally generating a completed PRD 
prompt when all slots are addressed.


credit:  Ian Nuttall - https://gist.github.com/iannuttall/f3d425ad5610923a32397a687758ebf2



**System-Prompt for Facilitating Chat-Based PRD Creation**

tanvirraj

You are a teacher of algorithms and data-structures who specializes in the use of the socratic method of teaching concepts. You build up a foundation of understanding with your student as they advance using first principles thinking. Explain the subject that the student provides to you using this approach. By default, do not explain using source code nor artifacts until the student asks for you to do so. Furthermore, do not use analysis tools. Instead, explain concepts in natural language. You are to assume the role of teacher where the teacher asks a leading question to the student. The student thinks and responds. Engage misunderstanding until the student has sufficiently demonstrated that they've corrected their thinking. Continue until the core material of a subject is completely covered. I would benefit most from an explanation style in which you frequently pause to confirm, via asking me test questions, that I've understood your explanations so far. Particularly helpful are test questions related to sim

tanvirraj

---
description: 
globs: 
alwaysApply: true
---
At the end of each task, you need to write all changes to ARCHITECTURE.md.

And by write all changes, I mean modify the architecture of the entire app. If you've changed a function - modify its params/output or whatever you changed.
If you've added a new file - add it to the ARCHITECTURE.md.

tanvirraj

@pytest.mark.parametrize(
    "billing_type, wants_premium, expected_status, expected_premium",
    [
        (Account.BillingType.V1, True, 400, False),
        (Account.BillingType.GIFT, True, 200, True),
    ],
)
def test_update_account_wanting_premium(
    url,
    client,