The way I - a non-designer - understand this, these flow cards are not wireframes as such, where the intention would be to structure the information/content presented to the user on a page.
Instead, I view these as basically standardized "icons" - a visual language - with each depicting a function/meaning of one page (or step) in a flow. For example, you could have a "landing page" flow card, "account login" flow card, "home dashboard" home card, depicting the user flow when accessing their account.
It doesn't matter what the actual wireframe layout is at that point, as this is for a step before that, where you want to see what are the steps the user follows to do a specific thing.
I might be completely off the mark here, but if that's the intention: preparing a smaller, well defined and named set of cards, basically designing a language for this, would be clearer. As a non-designer, mixing the semantic value of the cards (if understood as icons) and the actual layout on each of the card (a step toward wireframing) makes it more confusing. Limiting the number of choices would force the designer(s)/stakeholders to focus on the meaning, not the mechanics.
Instead, I view these as basically standardized "icons" - a visual language - with each depicting a function/meaning of one page (or step) in a flow. For example, you could have a "landing page" flow card, "account login" flow card, "home dashboard" home card, depicting the user flow when accessing their account.
It doesn't matter what the actual wireframe layout is at that point, as this is for a step before that, where you want to see what are the steps the user follows to do a specific thing.
I might be completely off the mark here, but if that's the intention: preparing a smaller, well defined and named set of cards, basically designing a language for this, would be clearer. As a non-designer, mixing the semantic value of the cards (if understood as icons) and the actual layout on each of the card (a step toward wireframing) makes it more confusing. Limiting the number of choices would force the designer(s)/stakeholders to focus on the meaning, not the mechanics.