Skip to content
View jiakai03177-coder's full-sized avatar
  • Tokyo

Block or report jiakai03177-coder

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
jiakai03177-coder/README.md

Kai

FPGA Hardware Acceleration | Self-Attention & Transformer Optimizer

I build small, focused open-source tools that sit at the boundary between Transformer architecture and the hardware that runs it — cost models, tile planners, and developer tools that make AI workloads more legible to engineers.

📍 Tokyo · 🛠️ Python / JavaScript / FPGA mapping concepts


Current Focus

  • Self-attention and KV cache cost modeling
  • FPGA-oriented tile planning and resource estimation for Transformer inference
  • Developer tools that help AI coding agents understand repositories faster
  • Turning abstract model shapes into concrete engineering constraints (SRAM, BRAM, URAM, DSP)

Projects

Plan self-attention query/key tile sizes for FPGA accelerators. Estimates BRAM18K / URAM / DSP48 utilization against real device presets (VU9P, ZCU102, VCK190 …) so you can answer "does this attention tile fit my FPGA?" before writing HDL.

attention-tiles --preset llama3-8b --seq-len 4096 --sram-kib 512 --device vu9p

Why: most FPGA attention papers stop at "we tiled it" — this answers the missing question of which tile actually fits.

Estimate Transformer attention FLOPs, KV cache size, and decode memory pressure directly from model shape parameters. Useful for early-stage architecture sizing before you spin up a GPU.

attention-cost --preset llama3-8b --seq-len 8192

Why: turns "how big does this model get at long context?" from a spreadsheet exercise into one CLI call.

Generate compact AI-ready context packs for codebases so coding agents (Claude Code, Codex, Cursor) can understand a repo before editing it.

repo-context-packer --token-budget 8000

Why: AI coding agents waste tokens re-reading the same files. This solves it once, upstream.

Direction

I care about the path from algorithm shape to hardware-aware execution:

Transformer architecture
        ↓
attention / KV cache cost
        ↓
memory bandwidth pressure
        ↓
on-chip tile planning (SRAM, BRAM, URAM)
        ↓
DSP / compute mapping
        ↓
acceleration strategy

Each of my projects sits on one of those arrows. The goal is to make every step a concrete, measurable engineering decision instead of a vibe.

Tech

Python · JavaScript · Node.js · GitHub Actions · FPGA / Xilinx UltraScale+ resource modeling · Transformer inference analysis · CLI tool design


Open to collaboration on FPGA-based Transformer inference, attention kernel optimization, and AI developer tooling.

Pinned Loading

  1. repo-context-packer repo-context-packer Public

    Generate AI-ready context packs for coding agents.

    JavaScript 2

  2. attention-cost-lab attention-cost-lab Public

    Estimate Transformer attention FLOPs, KV cache size, and decode memory pressure.

    Python 1

  3. fpga-attention-tile-planner fpga-attention-tile-planner Public

    Plan self-attention tile sizes for FPGA and accelerator SRAM budgets.

    Python