← All questions
What does a brand-new repo need in its first Loop task?
The stack named directly, where files should go, and what done looks like mechanically, because a new repo has no code for the agent to infer these from.
Name the framework, language and test runner. Give a rough folder convention. If there is no npm test or typecheck script yet, say what verifying the change means until one exists.
Once one real commit exists, later tasks can lean on it the way a mature repo lets every task lean on history.