portaljs-new-portal

PortalJS — New Portal

Overview

Scaffold a production-ready PortalJS data portal from a brief. The skill is interactive: if the brief is thin it interviews the user in three short rounds (mapped to the template's three surfaces — Home, Catalog, Showcase), echoes a brief back for confirmation, then copies examples/portaljs-catalog (locally or via a remote tiged fetch), substitutes placeholder tokens, sets the namespace mode and the UI language, seeds any datasets named in the interview, installs dependencies, and verifies the scaffold with a type check.

Prerequisites

• Node.js >=22 and npm available on PATH.
• Network access, unless a current local checkout of the portaljs repo is available (the resolver defaults to a remote fetch of the template).
• A destination directory name that does not already contain files (or user consent to overwrite one that does).

Instructions

The canonical, full step-by-step workflow is .claude/commands/portaljs-new-portal.md — the single source of truth. Read and follow it when executing. Summary:

1. Interview the user in up to three rounds — Home/basics (incl. the UI language, default English), Catalog & discovery (datasets, namespace mode theme vs owner), Showcase/views — skipping any round already answered by the input brief. Accept "use defaults" at any point.
2. Confirm a short brief (name, slug, description, language, namespace, datasets, views) before building.
3. Resolve the template source: prefer a remote tiged fetch of examples/portaljs-catalog at main (or PORTALJS_TEMPLATE_REF); use a local checkout only when it is current (has pages/[owner]/[slug].tsx) and the destination is outside that repo.
4. Materialize the template into ./PROJECT_SLUG, asking first if the destination already exists and is non-empty.
5. Substitute __PROJECT_NAME__, __PROJECT_SLUG__, __DESCRIPTION__ tokens across all files with perl -pi, escaping /, \, and & in the values.
6. Set NAMESPACE_TYPE ('theme' or 'owner') in lib/datasets.ts per the interview.
7. Set the UI language (skip for English): translate locales/en.json into locales/<code>.json (every key, {placeholders} verbatim, the plural forms the language uses, _intl BCP 47 tag such as it-IT), register it in lib/i18n.ts, set DEFAULT_LOCALE in next.config.js, and run npm run i18n:check.
8. Seed datasets captured in Round 2 (via /portaljs-add-dataset or by hand), or clear datasets.json to [] if none were named.
9. Run npm install inside the scaffolded portal.
10. Verify with npm run i18n:check and npx tsc --noEmit (never next build here — it would corrupt a running dev server's .next/ directory).
11. Report the scaffolded routes, namespace mode, language, and next steps.