add-by-rss-parity-sync

Synchronize add-by-RSS UI views with non-add-by-RSS counterparts for visual parity.

6|5|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/podverse/podverse --skill add-by-rss-parity-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-by-rss-parity-sync
Source: https://github.com/podverse/podverse/tree/main/.cursor/skills/add-by-rss-parity-sync
Command: npx skills add https://github.com/podverse/podverse --skill add-by-rss-parity-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep add-by-RSS views in sync with non-add-by-RSS counterparts to ensure consistent layout, routing, and user experience across podcasts, episodes, livestreams, artists, albums, and tracks.

Core Features & Use Cases

  • Synchronize add-by-RSS layouts with non-add-by-RSS layouts for podcasts, episodes, livestreams, artists, albums, or tracks to maintain a uniform UI.
  • Ensure add-by-RSS detail views mirror non-add-by-RSS detail views, including headers, tabs, and list row styling, while omitting non-applicable elements.
  • Align add-by-RSS routes with the corresponding non-add-by-RSS routes (e.g., /add-by-rss/podcasts, /add-by-rss/episode/:id) and reuse shared wrappers to preserve spacing and loading overlays.
  • Reuse shared UI wrappers like DetailListWrapper to keep spacing and loading overlays consistent across parity views.

Quick Start

Update the add-by-RSS UI components to mirror changes from non-add-by-RSS pages and verify parity in the running app.

Frequently Asked Questions about add-by-rss-parity-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep add-by-RSS UI views consistent with non-add-by-RSS pages?

To keep add-by-RSS UI views consistent, mirror layout, headers, and tabs from non-add-by-RSS counterparts by reusing shared wrappers like DetailListWrapper and aligning routes.

What is add-by-RSS parity sync in frontend routing?

Add-by-RSS parity sync is the process of ensuring add-by-RSS pages maintain identical visual layout and routing structures to their non-add-by-RSS equivalents across podcasts and episodes.

How do I route add-by-RSS detail views to match standard podcast pages?

Route add-by-RSS detail views by applying consistent path structures like /add-by-rss/podcasts and /add-by-rss/episode/:id to match standard podcast pages and preserve the user experience.

When do I need to apply parity sync to add-by-RSS components?

You need to apply parity sync when editing or introducing UI changes to any add-by-RSS pages for podcasts, episodes, livestreams, artists, albums, or tracks to ensure a uniform layout.

Does add-by-RSS parity sync require shared UI wrappers?

Yes, add-by-RSS parity sync requires reusing shared UI wrappers like DetailListWrapper to keep spacing and loading overlays consistent across parity views.

How to handle non-applicable UI elements in add-by-RSS detail views?

When synchronizing add-by-RSS detail views, mirror non-add-by-RSS headers and list row styling while intentionally omitting non-applicable elements to maintain visual parity.