agentleFS
Sign inStart free
reescalderreescalder/claude-skills/vertical-fanned-cards/SKILL.md

vertical-fanned-cards

Skill0 starsChanged 4 months agoMITView on GitHub

Vertical fanned card carousel where cards stack and fan vertically. Active card centered, adjacent cards peek above/below (dimmed, scaled). Auto-cycles when scrolled into view, stops on user interaction. Swipe up/down navigation.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use useInView from Framer Motion for auto-cycle trigger

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Vertical Fanned Cards

A vertical card carousel where the active card is prominent and adjacent cards peek from above and below, creating a fanned/stacked effect. Auto-advances when visible.

When to Use

  • Side-by-side content displays (two carousels next to text)
  • Compact card browsing in constrained width
  • Portfolio / timeline items in vertical layout
  • Any content that benefits from vertical card browsing

Props

PropTypeDefaultDescription
itemsT[]requiredArray of data items
renderCard(item, index, isActive) => ReactNoderequiredCard renderer
cardHeightnumber155Height of each card in px
overlapnumber22How much adjacent cards overlap

Behavior

  • Swipe up/down (30px threshold) to navigate
  • Click any visible card to jump to it
  • Auto-cycles every 2.5s when scrolled into view
  • Auto-cycle stops permanently on any user interaction
  • Vertical pagination indicators (dot indicators) along left edge, active dot stretches to pill
  • ▴/▾ arrow buttons for click navigation

Key Lessons

  • cardHeight - overlap determines the vertical spacing between card centers
  • Cards beyond 2 positions from active should be opacity: 0 to prevent pile-up
  • Use useInView from Framer Motion for auto-cycle trigger
  • Track userInteracted state to disable auto-cycle permanently once touched
  • Visible container height = cardHeight + overlap * 2 + 20

Reference Implementation

See reference/VerticalFannedCards.tsx

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.

Check your setup, free