# portaljs - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for portaljs. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0003` supported 0.86

## What It Can Do

- **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim: `clm_0001` supported 0.86
- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `.claude/INSTALL.md`, `README.md`, `packages/ckan-api-client-js/README.md`, `packages/ckan/README.md` Claim: `clm_0002` supported 0.86

## How to Start

- `curl -fsSL https://raw.githubusercontent.com/datopian/portaljs/main/scripts/install-portaljs-skills.sh | bash` Evidence: `README.md` Claim: `clm_0004` supported 0.86
- `npx tiged datopian/portaljs/examples/portaljs-catalog my-portal` Evidence: `README.md` Claim: `clm_0005` supported 0.86
- `npm i @portaljs/ckan` Evidence: `packages/ckan/README.md` Claim: `clm_0006` supported 0.86, `clm_0007` supported 0.86
- `npm i @portaljs/ckan-api-client-js` Evidence: `packages/ckan-api-client-js/README.md` Claim: `clm_0007` supported 0.86
- `/plugin marketplace add datopian/portaljs` Evidence: `.claude/INSTALL.md` Claim: `clm_0008` supported 0.86
- `/plugin install portaljs@datopian-portaljs` Evidence: `.claude/INSTALL.md` Claim: `clm_0009` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Trial role matching first
- **Why**: This project is more of a role library; the core risk is picking the wrong role or treating role copy as execution capability. Trial role matching with Prompt Preview first, then decide whether to sandbox-import it.

### 30-Second Read

- **What to do now**: Trial role matching first
- **Minimum safe next step**: Trial role matching with Prompt Preview first; import in isolation only once satisfied
- **Do not trust yet**: Role quality and task fit cannot be trusted directly.
- **Continuing will touch**: Role selection bias, Command execution, Host AI configuration

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0003` supported 0.86
- **Capability exists: Multi-Host Install and Distribution** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim: `clm_0001` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `.claude/INSTALL.md`, `README.md`, `packages/ckan-api-client-js/README.md`, `packages/ckan/README.md` Claim: `clm_0002` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0004` supported 0.86

### What You Cannot Trust Yet

