agentleFS
marco-bertellimarco-bertelli/filo/skills/page/SKILL.md

page

Skill1 starsChanged 3 days agoMITView on GitHub

Draws or redraws the visual page of a flow that is already decided - the map of who does what in each moment, the life of the main object, the storyboard with the screens, the choices behind it. Use when the user asks to see, show, draw, redraw or refresh the page, the diagram or the picture of a flow, for a flow saved in the project (product/flows) or the one just built in this conversation. It asks nothing and decides nothing. To design a flow or change one, use the flow skill instead.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. WALKERKILLER/Look-Tongji-Notes★ 53same name
    2. ilanbm/kpopper★ 12same name
    3. cmj-hub/claude-landing-page★ 3same name
    4. xabux/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write to the user in their language, and keep their names for things.

    line 10
  2. Very specific:

    The page of this conversation: If a flow-<slug>.html was built earlier in this conversation, the JSON in its flow-data block is the flow.

    line 16
  3. Very specific:

    Start from a fresh copy of the template, outside the repository, as flow-<slug>.html.

    line 24
  4. Distinctive:

    Check that the block parses as JSON.

    line 26
  5. Distinctive:

    Do not restyle the page and do not draw diagrams by hand: the page draws them from the data.

    line 29
  6. Distinctive:

    No "The flow in words": Write it from the purpose, the steps and the choices with their "Why", as the template's comment describes.

    line 46
  7. Very specific:

    No "new / changed / same": Leave every step as same.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Page

Draw the page of a flow that already exists. Nothing is decided here: no interview, no new choices. If what you read does not hold together, draw it as it is and say so in one line. Changing a flow is the flow skill's work.

Write to the user in their language, and keep their names for things.

Which flow

Take the first that applies:

  1. The page of this conversation. If a flow-<slug>.html was built earlier in this conversation, the JSON in its flow-data block is the flow.
  2. A saved flow. product/flows/<slug>.md in the repository, or wherever the project keeps its flows (its instruction files say). With one file, take it. With several and no name given, list them in one line and ask which.
  3. Neither. Say there is no flow to draw yet, and that /filo:flow builds one.

Drawing it

The page comes from ../flow/assets/flow-page.html (paths are relative to this skill's folder), and the rules for it are in "4. The page" of ../flow/SKILL.md. In short:

  1. Start from a fresh copy of the template, outside the repository, as flow-<slug>.html. Do this even when a page already exists: the template may have changed since, and the old data moves into the new one.
  2. Change only the <title> and the JSON in the flow-data block. The comment above the block explains every field. Translate labels into the user's language.
  3. Check that the block parses as JSON.
  4. Publish it with the environment's page tool if there is one (in Claude Code, the Artifact tool, following its rules). Otherwise give the file's full path.

Do not restyle the page and do not draw diagrams by hand: the page draws them from the data.

From a saved flow file

In the fileIn the data
Purposevalue
The flow in wordssummary[]: each part's title and text
Actors, Flowactors[] and their steps[]: keep the ids; the step's "new / changed / same" is change, its "Screen" line becomes the screen blocks, "Today" is today, the cases under it are branches
Pathspaths[]
Life of ...states
Choicesdecisions[]; "By" gives by: the user is you, proposed and accepted is me, decided before is before
Coveragecoverage[]
Out of this flowout[]

A file saved by an older version may lack some of this. Then:

  • No "The flow in words". Write it from the purpose, the steps and the choices with their "Why", as the template's comment describes. Do not invent reasons the file does not give.
  • No paths. Build them from the scenarios and the order of the steps: one path per moment, alternatives in separate paths. Say that you did.
  • No screen lines. Sketch a screen only from what the step's text says is on it. Do not invent controls.
  • No "new / changed / same". Leave every step as same.

From the page of this conversation

Move its JSON into the fresh template. If it was written for an older template (steps with next or apart, no paths), write the paths from what the session decided and drop the old fields.

What to write with it

Where the page is, and one line on anything you had to rebuild or could not draw. Nothing else: the page is the answer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.