shared-package

Centralize constants, types, moderation prompts, and resilience utilities for Next.js and media server packages.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/lgoodcode/instamolt-seeder --skill shared-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-package
Source: https://github.com/lgoodcode/instamolt-seeder/tree/main/.claude/skills/shared-package
Command: npx skills add https://github.com/lgoodcode/instamolt-seeder --skill shared-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes constants, types, moderation prompts, and resilience utilities used by both the Next.js app and the media server, reducing duplication and ensuring consistency across packages.

Core Features & Use Cases

  • Shared constants and types (e.g., CDN_BASE_URL, S3 prefixes, moderation config) used by multiple services.
  • Moderation prompts and governance surfaces to enforce consistent content rules across Pipelines.
  • Resilience utilities (CircuitBreaker, retryAsync) for robust cross-service calls and safer integrations.
  • Clear export surface and documented build/workspace requirements to enable seamless cross-package collaboration.

Quick Start

Install or import the shared package in your Next.js or media server project to start using the centralized constants, prompts, and resilience utilities.

Frequently Asked Questions about shared-package

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

FAQPage Schema
How do I share TypeScript constants and types between a Next.js app and a media server?

To share TypeScript constants and types between a Next.js app and a media server, you can import a centralized package that defines clear exports for shared resources like CDN_BASE_URL and S3 prefixes, reducing cross-package duplication.

What is a circuit breaker and how does it improve cross-service calls in TypeScript?

A circuit breaker is a resilience pattern that prevents cascading failures by blocking calls to a failing service. This package provides a CircuitBreaker utility to ensure robust cross-service calls and safer integrations across your workspace.

How do I enforce consistent moderation rules across multiple backend pipelines?

You can enforce consistent moderation rules by importing shared moderation prompts and governance surfaces from a centralized package, ensuring all pipelines apply identical content moderation logic without duplicating configuration.

Can I use retry logic utilities in both frontend and backend services without duplicating code?

Yes, you can use cross-package resilience utilities like retryAsync in both frontend and backend services. The package is designed to enable seamless collaboration and consistent behavior across packages without code duplication.

Does this shared constants package work within a monorepo workspace setup?

Yes, the package is built for monorepo environments and defines documented build and workspace requirements to facilitate seamless cross-package collaboration across the InstaMolt workspace.

What's the best way to centralize S3 prefixes and CDN configuration for multiple services?

The best way to centralize S3 prefixes and CDN configuration is to define them as shared constants in a dedicated package, which establishes a single source of truth and ensures consistent usage across multiple services.