spa-subdomain-root-render

What problem does it solve?

This Skill solves the problem of subdomain-based SPAs redirecting away from the subdomain root and rendering blank content when a React Router component expects route parameters that do not exist at "/".

Core Features & Use Cases

• Redirect-free router rendering at subdomain root: Render the target page at "/" (instead of using Navigate) so username.domain.com/ stays clean and feels like a personal website.
• Fallback identifier logic for missing params: Use injected subdomain user data when useParams() has no matching values at the root route.
• Edge-injected global user context: Inject user data into the SPA HTML before hydration so the client can reliably read it during initial render.
• Use Case: When thecomedianriley.divine.video/ should show the profile page at "/" rather than redirecting to something like "/profile/npub1...", this pattern keeps the URL stable and ensures the component still loads.

Quick Start

Follow the steps in the SKILL.md to render the profile component directly at the "/" route, add a fallback that uses edge-injected subdomain data when useParams() is empty, and inject the user JSON in the edge worker before SPA hydration.