Plan your code refactoring

Draw the current flow and note what needs to change in each block.

No sign-up. Your data is saved only in your browser.

Block-based flow

Connect blocks to describe processes, conditions, and error paths.

Before and after

Compare the current behavior and code with what you want to change.

Alternative paths

Name each output to explain when to follow that path.

Export

Keep a copy in JSON or share the full scenario as a PDF.

How to plan a refactoring in Refina

1. Describe the current flow
Create a use case and split it into scenarios. Connect processes, conditions, and error paths to record how the code works today.
2. Record what will change
Mark the blocks to keep, adapt, remove, or add. Compare the current code with the proposed code and note the acceptance criteria.
3. Review and share
Check the connections and the field mapping. Export the scenario as a PDF for review or as JSON to continue working on another device.

Field mapping between data structures

When you change an API contract or a data structure, record where each field comes from and where it goes. Refina reads structures in Go, Protobuf, TypeScript, and JSON. You can specify new fields, removed fields, and conversion rules in the same scenario as the flow.

Questions about Refina

Does Refina change my code?

No. You describe the current behavior and the proposed change. Implementation and test runs stay in your development environment.

How do I keep a copy of the project?

Use the JSON export to save the workspace data and import it later. Do this before clearing site data or switching devices. The PDF is for reading and review, not for restoring the project.

Can I draw a new flow?

Yes. When you create a use case, choose between mapping an existing flow and drawing a new one. Templates with conditions, integrations, loops, and waits are available as starting points.