Soma Intelligence answers questions about your athletes. Projects tell it how you want those questions answered, every time.
A project is a saved workspace holding two things: instructions, which is how you want it to behave, and project knowledge, which is what it reads before every response.
The difference projects make
Without a project, you ask a question and get an answer built on general knowledge plus whatever your data shows. It will be reasonable. It will also fill gaps, average across things that should not be averaged, and turn four results into a confident finding, because nothing has told it not to.
With a project, the same question is answered against your data, the Soma method, and a set of rules about what counts as a good answer. Same connector, same data, a very different response.
Ask about a baseline that does not exist and it tells you the plan ran without baseline comparison switched on, instead of substituting an average that looks like an answer.
Ask why an athlete slowed and it reads reaction time, accuracy and variation separately, because a task that slowed while gaining accuracy is trading speed for control rather than getting worse.
Every figure arrives with the result count behind it, so four results reads as a signal rather than a finding.
And it produces the same document every time. Two athletes, two reports, identical in structure and different only in the data.
The four projects
Soma Project. Ask anything about your athletes or about the method. Answers come from your data and a 42 page knowledge document covering the whole framework.
Soma Report Project. Reviews the block that finished and builds the one that follows, as a document you can send on.
Soma Periodisation Project. Lays out a year of cognitive training, block by block, around your season.
Soma Baseline Report Project. Turns a finished block into a full baseline review. Overall, every task, every minute and every hour.
Each is a separate project. Set up the ones you need and ignore the rest.
Every one is built and ready to load, so there is nothing for you to write. New projects are added as the method develops and appear in your Hub folder as they land, and the existing ones are updated in place, so what you set up today keeps improving without you rebuilding it.
The project files come with Hub membership, alongside [everything else the Hub includes].
How to set up any project
Download the project files. Sign in to the Hub and open the folder for the project you are setting up.
Connect Soma to Claude. See Connecting Soma to Claude if you have not done this yet.
Create the project. Projects in the sidebar, then New project. Name it after the project you are adding.
Paste the instructions file into Instructions. Every project folder has one, and it goes in Instructions, not project knowledge.
Upload everything else into Project knowledge. The knowledge document, and the example documents where the project has them. The examples are the templates the output is built from, so do not skip them.
Start asking.
Five minutes per project, once.
Make it yours
The files are a starting point. Once they are in your project they are yours, so open the instructions or the knowledge document and edit either.
Upload your logo to project knowledge and it appears on every document. A font that renders cleanly on any background is supplied. If you would rather use your own, attach the font file to the message where you ask for the document.
If you keep asking for the same change to how something is written, put it in the instructions rather than repeating it every time. That is what the file is for.