portaljs-architect

# PortalJS — Architect ## Overview The advisory entry point for a PortalJS project. Before anything gets scaffolded, this skill works out what to build: given the kind of portal, the shape of the data, and its purpose, it fills six architecture slots (storage, catalog, compute, access, hosting, metadata), resolves two build-time knobs (per-dataset data tier and the portal-wide `DATA_QUERY` mode), and hands off to the concrete build skills. It decides; it does not build. When the brief is thin it interviews in short rounds and never dead-ends — every question has a sensible default, reachable by replying "use defaults." ## Prerequisites - A rough idea of the portal's purpose and data (exact numbers are not required — the interview supplies defaults for anything missing). - Optional: local files or a directory of sample data to inspect for size and shape. - No PortalJS project needs to exist yet; this skill runs before scaffolding. ## Instructions The canonical, full step-by-step workflow lives in [`.claude/commands/portaljs-architect.md`](https://github.com/datopian/portaljs/blob/main/.claude/commands/portaljs-architect.md) — that file is the single source of truth. Follow it when executing this skill: 1. Parse `$ARGUMENTS` for anything already specified, then interview for what's missing, one round at a time: (1) what's being built, (2) what the data is, (3) what it's for, (4) constraints. Accept "use defaults" at any point. Inspect named files/directories with...