- **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results.
- **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.claude/INSTALL.md`, `AGENTS.md` et al.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

### What Continuing Will Touch

- **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions.
- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `.claude/INSTALL.md`, `README.md`, `packages/ckan-api-client-js/README.md`, `packages/ckan/README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.claude/INSTALL.md`, `AGENTS.md` et al.
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.claude/INSTALL.md`, `README.md` et al.
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0010` inferred 0.45
- **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim: `clm_0011` supported 0.86
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `.claude/INSTALL.md`, `README.md`, `packages/ckan-api-client-js/README.md`, `packages/ckan/README.md` Claim: `clm_0012` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **Multi-Host Install and Distribution**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim: `clm_0001` supported 0.86
- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `.claude/INSTALL.md`, `README.md`, `packages/ckan-api-client-js/README.md`, `packages/ckan/README.md` Claim: `clm_0002` supported 0.86

### Context Scale

- Total files: 1835
- Important-file coverage: 40/1835
- Evidence index entries: 80
- Role / Skill entries: 57

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for portaljs, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat portaljs as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for portaljs, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 57 role / Skill / project-doc entries.

- **Changesets** (project_doc): Hello and welcome! This folder has been automatically generated by @changesets/cli , a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it in our repository https://github.com/changesets/changesets Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.changeset/README.md`
- **Quickstart** (project_doc): PortalJS The AI-native framework for building data portals. Describe the portal you want — your agent helps you choose an architecture, scaffolds it, and loads your data. Docs · Discussions · Report a bug Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Giftless on Cloudflare R2 — staging deployment** (project_doc): Giftless on Cloudflare R2 — staging deployment Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `giftless/README.md`
- **Flowershow default template** (project_doc): Flowershow default app template. Uses Next.js with Tailwind and MDX. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/README.md`
- **Deployment** (project_doc): This is a repo intended to serve as an example of a data catalog that get its data from a CKAN Instance. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/ckan-ssg/README.md`
- **Getting Started** (project_doc): This is a Next.js https://nextjs.org/ project bootstrapped with create-next-app https://github.com/vercel/next.js/tree/canary/packages/create-next-app . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/ckan/README.md`
- **How to use** (project_doc): This example creates a portal/showcase for a single dataset. The dataset should be a Frictionless dataset data package fd i.e. there should be a datapackage.json . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/dataset-frictionless/README.md`
- **Data** (project_doc): ! goodtables.io https://goodtables.io/badge/github/datasets/country-codes.svg https://goodtables.io/github/datasets/country-codes Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/dataset-frictionless/public/country-codes/README.md`
- **Data** (project_doc): CBOE Volatility Index VIX time-series dataset including daily open, close, high and low. The CBOE Volatility Index VIX is a key measure of market expectations of near-term volatility conveyed by S&P 500 stock index option prices introduced in 1993. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/dataset-frictionless/public/dataset/README.md`
- **PortalJS Demo replicating the FiveThirtyEight data portal** (project_doc): PortalJS Demo replicating the FiveThirtyEight data portal Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/fivethirtyeight/README.md`
- **FiveThirtyEight Dataset Build Script** (project_doc): FiveThirtyEight Dataset Build Script Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/fivethirtyeight/scripts/README.md`
- **A data catalog with data on GitHub** (project_doc): This example showcases a simple data catalog that get its data from a list of GitHub repos that serve as datasets. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/github-backed-catalog/README.md`
- **Readme** (project_doc): PortalJS Learn Example - https://portaljs.com/docs Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/learn/README.md`
- **A data catalog with data on GitHub** (project_doc): This example showcases a simple data catalog that get its data from a list of GitHub repos that serve as datasets. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/openspending/README.md`
- **Readme** (project_doc): Spending Data Handbook ====================== Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/openspending/content/resources/handbook/README.md`
- **PortalJS Catalog Template dynamic routes** (project_doc): PortalJS Catalog Template dynamic routes Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/portaljs-catalog/README.md`
- **Metadata profiles** (project_doc): The metadata-profile contract is the seam that defines how a dataset's schema and descriptive metadata are authored and surfaced. It sits beside the other two seams: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/portaljs-catalog/lib/metadata/README.md`
- **Data providers** (project_doc): The data-provider contract is the seam that keeps a PortalJS portal decoupled from where its data lives. The three surfaces — the home page, the /search catalog, and the /@ / showcase — read datasets only through a DataProvider . Swap the provider and the source of data changes without touching a single page. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/portaljs-catalog/lib/providers/README.md`
- **Data query the compute seam** (project_doc): Where the data-provider contract ../providers answers which datasets exist , the data-query contract answers how to compute over a dataset's data — running SQL over it, beyond a flat-file preview. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/portaljs-catalog/lib/query/README.md`
- **PortalJS Template** (project_doc): This is the canonical template used by the /portaljs-new-portal skill. It is a real Next.js project — you can run it directly. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/portaljs-template/README.md`
- **Getting started** (project_doc): This demo d ata portal is designed for https://hatespeechdata.com. It catalogs datasets annotated for hate speech, online abuse, and offensive language which are useful for training a natural language processing system to detect this online abuse. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/turing/README.md`
- **Giftless on Cloudflare Containers — production host** (project_doc): Giftless on Cloudflare Containers — production host Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `giftless/cloudflare/README.md`
- **CKAN API client - JavaScript** (project_doc): Among other JS clients publicly available, the objectives of this one are: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `packages/ckan-api-client-js/README.md`
- **PortalJS CKAN Library** (project_doc): This is a library intended for the use with a CKAN Backend, it is composed of: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `packages/ckan/README.md`
- **@portaljs/core** (project_doc): Core Portal.JS package containing components, styles, and utils. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `packages/core/README.md`
- **create-portaljs** (project_doc): Scaffold a PortalJS https://github.com/datopian/portaljs data portal in one command. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `packages/create-portaljs/README.md`
- **AGENTS.md** (project_doc): The agent guide for this repository lives in CLAUDE.md ./CLAUDE.md — it's the single source of truth for conventions, repo structure, component selection, and how to build PortalJS data portals with an AI assistant. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `AGENTS.md`
- **PortalJS — AI Development Guide** (project_doc): PortalJS is a Next.js framework for building data portals and catalogs. This file teaches AI assistants the conventions, patterns, and idioms used across this repo. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CLAUDE.md`
- **Installing PortalJS skills** (project_doc): PortalJS ships a set of Claude Code https://docs.claude.com/en/docs/claude-code skills that scaffold and extend data portals: /portaljs-new-portal , /portaljs-add-dataset , /portaljs-add-chart , /portaljs-add-map , and /portaljs-deploy . They run from any project — /portaljs-new-portal fetches the template from GitHub when you're not inside a clone of this repo. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/INSTALL.md`
- **Our repository** (project_doc): https://github.com/datopian/datahub Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md`
- **How to contribute** (project_doc): OpenSpending is a project that aims to make public financial data more accessible, understandable, and usable. It is powered by PortalJS, a framework for building data portals that are fast, secure, and easy to customize. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `examples/openspending/content/contributing.md`
- **PortalJS skill-suite naming audit** (project_doc): Status: inventory + recommendation no renames performed — see bead po-ok8 . Scope: the OSS agentic skills PortalJS ships into a user's Claude Code skill namespace. Gas Town internal commands done , handoff , review are excluded — they are not shipped see scripts/install-portaljs-skills.sh and .claude-plugin/plugin.json . Decision owners: Anu / Joao. STOP at the recommendation — the actual rename is a follow-up bead. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/skill-naming-audit.md`
- **Profile** (project_doc): Manage your PortalJS Cloud profile, password, plan, and API keys. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/account.md`
- **Browse datasets** (project_doc): Browse, create, edit, and delete datasets and resources in PortalJS Cloud, including the DCAT metadata schema and table schema. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/datasets.md`
- **Sign up** (project_doc): Create your PortalJS Cloud account, sign in, and find your way around the admin dashboard. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/getting-started.md`
- **Permissions** (project_doc): Create and manage groups to categorize datasets in PortalJS Cloud. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/groups.md`
- **Supported sources** (project_doc): Automatically sync datasets from external sources into PortalJS Cloud. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/harvesters.md`
- **Contents** (project_doc): Administrator guide for PortalJS Cloud: manage datasets, organizations, users, visualizations, and your public portal. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/index.md`
- **Find your MCP URL** (project_doc): Connect AI chatbots to your PortalJS Cloud portal through the MCP server. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/mcp-server.md`
- **The main organization** (project_doc): Manage organizations, members, roles, and sysadmins in PortalJS Cloud. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/organizations.md`
- **How the portal works** (project_doc): Deploy your public PortalJS Cloud portal, customize its repository, and understand what visitors see. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/portal.md`
- **Permissions** (project_doc): Invite, edit, and remove users in your PortalJS Cloud portal. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/users.md`
- **Permissions** (project_doc): Publish and manage visualizations and data apps in PortalJS Cloud. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/cloud/docs/visualizations.md`
- **How it works** (project_doc): Datopian-managed static hosting for PortalJS portals — /portaljs-deploy to a live .arc.portaljs.com URL. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/arc.md`
- **Three questions** (project_doc): The advisory layer — how the skills turn three questions about your needs into a concrete, scaffoldable stack. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/architecture/decision-framework.md`
- **Where skills live** (project_doc): Write your own agentic command. Skills are markdown files with a clear input contract, described output, and structured errors. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/authoring-skills.md`
- **CKAN** (project_doc): PortalJS is decoupled by default — the frontend talks to any backend over an API. Integration notes per backend. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/backends.md`
- **1. Home — the landing page** (project_doc): Every data portal is built from three surfaces — Home, Catalog, and Showcase. Understand these and the template, routes, and skills all fall into place. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/core-concepts.md`
- **The guides** (project_doc): Task-oriented "how do I…" guides. Each shows the fast AI/skill path and the equivalent by-hand path — the same project either way. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides.md`
- **The AI path — /portaljs-add-chart** (project_doc): Add a line, bar, area, pie, or scatter chart to a dataset page — with /portaljs-add-chart, or by hand. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/add-a-chart.md`
- **The AI path — /portaljs-add-dataset** (project_doc): Add a CSV, TSV, or JSON dataset and render it as a sortable table — with /portaljs-add-dataset, or by hand. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/add-tabular-data.md`
- **The AI path — /portaljs-connect-ckan** (project_doc): Wire the portal to a live CKAN instance over its API — the decoupled path, with /portaljs-connect-ckan or by hand. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/connect-a-ckan-backend.md`
- **The AI path — /portaljs-deploy → PortalJS Arc** (project_doc): Publish to PortalJS Arc with /portaljs-deploy, or self-host the static export anywhere. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/deploy.md`
- **The AI path — /portaljs-add-map** (project_doc): Put a GeoJSON dataset on an interactive map — with /portaljs-add-map, or by hand with react-leaflet. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/render-a-map.md`
- **The problem with committing big files** (project_doc): Three tiers for dataset bytes — inline, Git-LFS + R2 via Giftless, and external Parquet queried in place — and how to pick between them. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/scaling-data.md`
- **The AI path — bring your own DESIGN.md** (project_doc): Bring your own branding — hand your AI assistant a DESIGN.md, or edit Tailwind directly. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/guides/theming.md`
- **Two ways to build** (project_doc): PortalJS is the AI-native framework for building data portals. Two paths to a live portal — describe it to your AI assistant, or build it by hand. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `site/content/docs/index.md`

