START HERE · OFFICIAL PROMPT

Clone the TabTin project locally

Have an AI choose a safe local directory, clone the official repository, and prove the source is ready.

Difficulty
Beginner
Stage
Preparation
Version
v1.0.0
Updated
2026-08-31

OUTCOMES

What this Prompt helps you deliver

  • The official TabTin repository is cloned to a known local path
  • The remote URL, current branch, and key files are verified

BEFORE YOU START

Before you start

  • This computer can reach GitHub
  • You have a writable local development directory

What AI should inspect first

README.mdAGENTS.md

READY TO RUN

Complete Prompt

Copy the complete Prompt with its execution and acceptance boundaries.

You are helping me obtain the TabTin source code on this computer for the first time. I plan to build my own product on TabTin rather than contribute upstream. The official repository is https://github.com/tabtin-ai/TabTin. Complete the clone and verification instead of only giving me commands.

Before you begin

Use read-only checks to identify the operating system, current directory, Git availability, and the parent directory that will hold the repository. If I have not chosen a destination, recommend one clear location based on the development directories already present and ask me to confirm it. Never clone into a system directory, temporary directory, or another existing project.

If the destination exists, determine whether it is already the same TabTin repository. Do not overwrite, delete, reset, clean, or force changes in an existing directory.

Work to complete

  1. Confirm that Git is available. If it is missing, explain the customary installation method and obtain approval before a system-level write.
  2. Confirm that the parent directory is writable and has enough free space, then state the final repository path.
  3. Run git clone in the approved parent directory using only https://github.com/tabtin-ai/TabTin.
  4. Enter the repository and verify that origin still points to the official URL. Record the default branch and latest commit.
  5. Verify that README.md, AGENTS.md, package.json, apps, and packages exist.
  6. Stop there. Do not install dependencies, start services, modify source code, create a branch, commit, or push.

Verification and report

Use Git to prove that the directory is a valid, clean worktree with the correct origin. If network, proxy, disk, permission, or credential issues block the clone, identify the exact cause, preserve existing files, and propose the smallest recovery step. Report the absolute repository path, origin, branch, latest commit, key-file checks, and any local configuration changed. Recommend the “Prepare a local TabTin development environment” Prompt as the next step.