skills.rest
brett406
brett406COMMUNITY
Explore all skills by this author →
GitHub

dealer-portal-stamp

Automate B2B dealer portal launches from Next.js template through DNS cutover.

Updated Mar 19, 2026
Search Tags:#next.js#prisma#launch checklist#b2b#railway deployment#dealer portal#brand reskin
One-click install
npx skills add https://github.com/brett406/dealer-portal-template --skill dealer-portal-stamp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dealer-portal-stamp
Source: https://github.com/brett406/dealer-portal-template/tree/main/.claude/skills/dealer-portal-stamp
Command: npx skills add https://github.com/brett406/dealer-portal-template --skill dealer-portal-stamp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inconsistent, error-prone process of launching new customer dealer portals from the shared template, preventing common oversights like missing environment variables, accidental production seed runs, and unpolished pre-launch branding that derail launches and waste team time.

Core Features & Use Cases

  • Phased End-to-End Playbook: Guides teams through 5 consistent, ordered phases (repo setup, brand reskin, content migration, Railway deployment, DNS cutover) for every new customer portal stamp.
  • Pre-Launch Guardrails: Includes hard-stops and checklists to catch critical failures like leaked demo copy, missing auth configuration, and broken CSRF settings before the portal goes live.
  • Use Case: Use this Skill when starting a new B2B dealer portal build for a customer, resuming an in-progress stamp, or verifying a portal is fully ready for public launch.

Quick Start

Use the dealer-portal-stamp skill to walk through the full end-to-end process of launching a new branded dealer portal for your customer, from initial repo setup through DNS cutover and pre-launch verification.

Frequently Asked Questions about dealer-portal-stamp

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

FAQPage Schema
How do I launch a new B2B dealer portal from a Next.js template without missing environment variables?▼

To launch a B2B dealer portal safely, this Skill enforces a phased playbook covering local environment setup, brand reskinning, and Railway deployment to prevent missing environment variables and common oversights. It guides you through five ordered phases from repo setup to DNS cutover.

What steps are required to reskin a shared Next.js template for a custom customer portal?▼

Reskinning a shared Next.js template requires passing mandatory pre-reskin branding gates, migrating customer-specific content, and verifying no leaked demo copy remains before deployment. This Skill enforces those hard-stop checklists to catch unpolished branding and broken configurations early.

How do I prevent accidental production seed runs when deploying a dealer portal to Railway?▼

Preventing accidental production seed runs requires production safety guardrails during Railway deployment and DNS cutover. This Skill enforces those guardrails alongside authentication and CSRF configuration checks to protect live public deployments.

Can I use this workflow to verify an in-progress dealer portal stamp is ready for public launch?▼

Yes, you can use this workflow to verify an in-progress dealer portal stamp by running pre-launch validation checklists that catch leaked demo content, missing auth configuration, and broken CSRF settings. It validates full readiness before the portal goes live.

Does this dealer portal launch process include DNS cutover and pre-launch validation?▼

The dealer portal launch process includes DNS cutover and pre-launch validation as the final phases of its end-to-end playbook. It enforces production safety guardrails and correct authentication configuration to ensure a clean public deployment.

Why do I need a launch checklist for stamping new B2B customer portals?▼

You need a launch checklist for stamping new B2B customer portals to eliminate inconsistent step execution and prevent common oversights like missing environment variables and unpolished pre-launch branding. This Skill automates that checklist to stop failures that derail launches and waste team time.

Related Skills

Explore More Software Engineering Skills→
yuhle-qugyuhle-qug

database-expert

Analyze and optimize database performance across PostgreSQL, MySQL, MongoDB, and SQLite.

Community
Advanced
rampstackcorampstackco
523

launch-runbook

Plan and execute structured launch runbooks with rollback procedures.

Official
Advanced
DexploarerDexploarer
7

Railway Postgres Manager

Automate PostgreSQL provisioning, migrations, backups, and connections on Railway.

Community
Advanced
brett406brett406

brand-discovery

Validate brand assets and generate a locked customer-specific design skill.

Community
Advanced