agentleFS
samuelclaysamuelclay/NewsBlur/.agents/skills/mobile-web/SKILL.md

mobile-web

Skill7.7k starsChanged yesterdayMITView on GitHub

End-to-end tests and screenshots of the NewsBlur web reader's phone layout (body.NB-mobile at 768px and narrower, or a phone held sideways). Use when changing anything the phone layout touches (views/mobile_*.js, css/reader/mobile.css, common/mobile_utils.js, reader.js layout code, story title/detail views, modals or popovers), when asked to test or screenshot the site on a phone, or to attach phone screenshots to a PR. Runs Playwright with iPhone emulation and real touch events against a running dev stack, and restores the dev account's settings afterwards.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the samuelclay/NewsBlur repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about samuelclay/NewsBlur

The biggest 5 of 19 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 19

Talked about on GitHub and Stack Overflow (19 times).

On GitHub · 16

11 more on GitHub

On Stack Overflow · 3

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. neijix/AICodeFactory★ 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 repository9 other files it gives its agents.

The file

Files
SKILL.md

Mobile web

The web reader turns into a phone app at 768px and narrower, and on short touch screens such as a phone held sideways. The desktop panes become stacked full-screen screens that slide over one another: feed list, dashboard, story list, and a swipeable story screen for grid layouts. views/mobile_layout_view.js runs it, with the gesture and history helpers in common/mobile_utils.js and every style in css/reader/mobile.css.

This skill drives that layout the way a thumb would, in the Playwright docker image on the stack's network. Swipes, edge swipes, long presses and pull to refresh are real CDP touch events, so touch-action and pointer events behave as on a phone.

Running

From the repo root or a worktree, with its stack running (make, or make worktree in a worktree):

python3 .agents/skills/mobile-web/run.py smoke                 # the regression suite
python3 .agents/skills/mobile-web/run.py all                   # every scenario except next_unread
python3 .agents/skills/mobile-web/run.py tour --args dark --out /tmp/phone-dark
python3 .agents/skills/mobile-web/run.py smoke --workspace mobile-web --feed 476

The workspace defaults to the checkout you run it from. Each scenario prints PASS and FAIL lines and a count. Any failure or exception makes run.py exit non-zero, and a crash leaves a <scenario>-crash.png behind. Screenshots go to --out (default /tmp/newsblur-mobile-web) as <scenario>-<name>.png. Read them after a run; a passing check does not prove a screen looks right.

Node unit tests for the pure helpers are separate: node --test node/tests/mobile_utils.test.js.

Scenarios

ScenarioWhat it covers
smokeEvery reader flow with assertions: screens and history, the Dashboard screen, long-press sheets, list inline expansion, grid → story screen, swipe paging, toolbar previous/next, Text view, Train modal, edge-swipe back (cancel and complete), browser back/forward, back from a search, pull to refresh, modal close, then regressions
regressionsBugs from code review, each confirmed failing before its fix. Add a check here for every phone layout bug you fix
tourScreenshots of every screen in order. --args dark for the dark theme, applied in the page and never saved
modalsThe 19 modals plus the activity sheet: each opens full width with nothing hanging off the screen
playerThe Listen and podcast player floats as a one-row bar at the bottom of each screen, clear of the toolbar row under the nav bar, opens as a bottom sheet and closes from the shade. Uses whatever the account's player already holds and skips when it's empty
page_scrollThe feed list and story list scroll the page itself while at rest, which is what lets a phone browser shrink its toolbar: bars stay stuck to the top, more stories load, and a sheet or slide holds each list where it was
sheetsA story's Share form, Save tags and notes, and Related stories slide up as bottom sheets over the shade instead of opening inside the story, the share field takes the cursor without iOS zooming in, and the shade closes each. Saves and unsaves one story, shares nothing
rtlArabic: screens slide from the left, swipe directions reverse, the edge swipe starts at the right edge
landscape852×393 keeps the phone layout
tabletiPad portrait gets the phone layout with a two-column grid
resizeNarrowing a desktop window switches to the phone layout with the open feed, widening switches back, and the feed's desktop layout is untouched
desktopA desktop window never sees the phone layout, its chrome, or tagged history entries
river_switchDesktop Split layout: leaving a folder for All Site Stories fades both panes out exactly as drawn (feed titles, river padding, scroll position, a stuck story header, a video frame as an empty box), then fades the river in. The story pane fades only when a river or folder is on either side of the switch, and nothing fades with animations off
stale_pageDesktop: opening a feed or folder cancels the page of stories still loading for the last one. Holds the server's answer to every later page (with page.route), then reopens the same folder, another folder and the same feed: the old page's request is aborted, the new first page goes out without waiting behind it, and none of its stories reach the new list once the held answers are let go
safariiOS Safari's browser mode (navigator.standalone === false): the layout's edge swipe stands down for Safari's own, Back after Safari's swipe doesn't slide twice, and a tap on the back button still slides
feed_cacheThe feed list draws from its localStorage copy before /reader/feeds answers (held with page.route), a feed opens meanwhile, the server's answer merges in without a redraw, and signing out clears the copy. Ends signed out, so it runs last
next_unreadNext unread reads to the end of a feed, moves on to the next feed with unreads and stays on the story screen. It marks every story it passes as read, so all skips it. It only starts in a visible feed with 1 to 6 unread stories that has another unread feed below it, and fails up front when there is none

