Multi-file Refactor

Use Flowise to change a cross-cutting concern while preserving behavior, optimized for visual LLM and agent flows.

Id: flowise/multi-file-refactor · Status: Untested · FREE · Primary action: COPY / USE (not a live RUN claim).

What is this

A FREE Flowise resource. Open the full body below, copy it, and use it in a compatible AI surface you control.

What you can do now

Copy the complete instructions and fill in the placeholders ([GOAL], [INPUTS], [CONTEXT_OR_FILES], [CONSTRAINTS]) with your real material.

Full FREE body

Back to Flowise

Pack body is English. UI language controls translate chrome labels only.

You are handling **Multi-file Refactor** in Flowise.

GOAL
[GOAL]

INPUTS
[INPUTS]

CONTEXT / ASSETS
[CONTEXT_OR_FILES]

CONSTRAINTS
[CONSTRAINTS]

EXECUTION
1. State the concrete objective and identify only missing information that would make execution unsafe or materially unreliable. Continue without blocking on optional details.
2. Inspect/analyze the supplied context before changing anything or drawing conclusions.
3. Specify ingress-to-output graph, logical nodes, inputs/outputs, connections, tools, memory scope, retrieval and fallbacks; include tests.
4. Keep evidence, assumptions and unknowns separate. Never invent files, source facts, tool results, metrics, test results or completed actions.
5. Produce the actual artifact for this task; do not return generic advice about how to do it.
6. Verify the artifact against [CONSTRAINTS] and the requested outcome before returning it.
7. For this use case specifically, ensure the result can change a cross-cutting concern while preserving behavior and includes concrete validation or acceptance criteria.

TARGET-SPECIFIC RULE
Make the graph reproducible; distinguish prompts, retrieval, tools, memory, routers and terminal output.

OUTPUT CONTRACT
RESULT: [completed | blocked]
DELIVERABLE: [Flowise blueprint with node graph, prompt payloads, connections, boundaries, fallbacks and tests]
VALIDATION: [checks performed / evidence used]
ASSUMPTIONS: [material assumptions only]
REMAINING: [none, or exact unresolved issue]

PLACEHOLDERS
[GOAL] desired outcome
[INPUTS] raw task material
[CONTEXT_OR_FILES] repository, documents, data, workflow context or API constraints
[CONSTRAINTS] scope, format, safety, compatibility, privacy, budget or policy constraints

Related FREE resources

Discovery links only — not a claim that BSV executes these together.

All Library Flowise shelf