How do I install the Flora Canvas Iterate skill?

Run npx skillmds@latest add florafauna-ai/flora-canvas-iterate-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flora Canvas Iterate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flora Canvas Iterate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flora Canvas Iterate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flora Canvas Iterate?

florafauna-ai (@florafauna-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flora Canvas Iterate by florafauna-ai

Name: Flora Canvas Iterate
Author: florafauna-ai

Flora Canvas Iterate

Find and build on work that already exists in a FLORA project — inspect a canvas, review past generations and what they cost, and regenerate specific assets with new direction applied. Use when the user refers to a named project, "my canvas", or earlier work ("the hero images from last week", "what's in the Meridian project"). Do not use to start new work in an empty project.

florafauna-ai Updated Sep 21, 2026

File contents

Iterate on existing FLORA work

A FLORA project outlives the conversation. Its canvas, every generation, and the cost of each are all still there, so revision starts from what exists rather than from a blank prompt.

Input: a project reference and the change wanted. Output: what is on the canvas today, plus any regenerated assets.

Steps

Find the project. flora_list_projects (most recently active first) and match on the user's wording. Never create a project when the user named an existing one — ask if the name is ambiguous.
Read what is there. flora_get_canvas for structure and how nodes connect; flora_list_canvas_nodes for the media nodes and their asset URLs. Use flora_list_generations to see what was made, with cost and status.
Identify the assets the user means. Name them back before changing anything. "Two hero images, both generated Tuesday" is confirmable; "the ones you meant" is not.
Apply the change. Regenerate with flora_generate, or re-run the original technique with flora_run_technique when the asset came from one — flora_list_technique_runs shows which technique produced what.
Report the new outputs, their cost, and where they landed on the canvas.

Rules

Read before writing. The user may have edited the canvas between turns.
Additive only. Regenerating adds new nodes; it does not replace the originals. Say so, so the user knows the earlier version is still there.
Confirm before spending. State the cost of the regeneration and wait.
You cannot see any asset. You have URLs, node labels, and generation metadata. Reason from those; never claim to have looked at the artwork.
Prefer the narrowest read that answers the question. A whole-canvas dump on a large project is mostly noise.

---name: flora-canvas-iterate-2description: Find and build on work that already exists in a FLORA project — inspect a canvas, review past generations and what they cost, and regenerate specific assets with new direction applied. Use when the user refers to a named project, "my canvas", or earlier work ("the hero images from last week", "what's in the Meridian project"). Do not use to start new work in an empty project.---# Iterate on existing FLORA workA FLORA project outlives the conversation. Its canvas, every generation, and thecost of each are all still there, so revision starts from what exists rather thanfrom a blank prompt.**Input:** a project reference and the change wanted.**Output:** what is on the canvas today, plus any regenerated assets.## Steps1. **Find the project.** `flora_list_projects` (most recently active first) and match on the user's wording. Never create a project when the user named an existing one — ask if the name is ambiguous.2. **Read what is there.** `flora_get_canvas` for structure and how nodes connect; `flora_list_canvas_nodes` for the media nodes and their asset URLs. Use `flora_list_generations` to see what was made, with cost and status.3. **Identify the assets the user means.** Name them back before changing anything. "Two hero images, both generated Tuesday" is confirmable; "the ones you meant" is not.4. **Apply the change.** Regenerate with `flora_generate`, or re-run the original technique with `flora_run_technique` when the asset came from one — `flora_list_technique_runs` shows which technique produced what.5. **Report** the new outputs, their cost, and where they landed on the canvas.## Rules- **Read before writing.** The user may have edited the canvas between turns.- **Additive only.** Regenerating adds new nodes; it does not replace the originals. Say so, so the user knows the earlier version is still there.- **Confirm before spending.** State the cost of the regeneration and wait.- **You cannot see any asset.** You have URLs, node labels, and generation metadata. Reason from those; never claim to have looked at the artwork.- Prefer the narrowest read that answers the question. A whole-canvas dump on a large project is mostly noise.

Frequently asked questions