Thechrisgrey MCP

thechrisgrey.com

Personal website for Christian Perez (@thechrisgrey) | Founder & CEO of Altivum Inc. | Former Green Beret (18D Special Forces Medical Sergeant) | Bronze Star Recipient | Host of The Vector Podcast | Author of "Beyond the Assessment"

[https://thechrisgrey.com](https://thechrisgrey.com)

---

Table of Contents

• Technology Stack
• Features
• Architecture
• AWS Infrastructure
• Getting Started
• Testing
• Environment Variables
• Deployment
• Project Structure
• Key Integrations
• Design System
• License

---

Technology Stack

---

Features

Pages

• Home : Scroll-based animations with sticky profile sections
• About : Personal biography and military background
• Altivum Inc : Company showcase and services
• The Vector Podcast : YouTube embeds, Spotify player, collapsible episode list
• Beyond the Assessment : Book information and purchase links
• Blog : Sanity CMS-powered with categories, tags, series, and reading progress
• AI Chat : Full-viewport conversational AI with RAG-enhanced responses
• Claude : AWS certifications and Claude expertise showcase
• AWS : AWS partnership and community builder profile
• Admin : Cognito-authenticated KB management and site health dashboard
• Links : Linktree-style quick links
• Contact : Contact form, speaking topics, downloadable press kit

Technical Highlights

• SEO : JSON-LD structured data, Open Graph, dynamic sitemap, RSS feed
• AI Chat with RAG : Bedrock Knowledge Base retrieval with streaming responses
• Podcast Auto-Sync : YouTube Data API fetches episodes at build time
• Chat Widget : Floating chat widget available across all pages
• Metrics Dashboard : CloudWatch and DynamoDB-backed operational metrics
• Error Boundaries : Page-level error handling with custom fallback UIs
• Accessibility : Focus trapping, keyboard navigation, ARIA labels, skip links
• Performance : Image optimization (Sharp/SVGO), lazy loading, code splitting, manual chunking

---

Architecture

┌─────────────────────────────────────────────────────────────────┐

│ FRONTEND (React) │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ Home │ │ Podcast │ │ Blog │ │ Chat │ ... │ │ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │ └─────────────────────────────────────────────────────────────────┘ │ │ │ │ ▼ ▼ ▼ ▼ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────────┐ │ Amplify │ │ YouTube │ │ Sanity │ │ Bedrock │ │ Hosting │ │ Data API │ │ CMS │ │ + RAG (KB) │ └───────────┘ └───────────┘ └───────────┘ └───────────────┘ (build-time) (runtime) (Lambda stream)

AI Chat Request Flow

User Message

│ ▼ Lambda Function URL (streaming) │ ├──> Bedrock Knowledge Base (retrieve context) │ │ │ ▼ │ S3 Vectors (autobiography chunks) │ ├──> Bedrock Guardrails (content filtering) │ └──> Bedrock ConverseStream API (Claude Haiku 4.5) │ ▼ Streaming Response -> Client

---

AWS Infrastructure

---

Getting Started

Prerequisites

• Node.js 20.x (see .nvmrc)
• npm
• AWS CLI (for deployment)

Installation

git clone https://github.com/thechrisgrey/thechrisgrey.git

cd thechrisgrey npm install

Development

npm run dev             # Start dev server at http://localhost:5173

npm run build # Full production build npm run preview # Preview production build npm run lint # Run ESLint

Build Pipeline

The production build runs these steps in sequence:

validate-env -> podcast-episodes -> lint -> tsc -> vite build -> sitemap -> rss

---

Testing

The test suite includes unit tests for components, hooks, and utilities; integration tests for page-level behavior; and end-to-end tests covering navigation, chat, blog, and contact flows.

Live-API contract tests (opt-in)

Critical external boundaries — Cognito admin auth, the live Sanity client, Bedrock KB retrieval, and the Bedrock guardrail — are also covered by opt-in contract tests that exercise the real services (green mocks alone can drift from reality). They skip cleanly during npm run test:lambda and CI, and only run when their flag + AWS/Sanity credentials are present:

COGNITO_CONTRACT_TESTS=1 COGNITO_CLIENT_ID=… COGNITO_TEST_EMAIL=… COGNITO_TEST_PASSWORD=… \

node --test lambda/shared/tests/cognito-contract.test.mjs SANITY_CONTRACT_TESTS=1 node --test lambda/chat-stream/tests/sanity-contract.test.mjs KB_RETRIEVE_CONTRACT_TESTS=1 node --test lambda/chat-stream/tests/kb-retrieve-contract.test.mjs BEDROCK_CONTRACT_TESTS=1 node --test lambda/blueprint/tests/guardrail-contract.test.mjs

See .env.example for the full list of flags and required permissions. Run these before a release (or on a scheduled job) to catch response-shape/schema drift that unit mocks can't.

---

Environment Variables

Set in AWS Amplify console or in a local .env file:

VITE_ prefixed variables are bundled into the frontend. YOUTUBE_API_KEY is only used during the build step.

---

Deployment

Automatic (Recommended)

Push to main triggers automatic Amplify deployment:

git push origin main

Manual Rebuild

aws amplify start-job \

--app-id d3btl94rm91y13 \ --branch-name main \ --job-type RELEASE \ --region us-east-2 \ --profile personal-dev # Delta Centric 512880383078, the site's home

Lambda Deployment

Each Lambda function is deployed independently via a single verified script. The script installs from the lockfile, dereferences the lambda-shared symlink into the bundle, and verifies the entire module graph resolves before upload — so a deploy can no longer ship a Lambda that crashes on cold start.

# Verify the bundle builds and resolves, without uploading:

npm run deploy:lambda -- chat-stream --dry-run

Deploy for real (runs as profile personal-dev and refuses unless the caller

accoun