podverse
25 verified skills100 total stars
podverse-workers-patterns
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.
documentation4
llm-history-tracking
LLM history tracking guidelines. Use when updating history files or starting new feature work.
documentation4
lighthouse-docker-sync
Keeps Lighthouse Docker compose/env files aligned with infra Docker changes. Use when editing infra docker-compose files, docker envs, or scripts that Lighthouse services depend on.
devops4
add-by-rss-parity-sync
Keeps add-by-RSS views in sync with non-add-by-RSS counterparts. Use when modifying podcasts/episodes/livestreams/artists/albums/tracks list or detail components, routes, or styles in apps/web.
development4
add-by-rss-components-sync
Keep Add-by-RSS and non-Add-by-RSS list/media components in sync.
content-media4
env-file-formatting
Env file value formatting (double quotes for non-empty). Use when adding or editing .env, .env.example, or any *.env template in the repo.
development4
podverse-documentation-conventions
Documentation file naming conventions for the Podverse monorepo. Use when creating or modifying documentation files, README files, or any markdown documentation.
documentation4
bundle-optimization
Keeps bundle size in mind when adding dependencies, changing helper packages, or modifying the web app. Use when adding npm deps, touching @podverse/helpers*, introducing heavy UI, or working on client-side code in apps/web.
tools4
podverse-global-patterns
--- name: podverse-global-patterns version: 1.1.0 --- # Global Patterns ## Dependencies Tier 1 → Tier 2 → ... → Tier 5. Only depend on lower tiers. ## Workspace Deps ```json { "dependencies": { "@podverse/helpers": "workspace:*", "@podverse/helpers-validation": "workspace:*", "@podverse/helpers-requests": "workspace:*" } } ``` **Helper packages available:** - `@podverse/helpers` - Core utilities, types, DTOs - `@podverse/helpers-validation` - Validation utilities - `@podve
tools4
podverse-logging-log-dir
Log directory (LOG_DIR) behavior across the monorepo. Use when adding or changing log directory behavior, LOG_DIR env, or file logging in any app or package.
tools4
lighthouse-env-alignment
Keeps Lighthouse env handling aligned with apps/api and apps/web startup validation. Use when changing Lighthouse env loading, .env.api/.env.web examples, or app validation requirements.
development4
routing-url-params
Enforces URL query param handling across pages. Use when adding or updating list/detail filters, pagination, or sorting. Keep URLs clean by not auto-inserting params; only preserve params when the user navigates with them, and remove defaults from the URL.
data-ai4
podverse-web-patterns
Common patterns and examples for the podverse-web Next.js application
development4
.cursor/skills/testing-policy
--- 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
testing4
podverse-api-patterns
Common patterns for the podverse-api Express application
development4
podverse-github-workflows
--- name: podverse-github-workflows version: 1.0.0 --- # GitHub Workflows & Issue Management ## Repository Information - **Repository**: `podverse/podverse` - **Full URL**: https://github.com/podverse/podverse - **Issues**: https://github.com/podverse/podverse/issues - **Pull Requests**: https://github.com/podverse/podverse/pulls This information is also available in `package.json`: ```json { "repository": { "type": "git", "url": "https://github.com/podverse/podverse.git" }, "
development4
interactive-prompts
Do not complete steps that require interactive prompts (inquirer, CLI input). Tell the user their input is needed and provide exact instructions. Use when verification or workflows involve prompts, wizards, or interactive CLI tools.
tools4
podverse-k8s-patterns
Common patterns for Kubernetes manifests in infra/k8s. Use when editing or adding K8s manifests, changing deployment config, adding env vars to ConfigMaps, or working with ArgoCD/Kustomize/SOPS.
development4
podverse-management-api-patterns
Common patterns for the podverse-management-api Express application
development4
podverse-orm-patterns
Common patterns for the podverse-orm package
tools4
parallel-plan-execution
Create decomposed, parallelizable execution plans with copy-pasta prompts for multi-agent workflows. Use when planning large migrations, refactoring tasks, or any work that can benefit from parallel execution across multiple agents.
development4
plan-completion
When you finish a plan file in active/, automatically move it to completed/. If it's the last plan in its set, move the whole set. Use when completing any plan under .llm/plans/active/.
data-ai4
rate-limit-message
Standardizes 429 handling by using the shared rate-limit helper to render user-facing messages. Use when handling API errors that may return 429 (rate limited) responses or when the user mentions rate limiting.
tools4
styles-import-last
Enforces import ordering so styles (CSS/SCSS module) imports are last. Use when editing React components or pages in .tsx/.jsx files, or when the user mentions import order or style imports.
development4
time-format-local
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.
tools4