Execute Replit secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "replit secondary workflow", "secondary task with replit".
From replit-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin replit-packThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Secondary workflow for Replit. Complements the Repl creation and execution workflow by focusing on collaboration management, deployment configuration, and bulk Repl administration. Use this skill when you need to manage team member access to Repls, configure custom domains for deployed projects, migrate Repls between teams, or audit and clean up stale Repls across an organization.
replit-install-auth setupreplit-core-workflow-aIdentify the administrative task to perform: collaboration management, deployment configuration, or bulk cleanup. For collaboration changes, compile the list of team members and the permission levels (viewer, editor, owner) they should hold on each Repl. For deployment configuration, gather the custom domain, environment variables, and always-on settings required for production hosting.
// Step 1 implementation
Apply the configuration changes via the Replit API. For permission updates, patch each Repl's collaboration settings with the new access list. For deployment configuration, update the Repl's hosting settings and verify the custom domain resolves correctly. For bulk cleanup, list all Repls matching your stale criteria and batch-delete or archive them to reclaim quota.
// Step 2 implementation
Confirm that all changes took effect by querying the Repl metadata and verifying the updated state. Notify affected team members of permission changes. Document the administrative actions taken along with the rationale, particularly for deletions, so the audit trail is clear if questions arise later.
// Step 3 implementation
| Aspect | Workflow A | Workflow B |
|---|---|---|
| Use Case | Primary | Secondary |
| Complexity | Medium | Lower |
| Performance | Standard | Optimized |
// Complete workflow example
// Error handling code
For common errors, see replit-common-errors.