reuse-surface/docs/catalog/index.html

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Capability Catalog — helix_forge</title>
  <style>
    body { font-family: system-ui, sans-serif; margin: 2rem; line-height: 1.5; }
    h1 { margin-bottom: 0.2rem; }
    .subtitle { color: #555; margin-bottom: 2rem; }
    section { margin-bottom: 2rem; }
    .card { border: 1px solid #ddd; border-radius: 8px; padding: 1rem; margin: 1rem 0; }
    .meta { color: #444; font-size: 0.95rem; }
    .path { font-size: 0.85rem; color: #666; }
  </style>
</head>
<body>
  <h1>Capability Catalog</h1>
  <p class="subtitle">Updated 2026-10-13 · 3 entries</p>
  <section><h2>helix_forge</h2>
<article class="card">
  <h3>Capability Registration</h3>
  <p class="meta"><code>capability.registry.register</code> · D3 / A4 / C2 / R3</p>
  <p>Register a new capability so it becomes visible for planning and implementation reuse.</p>
  <p class="path">registry/capabilities/capability.registry.register.md</p>
</article>
<article class="card">
  <h3>Registry Entry Validation</h3>
  <p class="meta"><code>capability.registry.validate</code> · D4 / A3 / C3 / R3</p>
  <p>Validate capability registry entries against schema, index consistency, and relation integrity.</p>
  <p class="path">registry/capabilities/capability.registry.validate.md</p>
</article></section>
<section><h2>infotech</h2>
<article class="card">
  <h3>Headless Browser Automation</h3>
  <p class="meta"><code>capability.infotech.headless-browser</code> · D3 / A2 / C2 / R2</p>
  <p>Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations.</p>
  <p class="path">registry/capabilities/capability.infotech.headless-browser.md</p>
</article></section>
</body>
</html>