Files
Rpa_Skills/rpa-dashboard-ai/templates/reference/web/index.html
T
VasanthandClaude Opus 5.5 8951ac05a5 AI skill: SKILL.md, AI contract, scrubbed references, eval fixture (d)
- rpa-dashboard-ai/SKILL.md: trigger description and the shared question flow;
  points at the no-AI frontend.md, themes and palette instead of copying them.
- templates/contract.md: runs, review rows, endpoints and the server approve gate.
- Superbill extracts: patient names and the client name removed, every file
  carries an EXAMPLE ONLY banner. tests/test_reference_scan.py checks both skills
  for patient data, internal IPs, credentials and keys.
- tests/fixtures/d-ai-extraction and its eval entry, which runs page_check_ai
  on the built folder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 15:13:55 +05:30

37 lines
1.8 KiB
HTML

<!doctype html>
<!-- EXAMPLE ONLY: an extract from the Superbill Review prototype, kept as reference for porting. ECW/eClinicalWorks, Tebra, 'Example Client', SPB_* tables and patient/ticket wording are that project's examples. Don't copy them into a new project. -->
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="icon" type="image/png" href="/logo-mark.png" />
<!--
Two webfonts, and only for the sign-in screen — Sora for its display type
(brand name, headline, button) and IBM Plex Sans for its body. Both are
carried over from the approved login mockup, which is the whole reason
they are here: the screen is meant to render identically to it.
The INTERFACE behind sign-in stays on the system stack, which is a
documented density decision for 11-13px data-dense lists, where a webfont
costs a network dependency to look almost identical to Segoe UI (see
DESIGN.md Typography). Neither family is set on `body`.
`display=swap` plus the full local fallback in each `.sb-login` rule is
what makes this safe on an internal network: if fonts.googleapis.com is
blocked the sign-in screen falls back to the system stack and every other
surface never wanted a webfont in the first place.
-->
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link
href="https://fonts.googleapis.com/css2?family=Sora:wght@600;700;800&family=IBM+Plex+Sans:wght@400;500;600&display=swap"
rel="stylesheet"
/>
<title>Extraction and Automation Tool</title>
</head>
<body>
<div id="root"></div>
<script type="module" src="/src/main.tsx"></script>
</body>
</html>