podverse/add-by-rss-components-sync
.cursor/skills/add-by-rss-components-sync/SKILL.md
Keep Add-by-RSS and non-Add-by-RSS list/media components in sync.
$ install --global
skillsauthnpx skillsauth add podverse/podverse add-by-rss-components-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:48 PM6.9s1 file scanned
SKILL.md
- name:
- add-by-rss-components-sync
- description:
- Keep Add-by-RSS and non-Add-by-RSS list/media components in sync.
- version:
- 1.0.0
Add-by-RSS Components Sync
Purpose
Keep Add-by-RSS and non-Add-by-RSS list/media components visually and structurally aligned while preserving their distinct data sources and behaviors.
Scope
apps/web/src/components/Common/shared list/media componentsapps/web/src/components/Core/non-Add-by-RSS components that use Commonapps/web/src/components/AddByRSS/**Add-by-RSS componentsapps/web/src/app/add-by-rss/**page entrypoints that import Add-by-RSS componentsapps/web/src/app/**page entrypoints for non-Add-by-RSS components
Workflow
- Identify the non-Add-by-RSS component being changed (list row, grid node, header, list header).
- Locate its Core counterpart in
components/Core/**and Add-by-RSS counterpart incomponents/AddByRSS/**. - Check for a shared component in
components/Common/**. - If a shared component exists, update it first and verify both call sites.
- If no shared component exists and layouts match, extract one into
components/Common/**. - Update both Add-by-RSS and non-Add-by-RSS adapters to use the shared component.
- When refactoring list patterns, align with the Common/Core/AddByRSS split:
components/Common/List/<Resource>/Common<Resource>List{GridNode|Row|Nodes}.tsxcomponents/Core/List/<Resource>/Core<Resource>{GridNode|Row|Nodes|List}.tsxcomponents/AddByRSS/**/AddByRSS<Resource>{GridNode|Row|Nodes}.tsx- Keep shared types in
components/Common/List/<Resource>/types.ts
Naming Conventions
- Shared components in
components/Common/**use theCommon*prefix. - Non-Add-by-RSS components that use Common live in
components/Core/**and useCore*prefix. - Add-by-RSS components live in
components/AddByRSS/**and useAddByRSS*prefix. - Page-only components live in
apps/web/src/app/**and includePagein the name.- Rename
*Client,*Context,*DropdownConfig,*Header,*List→*Page*and update imports.
- Rename
Add-by-RSS Constraints
- Add-by-RSS headers must not include share buttons.
- Add-by-RSS channel views should use the feed URL as a title fallback until parsed fields exist.
- Add-by-RSS list views should support list and grid when their non-Add-by-RSS equivalents do.
- Add-by-RSS list rows should include the same MoreButton menu where applicable.
Checklist
- List row/grid parity: title, image sizing, last pub date formatting, link behavior.
- Header parity: layout structure and shared styles between tablet and desktop.
- Add-by-RSS behavior preserved: subscribe actions, no share buttons.
- Shared styles reused wherever possible (avoid duplicating SCSS).
- Page-level components use the
Pagenaming convention (e.g.,PodcastPageList).
Examples
- Changing a podcast list row: update
components/Common/List/Podcast/*and ensure bothcomponents/Core/List/Podcast/*andcomponents/AddByRSS/Podcast/*adapters render the same UI. - Changing a podcast header layout: update
components/Common/Media/Podcast/CommonPodcastHeaderView*and verify the Add-by-RSS header renders without share buttons. - Renaming page-level components:
TracksClient.tsx,TracksContext.tsx, andTracksDropdownConfig.tsxbecomeTracksPageClient.tsx,TracksPageContext.tsx, andTracksPageDropdownConfig.tsx, with imports updated inapps/web/src/app/tracks/page.tsx.
Related Skills
podverse/podverse-workers-patterns
documentation
VerifiedTrustedCommunity
Per-job env validation and config patterns for the workers app. Use when adding or changing worker commands, touching workers startup validation, or documenting worker env vars.
4SKILL.mdUpdated Apr 16, 2026
podverse/podverse-web-patterns
development
VerifiedTrustedCommunity
Common patterns and examples for the podverse-web Next.js application
4SKILL.mdUpdated Apr 16, 2026
podverse/time-format-local
tools
VerifiedTrustedCommunity
Ensures client-side time displays use formatDateTimeAbbrev for localized, readable timestamps. Use when rendering dates/times in the UI or when the user mentions time formatting or local timezone display.
4SKILL.mdUpdated Apr 16, 2026
podverse/.cursor/skills/testing-policy
testing
VerifiedTrustedCommunity
--- name: podverse-testing-policy description: Skip test implementation unless the user explicitly asks. Use when a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". version: 1.0.0 --- # Testing policy — skip tests for now ## When to use - When a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". - When deciding whether to implement tests for a feature. ## Rules 1. **We are not concerning ourselves with tests at this time.** Skip test imp
4SKILL.mdUpdated Apr 16, 2026