## Evidence Index

- Indexed 80 evidence entries.

- **Changesets** (documentation): Hello and welcome! This folder has been automatically generated by @changesets/cli , a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it in our repository https://github.com/changesets/changesets Evidence: `.changeset/README.md`
- **Quickstart** (documentation): PortalJS The AI-native framework for building data portals. Describe the portal you want — your agent helps you choose an architecture, scaffolds it, and loads your data. Docs · Discussions · Report a bug Evidence: `README.md`
- **Giftless on Cloudflare R2 — staging deployment** (documentation): Giftless on Cloudflare R2 — staging deployment Evidence: `giftless/README.md`
- **Flowershow default template** (documentation): Flowershow default app template. Uses Next.js with Tailwind and MDX. Evidence: `site/README.md`
- **Deployment** (documentation): This is a repo intended to serve as an example of a data catalog that get its data from a CKAN Instance. Evidence: `examples/ckan-ssg/README.md`
- **Getting Started** (documentation): This is a Next.js https://nextjs.org/ project bootstrapped with create-next-app https://github.com/vercel/next.js/tree/canary/packages/create-next-app . Evidence: `examples/ckan/README.md`
- **How to use** (documentation): This example creates a portal/showcase for a single dataset. The dataset should be a Frictionless dataset data package fd i.e. there should be a datapackage.json . Evidence: `examples/dataset-frictionless/README.md`
- **Data** (documentation): ! goodtables.io https://goodtables.io/badge/github/datasets/country-codes.svg https://goodtables.io/github/datasets/country-codes Evidence: `examples/dataset-frictionless/public/country-codes/README.md`
- **Data** (documentation): CBOE Volatility Index VIX time-series dataset including daily open, close, high and low. The CBOE Volatility Index VIX is a key measure of market expectations of near-term volatility conveyed by S&P 500 stock index option prices introduced in 1993. Evidence: `examples/dataset-frictionless/public/dataset/README.md`
- **PortalJS Demo replicating the FiveThirtyEight data portal** (documentation): PortalJS Demo replicating the FiveThirtyEight data portal Evidence: `examples/fivethirtyeight/README.md`
- **FiveThirtyEight Dataset Build Script** (documentation): FiveThirtyEight Dataset Build Script Evidence: `examples/fivethirtyeight/scripts/README.md`
- **A data catalog with data on GitHub** (documentation): This example showcases a simple data catalog that get its data from a list of GitHub repos that serve as datasets. Evidence: `examples/github-backed-catalog/README.md`
- **Readme** (documentation): PortalJS Learn Example - https://portaljs.com/docs Evidence: `examples/learn/README.md`
- **A data catalog with data on GitHub** (documentation): This example showcases a simple data catalog that get its data from a list of GitHub repos that serve as datasets. Evidence: `examples/openspending/README.md`
- **Readme** (documentation): Spending Data Handbook ====================== Evidence: `examples/openspending/content/resources/handbook/README.md`
- **PortalJS Catalog Template dynamic routes** (documentation): PortalJS Catalog Template dynamic routes Evidence: `examples/portaljs-catalog/README.md`
- **Metadata profiles** (documentation): The metadata-profile contract is the seam that defines how a dataset's schema and descriptive metadata are authored and surfaced. It sits beside the other two seams: Evidence: `examples/portaljs-catalog/lib/metadata/README.md`
- **Data providers** (documentation): The data-provider contract is the seam that keeps a PortalJS portal decoupled from where its data lives. The three surfaces — the home page, the /search catalog, and the /@ / showcase — read datasets only through a DataProvider . Swap the provider and the source of data changes without touching a single page. Evidence: `examples/portaljs-catalog/lib/providers/README.md`
- **Data query the compute seam** (documentation): Where the data-provider contract ../providers answers which datasets exist , the data-query contract answers how to compute over a dataset's data — running SQL over it, beyond a flat-file preview. Evidence: `examples/portaljs-catalog/lib/query/README.md`
- **PortalJS Template** (documentation): This is the canonical template used by the /portaljs-new-portal skill. It is a real Next.js project — you can run it directly. Evidence: `examples/portaljs-template/README.md`
- **Getting started** (documentation): This demo d ata portal is designed for https://hatespeechdata.com. It catalogs datasets annotated for hate speech, online abuse, and offensive language which are useful for training a natural language processing system to detect this online abuse. Evidence: `examples/turing/README.md`
- **Giftless on Cloudflare Containers — production host** (documentation): Giftless on Cloudflare Containers — production host Evidence: `giftless/cloudflare/README.md`
- **CKAN API client - JavaScript** (documentation): Among other JS clients publicly available, the objectives of this one are: Evidence: `packages/ckan-api-client-js/README.md`
- **PortalJS CKAN Library** (documentation): This is a library intended for the use with a CKAN Backend, it is composed of: Evidence: `packages/ckan/README.md`
- **@portaljs/core** (documentation): Core Portal.JS package containing components, styles, and utils. Evidence: `packages/core/README.md`
- **create-portaljs** (documentation): Scaffold a PortalJS https://github.com/datopian/portaljs data portal in one command. Evidence: `packages/create-portaljs/README.md`
- **Package** (package_manifest): { "name": "portaljs", "workspaces": "./packages/ " , "version": "0.0.0", "license": "MIT", "scripts": { "changeset": "changeset", "release": "changeset publish", "gen:skills": "node scripts/gen-skills-docs.mjs", "gen:skills:check": "node scripts/gen-skills-docs.mjs --check" }, "private": true, "devDependencies": { "@changesets/changelog-github": "^0.4.8", "@changesets/cli": "^2.26.1", "@types/node": "18.14.2", "@types/react": "18.0.28", "@types/react-dom": "18.0.11", "@typescript-eslint/eslint-plugin": "^5.36.1", "@typescript-eslint/parser": "^5.36.1", "eslint": "~8.15.0", "eslint-config-prettier": "8.1.0", "prettier": "^2.6.2", "typescript": "~4.9.5" } } Evidence: `package.json`
- **Package** (package_manifest): { "name": "@flowershow/template", "private": true, "version": "1.0.0", "engines": { "node": " =20 <21" }, "scripts": { "dev": "npm run mddb && next dev", "build": "next build", "prebuild": "npm run mddb && node ./scripts/fix-symlinks.mjs", "postbuild": "next-sitemap && node ./scripts/generate-feeds.js", "start": "next start", "mddb": "mddb content", "smoke:markdown": "node ./scripts/smoke-markdown-pages.mjs" }, "dependencies": { "@docsearch/react": "^4.6.3", "@flowershow/remark-wiki-link": "^3.4.0", "@headlessui/react": "^2.2.10", "@heroicons/react": "^2.0.18", "@lottiefiles/react-lottie-player": "^3.6.0", "@portaljs/core": "^1.0.6", "@portaljs/remark-callouts": "^1.0.5", "@portaljs/remark-… Evidence: `site/package.json`
- **Package** (package_manifest): { "name": "arc-api", "private": true, "type": "module", "scripts": { "test": "vitest run", "dev": "wrangler dev", "deploy": "wrangler deploy", "typecheck": "tsc --noEmit", "migrate:staging": "wrangler d1 migrations apply portaljs-arc-staging --remote" }, "devDependencies": { "@cloudflare/workers-types": "^4.20240909.0", "typescript": "^5.5.4", "vitest": "^2.1.1", "wrangler": "^3.78.0" } } Evidence: `cloud/api/package.json`
- **Package** (package_manifest): { "name": "arc-auth", "private": true, "type": "module", "scripts": { "test": "vitest run", "dev": "wrangler dev", "deploy": "wrangler deploy", "typecheck": "tsc --noEmit" }, "devDependencies": { "@cloudflare/workers-types": "^4.20240909.0", "typescript": "^5.5.4", "vitest": "^2.1.1", "wrangler": "^3.78.0" } } Evidence: `cloud/auth/package.json`
- **Package** (package_manifest): { "name": "arc-router", "private": true, "type": "module", "scripts": { "test": "vitest run", "dev": "wrangler dev", "deploy": "wrangler deploy", "typecheck": "tsc --noEmit" }, "devDependencies": { "@cloudflare/workers-types": "^4.20240909.0", "typescript": "^5.5.4", "vitest": "^2.1.1", "wrangler": "^3.78.0" } } Evidence: `cloud/worker/package.json`
- **Package** (package_manifest): { "name": "my-app", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint" }, "dependencies": { "@heroicons/react": "^2.0.17", "@portaljs/ckan": "^0.0.2", "@portaljs/remark-wiki-link": "^1.0.4", "next": "13.3.1", "next-seo": "^6.0.0", "octokit": "^2.0.14", "react": "18.2.0", "react-dom": "18.2.0", "react-markdown": "^8.0.7", "remark-gfm": "^3.0.1" }, "devDependencies": { "@tailwindcss/typography": "^0.5.9", "@types/node": "18.16.0", "@types/react": "18.0.38", "@types/react-dom": "18.0.11", "autoprefixer": "^10.4.14", "eslint": "8.39.0", "eslint-config-next": "13.3.1", "postcss": "^8.4.23", "tailwindcss": "^3.3.1… Evidence: `examples/ckan-ssg/package.json`
- **Package** (package_manifest): { "name": "ckan", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "prebuild": "npm run mddb", "build": "next build", "start": "next start", "lint": "next lint", "mddb": "mddb ./content" }, "dependencies": { "@githubocto/flat-ui": "^0.14.1", "@heroicons/react": "^2.0.18", "@portaljs/ckan": "^0.0.2", "@portaljs/components": "0.1.6", "@portaljs/core": "^1.0.5", "@portaljs/remark-callouts": "^1.0.5", "@portaljs/remark-embed": "^1.0.4", "@portaljs/remark-wiki-link": "^1.0.4", "@tailwindcss/typography": "^0.5.9", "@types/node": "20.2.3", "@types/react": "18.2.6", "@types/react-dom": "18.2.4", "autoprefixer": "10.4.14", "eslint": "8.41.0", "eslint-config-next": "13.4.3", "isom… Evidence: `examples/ckan/package.json`
- **Package** (package_manifest): { "name": "portal", "description": "The data presentation framework", "author": "Datopian", "license": "MIT", "version": "0.1.0", "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "export": "yarn build && next export", "test": "jest --coverage" }, "dependencies": { "@tailwindcss/typography": "^0.4.0", "autoprefixer": "^10.0.4", "datapackage-render": "git+https://github.com/frictionlessdata/datapackage-render-js.git", "frictionless.js": "^0.13.4", "next": "latest", "portal": "https://github.com/datopian/portal.js.git 25f3c6b32a60c4f922394c85d2d7d03fe2cbc143", "postcss": "^8.2.10", "react": "^17.0.1", "react-dom": "^17.0.1", "remark": "^13.0.0", "remark-html": "^13… Evidence: `examples/dataset-frictionless/package.json`
- **Package** (package_manifest): { "name": "fiverthirtyeight-example", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "build:datasets": "node scripts/build-datasets.js", "start": "next start", "lint": "next lint" }, "dependencies": { "@headlessui/react": "^1.7.14", "@heroicons/react": "^2.0.18", "@portaljs/components": "^0.1.8", "@portaljs/core": "^1.0.5", "@portaljs/remark-wiki-link": "^1.0.4", "@tailwindcss/typography": "^0.5.9", "@types/node": "20.1.1", "@types/react": "18.2.6", "@types/react-dom": "18.2.4", "autoprefixer": "10.4.14", "eslint": "8.40.0", "eslint-config-next": "13.4.1", "flexsearch": "^0.7.31", "next": "13.4.1", "next-mdx-remote": "^4.4.1", "next-seo": "^6.0.0… Evidence: `examples/fivethirtyeight/package.json`
- **Package** (package_manifest): { "name": "my-app", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint", "prettier": "prettier --write ." }, "dependencies": { "@portaljs/components": "^0.1.6", "@portaljs/core": "^1.0.5", "@portaljs/remark-callouts": "^1.0.5", "@portaljs/remark-embed": "^1.0.4", "@portaljs/remark-wiki-link": "^1.0.4", "@types/node": "18.16.0", "@types/react": "18.0.38", "@types/react-dom": "18.0.11", "eslint": "8.39.0", "eslint-config-next": "13.3.1", "mddb": "^0.1.9", "next": "13.4.3", "next-mdx-remote": "^4.4.1", "next-seo": "^6.0.0", "octokit": "^2.0.14", "react": "18.2.0", "react-dom": "18.2.0", "react-markdown": "^8.0.7… Evidence: `examples/github-backed-catalog/package.json`
- **Package** (package_manifest): { "name": "basic-example", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint", "export": "npm run build && next export -o out", "prebuild": "npm run mddb", "mddb": "mddb ./content" }, "dependencies": { "@githubocto/flat-ui": "^0.14.1", "@heroicons/react": "^2.0.17", "@opentelemetry/api": "^1.4.0", "@portaljs/components": "^0.1.8", "@portaljs/core": "^1.0.5", "@portaljs/remark-callouts": "^1.0.5", "@portaljs/remark-embed": "^1.0.4", "@portaljs/remark-wiki-link": "^1.0.4", "@tanstack/react-table": "^8.8.5", "flexsearch": "0.7.21", "gray-matter": "^4.0.3", "hastscript": "^7.2.0", "mddb": "^0.1.9", "mdx-mermaid"… Evidence: `examples/learn/package.json`
- **Package** (package_manifest): { "name": "my-app", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint", "prebuild": "npm run mddb", "mddb": "mddb ./content", "test": "vitest" }, "dependencies": { "@githubocto/flat-ui": "^0.14.1", "@headlessui/react": "^1.7.14", "@heroicons/react": "^2.0.18", "@octokit/plugin-throttling": "^5.2.2", "@portaljs/ckan": "^0.0.2", "@portaljs/components": "0.1.12", "@portaljs/core": "^1.0.5", "@portaljs/remark-callouts": "^1.0.5", "@portaljs/remark-embed": "^1.0.4", "@portaljs/remark-wiki-link": "^1.0.4", "@tailwindcss/typography": "^0.5.9", "@types/flexsearch": "^0.7.3", "@types/node": "20.2.3", "@types/react":… Evidence: `examples/openspending/package.json`
- **Package** (package_manifest): { "name": " PROJECT SLUG ", "version": "0.1.0", "private": true, "scripts": { "generate:dcat": "tsx scripts/generate-dcat.ts", "predev": "npm run generate:dcat", "dev": "next dev", "prebuild": "npm run generate:dcat", "build": "next build", "check-export": "node scripts/check-export.mjs", "start": "next start" }, "dependencies": { "@duckdb/duckdb-wasm": "^1.32.0", "@heroicons/react": "^2.0.0", "@tanstack/react-table": "^8.21.0", "next": "^16.2.7", "papaparse": "^5.4.0", "react": "^19.2.0", "react-dom": "^19.2.0" }, "devDependencies": { "@tailwindcss/typography": "^0.5.0", "@types/node": "^20.0.0", "@types/papaparse": "^5.3.0", "@types/react": "^19.0.0", "@types/react-dom": "^19.0.0", "autop… Evidence: `examples/portaljs-catalog/package.json`
- **Package** (package_manifest): { "name": " PROJECT SLUG ", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start" }, "dependencies": { "@heroicons/react": "^2.0.0", "@tanstack/react-table": "^8.21.0", "next": "14.2.35", "papaparse": "^5.4.0", "react": "18.3.1", "react-dom": "18.3.1" }, "devDependencies": { "@tailwindcss/typography": "^0.5.0", "@types/node": "^20.0.0", "@types/papaparse": "^5.3.0", "@types/react": "^18.0.0", "@types/react-dom": "^18.0.0", "autoprefixer": "^10.0.0", "postcss": "^8.0.0", "tailwindcss": "^3.0.0", "typescript": "^5.0.0" } } Evidence: `examples/portaljs-template/package.json`
- **Package** (package_manifest): { "name": "tailwindui-template", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint", "prebuild": "npm run mddb", "mddb": "mddb ./content" }, "browserslist": "defaults, not ie <= 11", "dependencies": { "@headlessui/react": "^1.7.13", "@heroicons/react": "^2.0.17", "@mapbox/rehype-prism": "^0.8.0", "@mdx-js/loader": "^2.1.5", "@mdx-js/react": "^2.1.5", "@next/mdx": "^13.0.2", "@opentelemetry/api": "^1.4.0", "@portaljs/core": "^1.0.5", "@portaljs/remark-callouts": "^1.0.5", "@portaljs/remark-embed": "^1.0.4", "@portaljs/remark-wiki-link": "^1.0.4", "@tailwindcss/forms": "^0.5.3", "@tailwindcss/typography": "^0.… Evidence: `examples/turing/package.json`
- **Package** (package_manifest): { "name": "giftless-cloudflare", "version": "0.1.0", "private": true, "description": "Cloudflare Containers deploy of the Giftless LFS-on-R2 host production ", "scripts": { "deploy": "./scripts/deploy.sh", "smoke": "./scripts/smoke-remote.sh", "typecheck": "tsc --noEmit" }, "dependencies": { "@cloudflare/containers": "^0.3.7" }, "devDependencies": { "@cloudflare/workers-types": "^4.20250101.0", "typescript": "^5.5.0", "wrangler": "^4.0.0" } } Evidence: `giftless/cloudflare/package.json`
- **Package** (package_manifest): { "name": "@portaljs/ckan-api-client-js", "version": "1.4.0", "description": "", "main": "dist/index.cjs.js", "module": "dist/index.esm.js", "types": "dist/index.d.ts", "scripts": { "test": "npm run build && mocha -r dotenv/config", "clean": "rimraf dist/ ", "build": "rollup -c", "prepare": "npm run build" }, "author": "Datopian Viderum Inc. trading as ", "license": "ISC", "devDependencies": { "@changesets/cli": "^2.27.7", "@rollup/plugin-commonjs": "^26.0.1", "@rollup/plugin-node-resolve": "^15.2.3", "@rollup/plugin-typescript": "^11.1.6", "@types/node": "^20.14.2", "chai": "^5.2.0", "chai-as-promised": "^8.0.1", "dotenv": "^16.5.0", "mocha": "^11.4.0", "rimraf": "^5.0.7", "rollup": "^4.18… Evidence: `packages/ckan-api-client-js/package.json`
- **Package** (package_manifest): { "name": "@portaljs/ckan", "version": "0.1.0", "type": "module", "description": "https://portaljs.com", "keywords": "data portal", "data catalog", "table", "charts", "visualization" , "scripts": { "build": "tsc && vite build && npm run build-tailwind", "lint": "eslint src --ext ts,tsx --report-unused-disable-directives --max-warnings 0", "build-tailwind": "NODE ENV=production npx tailwindcss -o ./dist/styles.css --minify", "prepare": "npm run build" }, "peerDependencies": { "react": "^18.2.0", "react-dom": "^18.2.0" }, "files": "dist" , "devDependencies": { "@types/react": "^18.0.28", "@types/react-dom": "^18.0.11", "@typescript-eslint/eslint-plugin": "^5.57.1", "@typescript-eslint/parser"… Evidence: `packages/ckan/package.json`
- **Package** (package_manifest): { "name": "@portaljs/core", "version": "1.0.9", "description": "Core Portal.JS components, configs and utils.", "repository": { "type": "git", "url": "git+https://github.com/datopian/portaljs.git", "directory": "packages/core" }, "author": "Rufus Pollock", "license": "MIT", "bugs": { "url": "https://github.com/datopian/portaljs/issues" }, "homepage": "https://github.com/datopian/portaljs readme", "publishConfig": { "access": "public" }, "scripts": { "clean": "rimraf dist", "build": "rollup -c rollup.config.mjs", "prepare": "npm run build" }, "files": "dist" , "type": "module", "module": "./dist/index.js", "types": "./dist/src/index.d.ts", "exports": { ".": { "types": "./dist/src/index.d.ts"… Evidence: `packages/core/package.json`
- **Package** (package_manifest): { "name": "create-portaljs", "version": "0.6.0", "description": "Scaffold a PortalJS data portal — npm create portaljs@latest", "type": "module", "bin": { "create-portaljs": "index.mjs" }, "files": "index.mjs", "README.md" , "engines": { "node": " =18" }, "keywords": "portaljs", "data-portal", "create", "scaffold", "cli", "nextjs" , "homepage": "https://github.com/datopian/portaljs/tree/main/packages/create-portaljs", "repository": { "type": "git", "url": "https://github.com/datopian/portaljs.git", "directory": "packages/create-portaljs" }, "license": "MIT", "publishConfig": { "access": "public" }, "dependencies": { "giget": "^1.2.3", "prompts": "^2.4.2" } } Evidence: `packages/create-portaljs/package.json`
- **AGENTS.md** (documentation): The agent guide for this repository lives in CLAUDE.md ./CLAUDE.md — it's the single source of truth for conventions, repo structure, component selection, and how to build PortalJS data portals with an AI assistant. Evidence: `AGENTS.md`
- **PortalJS — AI Development Guide** (documentation): PortalJS is a Next.js framework for building data portals and catalogs. This file teaches AI assistants the conventions, patterns, and idioms used across this repo. Evidence: `CLAUDE.md`
- **Installing PortalJS skills** (documentation): PortalJS ships a set of Claude Code https://docs.claude.com/en/docs/claude-code skills that scaffold and extend data portals: /portaljs-new-portal , /portaljs-add-dataset , /portaljs-add-chart , /portaljs-add-map , and /portaljs-deploy . They run from any project — /portaljs-new-portal fetches the template from GitHub when you're not inside a clone of this repo. Evidence: `.claude/INSTALL.md`
- **Our repository** (documentation): https://github.com/datopian/datahub Evidence: `CONTRIBUTING.md`
- **How to contribute** (documentation): OpenSpending is a project that aims to make public financial data more accessible, understandable, and usable. It is powered by PortalJS, a framework for building data portals that are fast, secure, and easy to customize. Evidence: `examples/openspending/content/contributing.md`
- **Marketplace** (structured_config): { "name": "datopian-portaljs", "owner": { "name": "Datopian", "url": "https://www.datopian.com" }, "metadata": { "description": "PortalJS agentic skills — build data portals with AI.", "version": "0.1.0" }, "plugins": { "name": "portaljs", "source": ".", "description": "Scaffold and extend PortalJS data portals: /portaljs-new-portal, /portaljs-add-dataset, /portaljs-add-chart, /portaljs-add-map, /portaljs-deploy." } } Evidence: `.claude-plugin/marketplace.json`
- **Plugin** (structured_config): { "name": "portaljs", "version": "0.1.0", "description": "Agentic skills for building PortalJS data portals — recommend an architecture, scaffold a portal, add datasets, charts, and maps, connect a CKAN backend, deploy, and audit data quality.", "author": { "name": "Datopian", "url": "https://www.datopian.com" }, "homepage": "https://github.com/datopian/portaljs", "repository": "https://github.com/datopian/portaljs", "license": "MIT", "keywords": "portaljs", "data-portal", "ckan", "nextjs", "data-catalog" , "commands": "./.claude/commands/portaljs-architect.md", "./.claude/commands/portaljs-new-portal.md", "./.claude/commands/portaljs-add-dataset.md", "./.claude/commands/portaljs-add-resour… Evidence: `.claude-plugin/plugin.json`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `license`
- **PortalJS skill-suite naming audit** (documentation): Status: inventory + recommendation no renames performed — see bead po-ok8 . Scope: the OSS agentic skills PortalJS ships into a user's Claude Code skill namespace. Gas Town internal commands done , handoff , review are excluded — they are not shipped see scripts/install-portaljs-skills.sh and .claude-plugin/plugin.json . Decision owners: Anu / Joao. STOP at the recommendation — the actual rename is a follow-up bead. Evidence: `docs/skill-naming-audit.md`
- **Profile** (documentation): Your account page is split into two tabs: Profile personal info and plan and API keys programmatic access . Evidence: `site/content/cloud/docs/account.md`
- **Browse datasets** (documentation): Datasets are the core unit of content in PortalJS Cloud. Each dataset has metadata title, description, tags, license, organization, group and one or more resources the actual files or URLs . Evidence: `site/content/cloud/docs/datasets.md`
- **Sign up** (documentation): This page walks you through creating your PortalJS Cloud account, signing in, and finding your way around the admin dashboard. Evidence: `site/content/cloud/docs/getting-started.md`
- **Permissions** (documentation): Groups categorize datasets thematically — for example, "Health", "Transport", "Open Budgets". A dataset can belong to multiple groups. Groups map to CKAN groups in the underlying catalog. Evidence: `site/content/cloud/docs/groups.md`
- **Supported sources** (documentation): Harvesters automatically pull datasets from external sources into your portal on a schedule — for example, mirroring a CKAN, DKAN, Socrata, or ArcGIS catalog. Evidence: `site/content/cloud/docs/harvesters.md`
- The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`.

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `.changeset/README.md`, `README.md`, `giftless/README.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `.changeset/README.md`, `README.md`, `giftless/README.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Overview**: importance `high`
  - source_paths: README.md, cloud/api/package.json, cloud/auth/package.json, cloud/worker/package.json, giftless/README.md
- **Lib**: importance `high`
  - source_paths: site/lib/common.ts, site/lib/computeFields.ts, site/lib/getAuthorsDetails.ts, site/lib/getGitHubData.ts, site/lib/getPageData.js
- **Lib**: importance `high`
  - source_paths: packages/ckan/src/lib/ckanapi.tsx, packages/ckan/src/lib/index.tsx, packages/ckan/src/lib/utils.ts
- **Src**: importance `high`
  - source_paths: packages/core/src/config/default.ts, packages/core/src/config/index.ts, packages/core/src/index.ts, packages/core/src/types/index.d.ts, packages/core/src/ui/Avatar/Avatar.tsx
- **Src**: importance `medium`
  - source_paths: packages/ckan/src/components/DatasetCard.tsx, packages/ckan/src/components/DatasetSearchFilters.tsx, packages/ckan/src/components/DatasetSearchForm.tsx, packages/ckan/src/components/ListOfDatasets.tsx, packages/ckan/src/components/Pagination.tsx
- **Src**: importance `medium`
  - source_paths: cloud/auth/src/device.ts, cloud/auth/src/email.ts, cloud/auth/src/html.ts, cloud/auth/src/index.ts, cloud/auth/src/ratelimit.ts
- **Src**: importance `medium`
  - source_paths: cloud/api/src/db.ts, cloud/api/src/index.ts, cloud/api/src/lfs.ts, cloud/api/src/untar.ts
- **Src**: importance `medium`
  - source_paths: packages/ckan-api-client-js/src/CkanRequest.ts, packages/ckan-api-client-js/src/index.ts, packages/ckan-api-client-js/src/types.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `97f522ba28db11d8c5f6e174faefcf752bccc030`
- inspected_files: `README.md`, `package.json`, `docs/skill-naming-audit.md`, `examples/ckan/.eslintrc.json`, `examples/ckan/README.md`, `examples/ckan/content/test.md`, `examples/ckan/lib/markdown.js`, `examples/ckan/lib/mddb.ts`, `examples/ckan/next.config.js`, `examples/ckan/package-lock.json`, `examples/ckan/package.json`, `examples/ckan/pages/api/cors.ts`, `examples/ckan/postcss.config.js`, `examples/ckan/tailwind.config.js`, `examples/ckan/tsconfig.json`, `examples/ckan-ssg/.eslintrc.json`, `examples/ckan-ssg/README.md`, `examples/ckan-ssg/index.d.ts`, `examples/ckan-ssg/next-env.d.ts`, `examples/ckan-ssg/next.config.js`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/datopian/portaljs
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/datopian/portaljs
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/datopian/portaljs
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/datopian/portaljs
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/datopian/portaljs
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.