DATAfest — Team Manual & Checklist

Available in English and Spanish (use the EN / ES toggle, top-right). The product itself is in Spanish. Draft for Diego's review before sharing with the partner.

Welcome. This is how the two of us build DATAfest together. It is written so that someone who has never used tools like this before can follow every step. Nothing here assumes you already know git, terminals, or code. Read it once, then keep it as your reference. Take your time.

1. What DATAfest is (in one breath)

Mission control for the captain. A full operating dashboard for a concert-promotion company: the always-on view of the whole business, plus a live command deck during a festival. Calm authority, total awareness, decisions from live signal.

2. The big picture: how the two of us work

• You (partner): design, ideas, and how DATAfest looks and feels.
• Diego + Claude: the build, the data, security, and the tech underneath.
• Your superpower: you do not need to learn git or write code. Claude is your hands. You think and design; you tell Claude what you want in plain words; Claude does the technical part for you.
• One shared folder: everything lives in a single project folder (called the "repo") that syncs between your computer and Diego's. That shared folder is our common brain. When you save something, it shows up for Diego. When Diego saves something, it shows up for you.

3. Plain-language glossary (read once, refer back anytime)

No jargon. One line each.

• Repo (repository): the shared project folder for DATAfest. Lives online (GitHub) and on each of our computers.
• GitHub: the website that hosts the shared folder online and keeps everyone in sync.
• Clone: make a copy of the online folder onto your computer (you do this once).
• Commit: save a snapshot of your changes, with a short note about what changed.
• Push / Pull: push sends your saved changes up to GitHub; pull brings down the latest.
• Branch / Pull Request (PR): a safe side-copy for a change, and the request to fold it into the main version. Claude handles these for you. You never have to.
• Terminal: the text-command window. You will not need it. Claude uses it for you.
• VS Code: the app where the project opens on your computer. Think of it as the workshop.
• Claude Code: your AI partner inside VS Code. You talk to it in plain language.
• GitHub Desktop: a simple app with buttons that shows you your changes and syncs them with one click. Your visual safety net.
• Inbox: the inbox/ folder. Your front door. Drop any idea here and we pick it up.
• Live Share: a way for us to see the same screen live, with both cursors, when we work apart.
• Secrets / .env: passwords and keys. These never go in the shared folder. Claude handles them the safe way.

4. Your one-time setup

You already run Claude Code in VS Code, like Diego, so this is short: a couple of things only you can do, then Claude sets up the rest.

4A. The few things to do yourself

1. Create a GitHub account. Go to github.com, click Sign up, pick a username (your name is fine), and confirm your email. Send Diego your username so he can add you.
2. Accept the invite. You will get an email invitation to the D-F-inc team. Click Accept. You are now a co-owner of the project.

That is it for your part. From here, Claude does the setup for you.

4B. Let Claude set up the rest (copy, paste, send, one at a time)

In your Claude Code (the one you already use), paste these prompts one at a time and let it work. It will explain each step in plain language and ask before doing anything important. This is the whole point of how we work: you say what you want, Claude does the technical part.

Prompt 1, bring the project in and get Claude up to speed:

"I've logged into GitHub. Please clone our repository D-F-inc/datafest, open it, then read the README.md first so you are up to speed on what we are building and how we work. After that, guide me through my setup in simple terms, and walk me through anything you need from me."

Prompt 2, set up my workbench:

"Set up my workbench for this project. Make sure GitHub Desktop, Git, and the project's recommended VS Code extensions (including Live Share) are installed and configured. Explain what each tool is as you go, and ask me before installing or changing anything important."

Prompt 3, learn the project:

"Read this project's CLAUDE.md and docs/manual.md, then explain to me in simple terms what we are building, what my role is, and exactly how I save and share my work. Keep it short."

Prompt 4, the readiness check:

"Check that everything is set up correctly and tell me whether I'm ready to work. Then give me a short cheat sheet of the plain-language phrases I can say to you to save my work, send it to Diego, and catch up at the start of a session."

If any prompt does something you do not understand, just ask Claude "explain that in simple terms," or message Diego. You cannot break anything by asking.

The "say hello" test

When you can ask Claude "What is DATAfest and how do we work?" and it answers with the mission-control idea and this workflow, you are fully set up. 🎛️

5. How you work, day to day (your smooth loop)

Your whole job, technically, is three moves. Claude does everything else.

1. Have an idea or a design. A sketch, a screenshot, a reference you like, a voice note, a rough thought. Anything.

2. Put it in the inbox. Drag the file into the inbox/ folder, or just tell Claude: "Add this to the inbox: [describe or paste it]." Nothing is too rough. The inbox is for scrappy, half-formed ideas on purpose. We scrap and shape from there together.

3. Tell Claude what you want, in plain words. For example:

   • "Save my work."
   • "Send this to Diego to look at."
   • "Catch me up on what changed since yesterday."

   Claude turns that into the right technical steps (the commits, the branches, the sync).

You never touch git. If you ever want to see your changes with your own eyes, open GitHub Desktop: it lists what changed; click Push origin to sync. That is the only button you ever need.

• Start a session: open the folder, tell Claude "catch me up" (it reads the latest handoff and the inbox).
• End a session: tell Claude "save my work and write a handoff." That passes the baton to Diego (and his Claude) cleanly.

6. How we work together (in person and remote)

We do a mix of both, and the flow works either way:

• In person: we sit together, one screen, and talk it through.
• Remote: we hop on a call and start VS Code Live Share so we see the same screen live, both cursors moving. It feels like sitting together.
• Either way, the shared folder carries everything between us, so even when we are apart our two Claudes stay in sync. The repo is the memory neither chat can see on its own.

7. Who owns what

• You: the design/ space, the look and feel, the flows, the ideas.
• Diego + Claude: the backend, the tools/, security, and infrastructure.
• We review each other's work and pair often. None of this is a wall.

8. The golden rules (short, and they matter)

• Never put passwords or keys in the shared folder. If something is secret, tell Claude and it handles it the safe way (locally, never synced).
• When in doubt, ask. Ask your Claude, or ping Diego. No question is too small.
• Small and often beats big and rare. Save and share little pieces frequently.
• The product is in Spanish. And in any copy we write, no em-dashes.

9. The path to our goals

We move in phases. We do not pre-decide the product; that comes from your design plus research.

Every phase runs the same loop: idea, shape it together, plan, build, review, ship.

10. Your first session with us (what to expect)

The goal of the first session is simple: get you set up and let you see how we work. We will:

1. Walk through your setup (Section 4) live, together: create your GitHub account, then watch Claude set up the whole project on your machine from a couple of prompts.
2. Show you the rhythm: you watch Diego and Claude do a small piece of real work, so you feel how fast and smooth the flow is.
3. Warm up the ideas: bring anything you have imagined for DATAfest. We drop it in the inbox and start scrapping.

No pressure, no prep beyond showing up curious. The detailed run-of-show is in kickoff-session.md.

11. Quick reference card (your cheat sheet)

• Start working: open the folder, then "Claude, catch me up."
• Save an idea: drop it in inbox/, then "Claude, save this."
• Send for review: "Claude, send this to Diego."
• See my changes: open GitHub Desktop, then Push origin.
• Stuck or unsure: ask Claude, or message Diego.

This page is generated from the manual and lives on a private review URL, where you and your partner can leave comments right on it and Claude reads them to iterate.