privilege-admin-config-ui

Builds LMDB-backed admin config pages with Express routes and themed React components.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/curtismu7/AI-DEMO2 --skill privilege-admin-config-ui-curtismu7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: privilege-admin-config-ui
Source: https://github.com/curtismu7/AI-DEMO2/tree/main/.claude/skills/privilege-admin-config-ui
Command: npx skills add https://github.com/curtismu7/AI-DEMO2 --skill privilege-admin-config-ui-curtismu7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding a new settings or configuration page for PingOne Privilege or an MCP server in this repo normally requires re-deriving the same store/route/component pattern each time, risking duplicated setup docs, hardcoded URLs, and theming regressions. ## Core Features & Use Cases - Repeatable four-part recipe: an LMDB-backed config store, a thin Express route, a themed React component, and wiring into an existing page or tab bar. - Secret-safe storage pattern: masks secrets with hasX flags and treats blank fields as "keep existing value" on save. - Single source of truth: points to privilege/CURRENT-CONFIGURATION.md and SE1-Privilege-Shared-Demo.md instead of duplicating onboarding or live-state docs. - Use Case: When asked to "add an OAuth config form for banking-mcp on /privilege-demo", follow the recipe to create the store, route, and component with TDD, then verify with Jest and the UI build. ## Quick Start Ask the agent to add a new Privilege configuration page for your MCP server and it will follow this recipe to create the store, route, and themed React component.

Frequently Asked Questions about privilege-admin-config-ui

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

FAQPage Schema
How do I add a new admin config page for PingOne Privilege?▼

Follow the four-part recipe: create an LMDB-backed store in demo_api_server/services, add a thin Express route mounted in server.js, build a themed React component under src/components/privilege, and wire it into the host page as a tab.

How should secrets be stored in an LMDB config store?▼

Never return raw secret values from a get call; return only a hasX true/false flag. On save, treat a blank field as "keep the existing value" rather than wiping the stored secret.

What theming tokens should React components use in this repo?▼

Use --th-*, --font-size-*, and --radius-* tokens defined in src/index.css, and grep the actual token names before using them. The theming-ratchet test fails on literal px radii or themed backgrounds without explicit ink colors.

Should a Test Connection button fake success when the platform is blocked?▼

No. Make the real upstream call and report the real status and body. A documented platform blocker surfacing as a live 401 is the correct, honest result rather than a swallowed 500 or fake success.

When should I duplicate Privilege setup docs into the UI?▼

Never. Link out to privilege/SE1-Privilege-Shared-Demo.md for onboarding steps and privilege/CURRENT-CONFIGURATION.md for live state, since an earlier in-app checklist drifted stale and was deleted.