new-portal

Scaffold a new authenticated portal with login actor, routes, and optional SPA frontend.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/weiloon1234/Forge-Starter --skill new-portal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-portal
Source: https://github.com/weiloon1234/Forge-Starter/tree/main/.claude/skills/new-portal
Command: npx skills add https://github.com/weiloon1234/Forge-Starter --skill new-portal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of a brand-new authenticated portal surface within Forge Starter, including a dedicated login actor, REST routes, a per-portal guard, and an optional SPA frontend, so teams can launch a distinct surface without impacting existing portals.

Core Features & Use Cases

  • Self-contained portal with its own login actor and guard
  • Separate REST namespace under /api/v1/<name>/ and a per-portal router scope
  • Optional SPA frontend scaffold under frontend/<name>/ for a complete user-facing experience

Quick Start

Create a brand-new portal with its own login, routes, guard, and optional SPA frontend.

Frequently Asked Questions about new-portal

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

FAQPage Schema
How do I scaffold an authenticated portal with a separate SPA frontend?▼

Scaffolding an authenticated portal with a SPA frontend involves generating a dedicated login actor, per-portal routes, and a separate frontend directory. This creates a self-contained surface with its own login and REST namespace under /api/v1/.

What is a per-portal guard and when do I need a separate login actor?▼

A per-portal guard secures a specific portal surface. You need a separate login actor when launching a distinct authenticated surface requiring its own login flow, REST routes, and infrastructure wiring without impacting existing portals.

Does the portal scaffolding handle infrastructure configuration like Dockerfile and i18n keys?▼

Yes, portal scaffolding handles infrastructure configuration by generating Makefile and Dockerfile adjustments alongside i18n keys. It ensures per-portal infrastructure wiring is fully generated, including optional RBAC or permissions scaffolding for the new surface.

Can I add an RBAC permissions scaffold when creating a new portal?▼

Yes, you can add an RBAC permissions scaffold when creating a new portal. The scaffolding process optionally generates role-based access control structures alongside the dedicated login actor, per-portal routes, and guard.

What is the best way to namespace REST routes for a newly created portal?▼

The best way to namespace REST routes for a new portal is under /api/v1/<name>/ using a per-portal router scope. This ensures the new authenticated surface operates independently without impacting existing portal routes or login actors.