PM Pro Tips: Getting the Most Out of Fei Studio

Last updated: March 25, 2026

Fei Studio works best when you treat it like a real collaboration partner.

Based on hands-on experience building Fei with Fei, here are practical tips to help you move faster, get better results, and stay in control.

Think in “one ticket at a time”

Approach each task as if you’re handing over one clear product ticket to a frontend developer.

  • Focus on a single feature, screen, or behavior.

  • Avoid mixing unrelated ideas in the same task.

  • If you want to explore a different direction - start a new task.

Why it helps:

Clear scope leads to clearer plans, better previews, and fewer surprises.

Batch changes - just number them clearly

When reviewing a component in the preview, you can ask for multiple changes at once.

Best practice:

  • Put all small changes in one request

  • Number each change clearly

Example:

  1. Increase spacing between list items

  2. Add a filter dropdown above the list

  3. Align the empty state message to the center

Why it helps:

When changes are sent together, it saves multiple rendering efforts, and if they are structured Fei understands them much better - just like a human developer.

You can change the preview itself to test ideas better

The preview isn’t just for looking - it’s a tool for thinking and testing.

You can ask Fei to adjust the preview so you can validate behavior more clearly:

Add mock data

Ask for specifics:

  • Number of rows

  • Different statuses

  • Edge cases

View the component as a specific role

Example:

“Show this as an admin user”

Show all states of a component

Hover, loading, empty, error, success — all at once if needed.

Include additional components in the preview

If a change affects more than one component, ask to preview them together.

Use sliders when you’re unsure

Not sure about spacing, width, or size?

  • Ask Fei to add to the preview a slider for the specific property (or even a hovering modal of a few slider controls to play with)

  • Play with it live in the preview

  • Ask Fei to apply the specific values you liked the most

  • Lastly ask Fei to remove the sliders

Add reset or control buttons

For time-based or one-time actions, ask for:

  • Reset buttons

  • State toggles

  • Context switchers (e.g. different tasks, users, scenarios)

Example:

“Add to the preview buttons to switch between three tasks so I can test persistence.”

“Show, don’t explain” when something’s off

If Fei says it fixed something but the preview doesn’t match what you expected:

  • Take a screenshot of the preview

  • Attach it

  • Explain what’s wrong by pointing to the image

Treat it like feedback to a real teammate:

“This isn’t what I meant - the button should be below the list, not inside it. See attached screenshot from the preview”

If things go wrong - go back, don’t patch

If Fei:

  • Misunderstood the request

  • Fixed one thing but broke another

Don’t fight the result.

Instead:

  1. Jump back to the last version you liked

  2. Rephrase the request more clearly

  3. Try again

This is usually faster (and cleaner) than stacking fixes on a shaky version.

Use planning mode when clarity matters

If Fei doesn’t quite get what you want:

  • Switch to plan mode

  • Let Fei ask follow-up questions

  • Review the plan (or even the Task Spec Doc) before it builds

This is especially useful for:

  • Complex flows

  • New components

  • Behavior-heavy features

Think of it as a quick design alignment before implementation.

Use Fei for early exploration - not just execution

Fei isn’t just for implementing a decided solution. You can use it to explore different layout and structure options early on.

  • Describe the goal of the screen or feature, let Fei generate a first version

  • Ask for alternative layouts or directions.

  • Each option becomes a live version you can preview, compare, and iterate on.

This is a great way to walk into design reviews with real options instead of abstract ideas.

👉 Learn more: 📄 Exploring Ideas and Layouts with Fei Studio

Use flags and experiments to keep momentum (and learn faster)

When a change depends on backend work or when you want to validate different ideas with real users, Fei can work with your existing feature flag and A/B testing infrastructure.

This tip applies only if your codebase already uses feature flags and/or experimentation tools. Fei builds on what you already have.

Unblock backend-dependent work with feature flags

If backend work isn’t ready and you don’t know when it will land, don’t let the frontend wait.

Ask Fei to:

  • Wrap the UI change behind a feature flag

  • Keep the feature off by default until the backend is ready

This allows you to:

  • Ship frontend changes safely

  • Avoid UI code going stale

  • Turn the feature on instantly when the backend is done

Explore and validate ideas with A/B testing

If your team already uses an A/B testing framework, Fei can help you turn exploration into real experiments.

Ask Fei to:

  • Create two or more UI variants or flows

  • Wire them into your existing A/B setup

Use this to:

  • Compare layouts, copy, or interactions

  • Test different flows with real users

  • Make decisions based on behavior, not opinions

Remember the preview tip?

Ask Fei to let you toggle between flag states or A/B variants, or to show all options side by side in the preview, and verify all states before shipping.

Final thought…

Fei works best when you:

  • Stay focused

  • Be explicit

  • Use the preview as a thinking tool

  • Design UI changes so they can ship even when backend work isn’t ready

Treat Fei like a real collaborator - that’s when ideas move fast and stay high quality 🚀