🎯

hook-protocol

🎯Skill

from jtapias92672/onedrive_1_1-19-2026-2

VibeIndex|
What it does

Manages secure, protocol-specific communication hooks for inter-package data exchange and validation within the FORGE pipeline's microservice architecture.

πŸ“¦

Part of

jtapias92672/onedrive_1_1-19-2026-2(19 items)

hook-protocol

Installation

npxRun with npx
npx jest tests/unit/
πŸ“– Extracted from docs: jtapias92672/onedrive_1_1-19-2026-2
1Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

Overview

FORGE Complete Pipeline

Full Figma β†’ React β†’ Mendix Pipeline

Total: 9 packages, 108 TypeScript files, ~35,000 lines of code

Package Overview

Package Epic Files Lines Status

answer-contract 02 9 ~2,600 βœ… Complete

convergence-engine 04 11 ~2,700 βœ… Complete

figma-parser 05 15 ~4,900 βœ… Complete

mcp-gateway 2.5 10 ~4,500 βœ… Complete

forge-c 03 9 ~4,250 βœ… Complete

react-generator 06 11 ~3,700 βœ… Complete

evidence-packs 08 7 ~1,900 βœ… Complete

mendix-integration 07 10 ~2,000 βœ… Complete

validators 14.1 12 ~5,000 βœ… Complete

Pipeline Flow

Figma Design

β”‚

β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ figma-parser β”‚ Epic 05 - Parse Figma JSON

β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ react-generator β”‚ Epic 06 - Generate React/Tailwind

β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β–Ό β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ answer-contract β”‚ β”‚ mendix-integrationβ”‚ Epic 07

β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚convergence-engineβ”‚ Epic 04 - Iterative Refinement

β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β–Ό β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ validators β”‚ β”‚evidence-packsβ”‚ Epic 08

β”‚ (Wolfram API) β”‚ β”‚ (Audit Trail)β”‚

β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ forge-c β”‚ Epic 03 - Core Orchestrator

β”‚ + mcp-gateway β”‚ Epic 2.5 - Security Layer

β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β–Ό

Claude Code MCP

Quick Start

# Extract complete pipeline

unzip forge-complete-pipeline.zip

# Test any package

cd react-generator && ./tests/quick-test.sh

Archive Contents

forge-complete-pipeline.zip - All 9 packages (255KB)

react-generator.zip - Epic 06 only

evidence-packs.zip - Epic 08 only

mendix-integration.zip - Epic 07 only

mcp-gateway-CLEAN.zip - Epic 2.5 (Security Gateway)

forge-c-CLEAN.zip - Epic 03 (Core MCP Server)

Claude Code Integration

The MCP server in forge-c exposes these tools:

forge_generate - Run convergence session

forge_validate - Validate against contract

forge_get_metrics - Get session metrics

forge_parse_figma - Parse Figma design

forge_generate_react - Generate React components

forge_generate_mendix - Generate Mendix pages

forge_create_evidence - Create audit evidence pack

Built for DCMA/DFARS/CMMC/SOC2 compliance.

---

Quality Assurance Guidelines

Verification Checklist (Before Marking Complete)

  1. Verify coverage BRANCH %, not just line % - Line coverage can be misleading; branch coverage shows if all code paths execute
  2. Test ALL config combinations, not just defaults - Real-world usage involves different configurations
  3. Run ALL test suites - Not just npm test, also tests/unit/ and package-specific tests
  4. Check for skipped tests - They indicate unresolved issues that need attention
  5. Inspect actual uncovered lines - Understand what functionality is not being tested
  6. Smaller, focused instructions - Avoid token limits by breaking work into phases

Key Lessons Learned

| Lesson | Impact |

|--------|--------|

| Test counts β‰  Code quality | High test count masked untested code paths |

| Branch coverage matters | 66% branch = 1/3 of logic NEVER runs |

| Default config bias | Only testing defaults misses real-world scenarios |

| Security needs extra scrutiny | 1-8% coverage on security = vulnerability |

| "Passing" can be misleading | Tests can pass in one suite while failing in another |

| Verify before trusting reports | Reports need validation against actual code |

Coverage Targets

| Metric | Target | Critical Components |

|--------|--------|---------------------|

| Line Coverage | β‰₯90% | All packages |

| Branch Coverage | β‰₯85% | All packages |

| Security Components | β‰₯95% | oauth, sandbox, tenant, sanitization |

| Test Pass Rate | 100% | Zero failures, zero skipped |

Test Commands

```bash

# Main platform tests

npm test

# Unit tests (separate suite)

npx jest tests/unit/

# Express generator

cd packages/express-generator && npm test -- --coverage

# Full coverage report

npm test -- --coverage

```