agentleFS
VinayKhandiaVinayKhandia/no-slop/skills/storyboard/SKILL.md

storyboard

Skill1 starsChanged 12 days agoMITView on GitHub

Use before building any immersive, 3D or motion-heavy site. Plans the page like a short film (scenes, camera moves, transitions, pacing, one signature moment) so the result feels directed instead of assembled from sections.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use acquisition-channel-advisor, altitude-horizon-framework and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nandanosqlSkill

    acquisition-channel-advisor

    Evaluate and recommend customer acquisition channels based on product type, target audience, budget, and stage — covering organic, paid, referral, partnerships, and product-led growth.

    Also in 3 projects that use this

  • nandanosqlSkill

    altitude-horizon-framework

    Navigate between strategic (30,000 ft) and tactical (ground level) thinking using the Altitude-Horizon framework — knowing when to zoom in vs. out and adjusting communication to the right level.

    Also in 3 projects that use this

  • +10 more from nandanosql

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write: "Signature: <what>.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 16 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

Storyboard

Sites feel generic when they are a stack of sections. Wow comes from a directed sequence. Write STORYBOARD.md before any code.

1. The signature moment (exactly one)

The one thing a visitor will describe to a friend. It must be specific to this product, driven by scroll or interaction, and doable at 60fps. Examples: scrolling pours the cup and the liquid level is the progress bar; the camera flies through a perfume bottle's glass into the next scene; the page descends through depth zones with a live depth meter; headline letters assemble into the product; the object explodes into parts with spec callouts and reassembles. Write: "Signature: <what>. Mechanism: <what scroll drives, what the visitor sees, what changes>."

2. Structure

Pick one archetype and say why: Descent, Turntable, Walk-through, Shelf, Type storm, Focus tour, Portal chain.

3. Shot list (5 to 8 scenes)

For every scene write:

  • Name and length in viewports of scroll
  • Camera: position, move, FOV
  • Hero object state and environment or light change
  • Text beat: the final headline and supporting line, plus its screen zone
  • Entry transition and exit transition
  • Interaction available
  • Intensity: calm, build, peak or release

4. Pacing

Calm opening, build, one PEAK (the signature, placed at 55 to 70 percent of the scroll), release, then a clear call to action. Never two peaks in a row. One focal point per scene. First interaction available within one second.

5. Transition toolkit (different type at each boundary, at most 3 types per page)

  • Camera fly-through: the camera path continues into the next environment, with fog or shared geometry hiding the join.
  • Shader dissolve or wipe: render two scenes to render targets and mix them with a progress uniform and a noise threshold.
  • Clip-path portal: a circle or shape expands from the hero object into the next scene.
  • Object morph: the hero changes variant or deforms while the environment shifts.
  • Depth-sandwich shift: the ghost wordmark scales past the camera as the next scene emerges.
  • Pinned scrub: one viewport changes state across scroll, with a step indicator.
  • Color wash: background and light lerp through a palette midpoint.
  • Focus pull: depth of field or blur shifts from one layer to another.
  • Scale-through: zoom into a detail that becomes the whole next frame. For each boundary write: type, scroll range, duration and ease, and the CONTINUITY ELEMENT, something that stays on screen across the cut so scenes feel connected.

6. Copy

Final headlines, no placeholders. Maximum 12 words per headline. Voice follows the style. No jargon unless the product is technical.

7. Output: STORYBOARD.md

Signature and mechanism, archetype, shot-list table, transition map, a one-line intensity curve (for example calm, build, build, PEAK, release, close), asset list (models, textures, images, with a fallback for each), performance budget per scene.

8. Final check

  • One signature moment with a clear mechanism.
  • 5 to 8 scenes, each with camera, text, entry and exit transition.
  • Every boundary has a continuity element.
  • Exactly one peak.
  • Copy is final, assets have fallbacks.

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.