YFlows documentation
YFlows docs
YFlows is a free yoga sequence editor and pose library. These pages cover how to write a sequence, how the pose library is organized, and how to use the API.
Start here
New to YFlows? Read Your first sequence. It walks through the pose library, a sample floor series, and how to create and edit a sequence in the text format.
When you are ready to write or edit text by hand, use the canonical Sequence Text Format (v0.2) guide. A short reference is included below.
Guides
| Page | What it covers |
|---|---|
| Your first sequence | A short walkthrough for creating a sequence, plus a sample floor series in the text format. |
| Sequences | How a sequence is made of subsequences, optional types and repetitions, common names, and sequence cues (as opposed to pose-library cues). |
| Sequence Text Format (v0.2) | The canonical grammar for delimited sequence text: headers, variations, cues, directions, and repetitions. |
| Poses and pose data | How the pose library is organized: one pose with many common names, images, and cues. |
| YGroups | A group-practice feature in development, with a target of late Q2 2026. |
Sequence text format
The full rules live in the Sequence Text Format (v0.2) spec. This is a compact reference.
Subsequence header
A sequence is one or more subsequences separated by a blank line (\n\n). Each block has a header, then a comma-separated list of pose variations:
[SubsequenceName::SequenceType](Repetitions)
variation1, variation2, variation3
SubsequenceNameis required.::SequenceTypeis optional. If you include a type, it must be one of the predefined names (see below).(Repetitions)is optional and uses the repetition syntax below.
Confirmed subsequence types:
Complete, Cooldown, Floor, Flow, Ground, Intro, Rest, Starting, SunA, SunB, SunC, Standing, Warmup
To request a new type, contact YFlows (see Help & contact).
Pose variation
[TransitionCues]CommonPoseName:Direction(VariationName)[VariationCues]
CommonPoseNameis required and must match a library common name exactly (English, Spanish, Sanskrit, or an acronym). Acronyms are written in ALL CAPS; other names are lowercase.:Ror:Lis an optional side. Those are the two accepted direction markers.(VariationName)is an optional label for this occurrence of the pose (it does not have to be a library name).- Transition cues come before the name, in square brackets. Variation cues come after, also in square brackets. Sequence cues are free text; they are not the same as pose-library cues.
Pose-library cue type codes
Cues stored on a pose in the library use these types (from the poses API):
| Code | Type |
|---|---|
A | Alignment |
B | Breath |
F | Feel |
Z | Anatomical |
These codes apply to pose-library cues, not to the free-text [cues] written in sequence text.
Repetition ranges are slices
Repetitions use this pattern:
[Summary] RepetitionType(Count)[StartIndex:EndIndex]
- Types:
Right/Left,Left/Right,Repeat, orSingle(no repetition; this is the default). - Count, such as
(2), is optional. - A summary in square brackets, such as
[Warm-up], is optional.
The optional range [StartIndex:EndIndex] is a slice of that subsequence’s pose list, in the same way as a Python list slice: 0-based and end-exclusive (like poses[start:end]). Both [0:3] and [1:3] are valid; they simply select different poses.
Take this four-pose subsequence:
[Standing Poses::Standing](Right/Left(1)[1:3])
mountain,
warrior I:R,
triangle:R,
mountain
| Index | Pose |
|---|---|
0 | mountain |
1 | warrior I:R |
2 | triangle:R |
3 | mountain |
[0:3]selects indexes 0, 1, and 2:mountain,warrior I:R,triangle:R.[1:3]selects indexes 1 and 2:warrior I:R,triangle:R(not either mountain).
The last index is never included. [1:3] is not “poses 1 through 3”; it is “from index 1, up to but not including index 3.”
For developers & agents
Start with the machine-readable agent guide at /llms.txt. It describes how to resolve pose names, validate delimited_text, and create or update sequences.
- API usage guide — setup and examples. Sign-in required.
- Sequences schema — JSON summary of the data model, delimited-text rules, and sequence endpoints. Public.
- Poses schema — JSON list of pose-library endpoints. Public.
- Sequences OpenAPI — interactive docs for create/update/validate. Sign-in required in the browser.
- Poses OpenAPI — interactive docs for the pose library, cues, and common-name search. Sign-in required in the browser.
API keys are created in Account Settings (sign-in required). There are separate permissions for managing sequences and managing poses. Send the key as Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY. Keys expire 30 days after creation, and the raw key is shown once when you create it.
Pose library & data
Browse the pose library for the current poses and their common names. Background on how poses, names, images, and cues are structured is in Poses and pose data.
Individual pose information (names, descriptions, anatomical details, and basic instructional content) is available under the Creative Commons Attribution-ShareAlike 4.0 license (CC-BY-SA 4.0). The Terms of Service have the full license terms, including how sequence data is treated (that is separate from the pose data license).
To request a manual download of the pose data, use the contact address shown when you are signed in, or the contact page.
Help & contact
- Contact — the address for signed-in users is shown on this page.
- About YFlows
- Public sequences
- Blog
- Privacy Policy
- Terms of Service
yflows