Audit: shayanspiel/shayanspiel.github.io
Who this developer is
Shayan Spiel (Tehran) — solo operator, ex-growth lead at scale (Digikala, Takhfifan, Varzesh3), pivoted 2024–25 to agentic AI (LangChain/LangGraph, Claude Code, opencode). Three active efforts:
1. SpielEngine (just open-sourced) — an “agentic wiki content engine”: a markdown state machine (AGENTS.md, 18 states), 18 slash commands, validation gates, two Python health scripts. Sold as a $2,900 productized service (3 slots/month, manual fulfillment).
2. GeoGent — browser strategy MMO with AI rivals, in test phase; waitlist page on this site, with a share URL pointing at
geogent.spiel.workers.dev (he already uses Cloudflare Workers).
3. The Jekyll blog itself (no-style-please remote theme) as the marketing front door.
Technical audit findings (his site)
• jektex plugin likely dead: there is no .github/workflows build pipeline, so the site builds on the classic GitHub Pages Jekyll pipeline, which only runs whitelisted plugins. jekyll-feed/jekyll-sitemap are whitelisted; jektex is not — LaTeX macros in _config.yml are probably silently ignored.
• paginate_path configured but no pagination plugin loaded — dead config.
• Waitlist form reliability: GeoGent-Waitlist/script.js submits through a hidden iframe and treats any iframe load event within 6s as success (cross-origin responses are opaque), so failed submissions can show “You’re in.” No honeypot/bot protection; validation is client-side only.
• Hygiene: .DS_Store committed; repo README.md is still the upstream theme’s README, not his own; LinkedIn handle inconsistency (shayayantawabi in about.md vs shayantawabi in _config.yml — one is a typo).
• Otherwise solid: content-first, fast theme, sensible SEO config, future: true is intentional (SpielEngine publishes future-dated posts).
Would he benefit from Seraphina-AGI?
As a product, no. Seraphina-AGI is a Windows-centric desktop AGI suite (PySide6 tray GUI, WildRig mining, RVN wallet, Azure KV/DPAPI secrets). He’s a macOS-based content/agent-workflow operator — the core system doesn’t match his needs, and the repo is private anyway, so he couldn’t consume it directly.
Specific subsystems/patterns, yes:
• payments/cloudflare-worker (Stripe → license issuance → Resend email → KV): the strongest match. He sells a $2,900 offer with manual fulfillment and runs a waitlist on a fragile iframe form — and he already deploys to Cloudflare Workers. Your worker’s pattern (webhook handling, KV-backed records, Resend transactional email) maps directly onto both Spiel Engine checkout/licensing and a reliable GeoGent waitlist endpoint. Since the repo is private, the benefit would come from sharing the pattern/architecture, or extracting a sanitized template.
• Security/CI hardening patterns: SpielEngine just went public with Python scripts and zero CI. Your pinned-tool workflows (Bandit SARIF, GitLeaks OSS CLI, ESLint security plugins) and security_scanner.py approach are directly reusable patterns for a newly open-sourced repo inviting contributions.
Your other repositories — fit assessment
• SynerGro-AI/seraphina-grok-planner (public, TypeScript): best public-repo fit. Anti-hallucination verifier planner repo grep tools align exactly with his “validation gates / loops beat prompts” thesis. Caveat: it targets Copilot LM tools while he works in opencode/Claude Code, so it’s conceptually adjacent rather than drop-in.
• jmwilson2019/Civ1Better (public): strong thematic overlap with GeoGent (hex/strategy mechanics, cities, economies, AI opponents in JS/Canvas Python). More a collaboration/idea-exchange opportunity than a dependency.
• SynerGro-AI/grok-4agent-auditor (archived): multi-agent auditing matches his gate philosophy, but it’s archived — only worth pointing to as prior art.
• seraphina-agi-releases, Seraphina.AGIv1.0.8, Codepro, codefinity repos: not relevant to his profile.
#you in?