- Home
- Skills
- Mobile Development
- Feature Flow
Feature Flow
A seven-step flow for building one feature, or rethinking part of an app, from the user's idea to a build they have tried on their own device.
$5
Works with the AI Agents you already use
Feature Flow
Example session with this skill installed
Our workout sessions take too long because endurance, strength and mobility all go into one session. I was thinking we could split them into different kinds of days.
- Read your context and instructions
- Compiled the feature flow
Step 1 · The problem, restated
What you experience: a session runs long, and the endurance part doesn't raise your heart rate.
Why the code does it:
TodayBuilder.swiftexpands every exercise into one block per quality you switched on, so three qualities triple the session.- The "endurance" block is the same exercise two steps easier for high reps. That is muscular endurance, not cardio.
What must not change (from the feature map's Watch out lines):
- Only a test moves a level.
- Every setting lives in the profile tab.
- The Android port and the watch app compute today the same way as iOS.
Does this match what you meant?
Step 2 · Decisions so far
Plan doc: docs/features/day-types.md
| Date | Topic | Decision | Why |
|---|---|---|---|
| 2026-11-05 | Day types | Strength, conditioning and rest days | Keeps each session short |
| 2026-11-05 | Conditioning | Interval sessions with bodyweight moves | Works at home with no equipment |
| 2026-11-05 | Existing users | "Endurance on" becomes one conditioning day a week | Keeps their intent |
Rule that follows: the weekly split must count strength days only, or five days with two conditioning still reads as a five-day split.
Next
Step 3: the flow in FigJam. It branches at Today into a strength day, a conditioning day and a rest day, and numbers 9 screens for step 4. Shall I draw it?
Connects securely to your tools. The creator never sees your data.
About this skill
A seven-step flow for building one feature, or rethinking part of an app, from the user's idea to a build they have tried on their own device. Each step ends with the user's approval, so nothing gets built that wasn't agreed.
What it does
| # | Step | Ends with |
|---|---|---|
| 1 | Understand | The problem restated in terms of how the code works today, with the features it touches and their Watch out lines |
| 2 | Research and decide | A dated plan doc: domain research, competitor patterns from Mobbin, platform rules, and each decision settled one at a time |
| 3 | Flow | A FigJam flow of every path and state, numbered into the plan doc's screen list |
| 4 | Design | Each numbered screen drawn in Figma from the design system, in every state, passing the design audit |
| 5 | Build | Code on every platform the app ships, with the feature map updated in the same change |
| 6 | Test | Unit tests for every rule in the plan doc, platforms kept in step, verifier passing |
| 7 | Validate on device | A build on the user's phone with a short checklist, their findings fixed, the feature marked shipped |
How to use it
Propose a feature the way you would to a teammate: "I was thinking we could add rest days", or "this session takes too long, maybe we should split it". The agent starts at step 1, or at the step you name ("draw it" starts at the flow, "build what we decided" at step 5).
It never commits, pushes, uploads or submits to a store without a separate yes for each.
Requirements
- Figma: the Figma MCP server (FigJam for the flow, Figma for the screens) and Figma's skills (figma-use, figma-generate-design, figma-generate-diagram, figma-use-figjam). Steps 3 and 4.
- Mobbin: the Mobbin MCP server for competitor research. Step 2.
- Your platform's build tools (Xcode, Gradle, npm) and your own device for step 7.
- Works best on top of App Foundations: a feature map, verification hooks and a Figma design system. Without them it says what is missing and offers to set it up first.
Both are also sold together in the App Foundations + Feature Flow bundle.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Steps 3 and 4 need the Figma MCP server, and step 2's competitor research uses the Mobbin MCP server. Step 7 needs your platform's build tools and your own device. Without the App Foundations setup (feature map, verifier hooks, Figma library) the flow still runs, but it checks less and tells you what it is skipping.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 12 days ago
- Accounts
Figma MCP
- Software
Mobbin MCP
XcodeorGradleornpm
Use the build tools for your platform.
Permissions
Allowed Hosts