Scenarios pick the active visible feed with the most unread stories, then the busiest one that shows read stories too. When the account hides read feeds and everything is read, the harness switches the feed list to All first. A feed showing fewer than four stories is switched to all stories so there is something to swipe through. Both changes save to the account and are put back after the run. Pass --feed <id> to choose the feed yourself. A scenario is scenarios/<name>.py with a run(ctx) function and an optional VIEWPORT override. harness.py documents the ctx helpers (login, open_feed, set_layout, tap_story, state, check, shot, and ctx.touch.swipe/drag/long_press).

Settings the runs change

Toggling list and grid, choosing Feed or Text on the story screen, and switching themes all save to the dev account. Every worktree shares one database, so these are the same settings the main checkout shows. run.py snapshots the account's view_settings and preferences in the web container before the first scenario, restores every key that changed afterwards (even when a scenario fails), and prints what it put back. Don't run scenarios with the run_in_background flag and then edit settings in the browser at the same time; the restore would undo your edits.

Other data does change and is not restored: opening stories marks them read, and next_unread reads through a whole feed.

Gotchas

  • Adding a stylesheet to newsblur_web/assets.yml needs docker restart newsblur_web_<worktree> before the page links it. JavaScript under media/js/newsblur/views/ is picked up by glob, with no restart.
  • A tap during momentum scrolling only stops the scroll, as on a real phone. Wait about a second after a vertical swipe before tapping a button, or the tap is swallowed.
  • page.evaluate invokes a snippet whose value is a function. Wrap snippets that assign functions in (() => { ... })().
  • A feed can appear in several folders. Locate rows with >> visible=true (ctx.feed_row does).
  • A list at rest is not its own scroller. While the feed list or story list sits still, the page scrolls in its place (body.NB-mobile-page-scroll), so window.scrollY moves and the list's scrollTop reads and sets the page's. During a slide, an edge swipe, a sheet or a modal the list scrolls itself again.
  • Emulated Chromium is not Safari. iOS Safari's own edge swipe-back, rubber banding and the soft keyboard still need a real iPhone. When the browser animates its own swipe-back, popstate carries hasUAVisualTransition and the layout switches screens without a second slide.
  • CDP touch events never set :hover or :active, but real phones apply both the moment a thumb lands. To test what a touch looks like, force the states with CSS.forcePseudoState (hover_changes in scenarios/regressions.py).
  • A backdrop-filter, like transform or filter, makes an element the containing block of its absolutely positioned descendants. The story list's search pill drops its glass while its field is open for that reason.

Screenshots on a PR

Attach images with gh 2.99.0 or newer, referencing the same local paths in the body so they get rewritten to hosted URLs. Build the argument list as an array; zsh does not split a string of flags:

ARGS=(); for f in /tmp/newsblur-mobile-web/tour-light-*.png; do ARGS+=(--attach "$f"); done
gh pr comment <number> --body-file body.md "${ARGS[@]}"

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.