Daniel Euchar daneuchar
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Build a React chat input component styled with shadcn/ui and Tailwind. White background, rounded-lg border, subtle shadow. Inside the box: | |
| A <textarea> with placeholder "How can I help you today?" that auto-grows as the user types (supports multiple lines). No visible border, transparent background. | |
| Below the textarea, a bottom toolbar row with: a "+" icon button on the left, and on the right side a model selector dropdown ("Opus 4.6 Extended" with a chevron-down) and a voice/audio waveform icon button. | |
| Use shadcn Button (variant ghost/icon), DropdownMenu, and Textarea. Keep everything inside a single rounded container with bg-white border border-gray-200 rounded-xl p-3 flex flex-col gap-2. The toolbar uses flex justify-between items-center. Make it responsive and max-width around 700px centered. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| flowchart LR | |
| subgraph P0["Phase 0 — Knowledge Bootstrap"] | |
| direction TB | |
| A["Scan Repo & Generate<br/>Module Docs"] --> B[" Define Rules &<br/>Conventions"] --> C[" Configure Copilot<br/> to Navigate Docs"] | |
| end | |
| subgraph P1["Phase 1 — Planning"] | |
| direction TB | |
| D["AI Generate PRD<br/>Ref Docs & Constraints"] --> E["Engineer Reviews<br/>generated PRD"] --> F["Co work with Copilot <br/> Refine PRD"] | |
| end |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # AI Assisted Development Workflow — 5-Minute Demo Script | |
| **Scope:** Phase 0 (AI Knowledge Bootstrap) through Phase 1 (Planning + PRD) | |
| **Duration:** 5 minutes | |
| **Audience:** UBS engineering leadership / team leads | |
| --- | |
| ## Slide-by-Slide Script |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Feature Development Workflow</title> | |
| <link rel="preconnect" href="https://fonts.googleapis.com"> | |
| <link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=Space+Grotesk:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet"> | |
| <style> | |
| *, *::before, *::after { margin: 0; padding: 0; box-sizing: border-box; } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Idea 1: Producer-Side Agent for Data Product Discovery & Structuring | |
| The core insight here is that producers often have raw data but struggle with the "productization" step. An AI agent dropped into a producer's environment could do several things. First, it would profile and catalog the data automatically — scanning tables, files, or streams to understand schema, data types, cardinality, null rates, and statistical distributions. Second, it could infer semantic meaning by looking at column names, sample values, and relationships to suggest business-friendly names, descriptions, and domain classification (e.g., "this looks like customer PII" or "this appears to be a clickstream event"). Third, it would recommend a data product structure — suggesting how to split or combine tables into coherent, self-contained data products aligned with domain boundaries. It could propose SLAs based on observed update frequency, suggest primary keys, recommend partitioning strategies, and flag quality issues before registratio |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Multi-Service Flow Orchestration Pattern | |
| **Date:** 2026-03-16 | |
| **Status:** Approved | |
| ## Overview | |
| Design for a **reusable multi-service API orchestration pattern** (the "Flow" layer) within the existing BDD test framework. A flow chains multiple services where each stage's output feeds into the next. | |
| The Data Product Registration flow below is the **first implementation** of this pattern, serving as the reference for all future multi-service flows. |
daneuchar
/ gist:860b9dadff89d9ee417dd032ac524f18
Created
March 11, 2026 06:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Clean Code Rules | |
| # Stack: TypeScript · Node.js · Apollo Federation · GraphQL · Kafka · EventHub | |
| # These rules are non-negotiable across every package and subgraph in the monorepo. | |
| --- | |
| ## 1. SIZE LIMITS — hard ceilings, not guidelines | |
| | Unit | Max Lines | Rationale | | |
| |-----------------------|-----------|--------------------------------------------------------| |
daneuchar
/ gist:4144176005f1c60fae623471060bb4f5
Last active
March 11, 2026 11:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Data Mesh Platform — Directory Structure | |
| # Architecture : Hexagonal (Ports & Adapters) + CQRS (separate read/write paths) | |
| # Pattern : Read path → Redis projections (low latency, no DB hits) | |
| # Write path → Command → Use Case → Domain → Event → EventHub | |
| # Stack : TypeScript · Apollo Federation · Azure EventHub · Kafka · Redis · PostgreSQL | |
| . | |
| ├── apps/ | |
| │ │ | |
| │ ├── gateway/ # Apollo Router — entry point for all GraphQL traffic |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| --- | |
| name: graphql-architect | |
| description: "Use this agent when designing or evolving GraphQL schemas across microservices, implementing federation architectures, or optimizing query performance in distributed graphs." | |
| tools: Read, Write, Edit, Bash, Glob, Grep | |
| model: opus | |
| --- | |
| You are a senior GraphQL architect specializing in schema design and distributed graph | |
| architectures. You have deep expertise in Apollo Federation 2.5+, GraphQL subscriptions, | |
| query performance, and clean, maintainable server-side code. Your primary focus is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Document Azure Function API Endpoints as Versioned OpenAPI Specs | |
| ## Purpose | |
| Scan the entire TypeScript Azure Functions codebase, discover all HTTP-triggered | |
| functions, extract their API metadata (route, method, request/response schemas, | |
| auth level, parameters), group them by API version, and generate one OpenAPI 3.0 | |
| YAML file per version. | |
| ## Output Convention |
NewerOlder