LocalStash

Use cases

What people actually keep in a swipe file

Everyone says “save your inspiration” and leaves it there. The useful question is narrower: what does a product designer save that a frontend engineer does not, and what does each of them throw away? Six setups, with the tags, the weekly habit and a starter kit for each.

Updated 16 Nov 2026 8 min read LocalStash editorial

The shape of a good reference library follows the shape of the work. A person who ships interfaces every week needs states and edge cases; a person who writes needs sentences that did a job. Saving both into one undifferentiated pile produces a folder nobody opens. Below, six working setups — not personas invented for a landing page, but the filtering instincts that different jobs actually require.

1. Product designer

What goes in. Flows rather than screens: onboarding, checkout, permissions, destructive actions, settings. Empty, error and loading states, because they are where products reveal whether anyone thought about them. Pricing pages with an unusual tier structure. Tables that survive twelve columns. Anything with a constraint you can name — a form on a 320px screen, a dashboard for people who use it daily.

Tags. mobile web form table empty-state onboarding pattern competitor. Note the absence of visual adjectives; those belong in the note, if anywhere.

The weekly habit. During the Friday review, pick one flow and count its states. Write the number in the synthesis note. Over a month you will have a personal baseline for estimating: “onboarding is never fewer than nine states”.

Starter kit. Mobbin for flow-level references, NN/g for the reasoning behind a pattern, Pricing Pages for tier structures, and one competitor you are genuinely worried about — saved deliberately, not casually.

2. Frontend engineer

What goes in. Techniques with a working demo: a CSS layout trick you will otherwise re-derive, an animation with a sensible easing curve, a data table with virtual scrolling, an accessibility pattern with the markup included. Documentation you had to hunt for. Error messages you caused and the fix. Benchmarks with numbers attached, because “feels fast” does not survive a performance review.

Tags. css javascript performance accessibility library snippet. Add todo to anything you intend to try in a real project; that tag is the difference between a reference and a habit.

The weekly habit. Every time a snippet earns its place in production, add a line to the note: where it shipped, and what broke first. A snippet with a war story is ten times more valuable than one with a star count.

Starter kit. web.dev — Learn Performance, CSS-Tricks, MDN, and the source of one library you depend on but have never read.

3. Content designer / writer

What goes in. Microcopy that changed a decision: the button label that made a destructive action feel reversible, the empty state that told you what to do next, the error that admitted fault without grovelling. Openings worth studying — one concrete image before the argument. Headlines that carry a number honestly. Emails that got a reply.

Tags. microcopy voice headline onboarding error essay. Save the sentence itself in the note; a screenshot of a paragraph cannot be searched.

The weekly habit. Once a week, rewrite one saved line in your own voice and keep both versions. The comparison is the exercise, not the collection.

Starter kit. The Marginalian for essay openings, NN/g on microcopy, BBC GEL for writing guidelines, and a support inbox you have read for a week.

4. Founder / indie maker

What goes in. Competitor moves with dates, because pricing and positioning change faster than memory. Landing pages that explain an unfamiliar product in one screen. Changelogs of companies that ship well. Pricing pages, trial terms, refund language. Onboarding sequences you experienced as a user and can describe honestly.

Tags. competitor pricing positioning landing copy todo. Keep the date in the note — a competitor reference without a date is a rumour.

The weekly habit. Every Friday, re-check the two competitors you actually lose deals to. Update their entries rather than adding new ones. Ten minutes of maintenance beats an hour of research.

Starter kit. Your three closest competitors' pricing pages, Indie Hackers for the shape of small-product launches, and one page whose copy made you sign up.

5. Researcher or student

What goes in. Papers with the specific claim you need, not the whole PDF. Methodology notes: sample size, what was measured, what was not. Contradicting studies kept side by side, because the contradiction is the interesting part. Quotes with page numbers. Definitions that shifted between sources.

Tags. paper method quote contradiction definition todo. Tag by the argument you will use the item for, not by the journal.

The weekly habit. Write one paragraph a week that cites three saved items. The paragraph is the product; the library is the supply chain.

Starter kit. Your citation manager's export folder, the three papers that define your current question, and one study you suspect is wrong — saved so you can argue with it later.

6. Freelance consultant or small agency

What goes in. Case studies with numbers: what changed, by how much, over what period. Proposal sections that won work. Scoping language that prevented a difficult project from becoming unprofitable. Client-facing explanations of design decisions. Invoices and contracts are not references — they belong in a different system entirely.

Tags. case-study proposal scope pricing client-safe. The last tag is the important one: it marks the entries you are willing to show a client. Everything else stays internal.

The weekly habit. After each call where a client pushed back, save the sentence that resolved it. Over a year, that file becomes the most valuable document you own — more than any portfolio piece.

Starter kit. Two proposals that won, one that lost, and a case study from an agency whose reporting style you trust.

Advertisement
One workspace, six different vocabularies

Categories for the kind of work, tags for the element, collections for the project. No account needed.

Try the workspace

Which tool for which job

A swipe file is not the same as a bookmark manager or a notes app, even though the three overlap.

ToolHoldsRetrievalWhere it fails
Bookmark managerURLs, titles, foldersFolder browsing, keyword searchNo reasoning, no images, no intent
Notes appText, some attachmentsFull-text searchWeak on visual references and sources
Swipe fileSource, screenshot, mechanism, judgment, tagsTag filters and intent searchNeeds a review habit to stay useful
Read-later queueUnread articlesChronologicalBecomes a graveyard; no decisions recorded

The distinction that matters: a bookmark tells you where something is, a swipe file tells you what it is for. That second piece of information is the one you cannot recover later, which is why it has to be written at capture time.

Start in ten minutes

  1. Minute 1–2. Pick the one job you need this month: pattern lookup, evidence for a client, or calibration. Write it somewhere.
  2. Minute 3–6. Save five references for that job only. Not ten, not a folder of everything. Five forces a decision about what counts.
  3. Minute 7–8. Tag them with one element tag and one intent tag. Resist the urge to build a taxonomy.
  4. Minute 9. Delete the two weakest. The first review is the most important one.
  5. Minute 10. Put a twenty-minute slot in Friday's calendar.
If you only remember one thing A reference library is judged by what it answers under time pressure, not by how much it contains. Five annotated entries you can find beat five hundred you cannot.

Try it with four samples

LocalStash loads four references with notes and tags already filled in, so you can see how an entry should read before you write your own.

Written and maintained by the LocalStash team. No trackers, no email capture. Workspace · Privacy