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.