I build security products and practical AI engineering tools, with clear docs and verifiable releases.
EN
TR
DE
ES
PT-BR
FRStart with the project that matches what you need:
| If you need... | Start with |
|---|---|
| Vulnerability intelligence, CVE workflows, and public product docs | MyVuln product website and MyVuln public hub |
| Self-hosted password and secrets management, releases, and operator docs | VaultPilot release hub |
| Cross-platform Codex CLI and Claude Code setup with agents, skills, and MCP | AgentChef (formerly Codex Chef) |
| Reusable approval-gated prompts, workflows, and verification checklists | Prompt Architect |
| Documentation-first starter kits for AI-coded projects | AI Project Starter |
| Reusable AI agent and Codex skill creation | AI Skill Create |
| Codex CLI operating guidance for prompts, skills, MCP, hooks, and Windows | Codex CLI Operator Handbook |
| SEO for your own sites: Search Console, technical audits, and local rank history | SEOTracker, derived from open-seo |
| Turkish cybersecurity writing and public research surface | SiberDergi |
- Security products and public hubs that make useful documentation, releases, and trust signals easy to find without exposing private source, customer data, or tenant context.
- Windows-first release surfaces for self-hosted tools, with the manifests, support evidence, operator notes, and verification gates needed to keep shipping understandable.
- Codex and AI-engineering tools that turn a vague idea into a clear plan, a reusable skill, a well-routed workflow, and a handoff another person can actually pick up.
Vulnerability intelligence and CVE workflows. 
|
Self-hosted password and secrets management. 
|
Codex CLI and Claude Code setup, agents, skills, and MCP. 
|
Reusable prompts, approval steps, and verification. 
|
These tools help me give coding agents useful project context, reuse workflows, and check the results.
Project context and documentation for AI-assisted development. 
|
Create, validate, and package reusable agent skills. 
|
Operating guidance for skills, MCP, hooks, and configuration. 
|
|
| Step | How I work |
|---|---|
| Research | I read the public docs, threat boundaries, release notes, and repo instructions before changing behavior. |
| Plan | I keep the scope clear, define the checks up front, and leave room for a safe rollback. |
| Execute | I make the focused change without weakening auth, validation, public-safety, or support boundaries. |
| Verify | I start with local checks, then widen the evidence when the change can affect more of the system. |
| Release | I keep the docs clean and make the public artifact easy for the next person to trust and use. |
| Area | Tools and platforms |
|---|---|
| Product UI and docs | TypeScript, React, Next.js, Tailwind CSS, Markdown, SVG assets |
| Security products | CVE workflows, URL intelligence, release manifests, support evidence, public-safe docs |
| Data and backend | Node.js, Supabase, PostgreSQL, SQLite, Prisma |
| Windows release work | PowerShell, Windows Server, signed release flow, GitHub Actions |
| AI engineering | OpenAI Codex, Claude Code, skills, agents, MCP connectors, prompt architecture, verification checklists |
A snapshot of my contributions, refreshed manually through the snake workflow.
The linked product hubs contain public documentation and releases. Private source code, customer data, credentials, and operational records stay private.
Build. Verify. Release.
