Skill / 01
Masterplan
An execution-ready planning system that turns a rough idea into structured product context, implementation guidance, and testable acceptance criteria.
Technical SEO · AI automation · Product direction
Working notes on search, systems and products built with agents.
I turn messy growth and product problems into clear specifications, dependable workflows, and shipped software. Agents produce much of the code. I own the framing, direction, validation, and final call.
01
Primary build · Open source
A work orchestrator for agent-directed software.
PRX–001 / Active
Proxima
A self-hosted workspace that turns conversations into isolated, reviewable work across chat, tasks, Git worktrees, diff review, recipes, schedules, and multi-agent execution.
CorePython · FastAPI · SQLite
ClientReact · TypeScript · PWA
RuleBehavior before completion claims
02
Public agent skills
Small operating systems for repeatable work.
These are not prompt collections. Each skill defines a workflow, artifacts, boundaries, and review points so an agent can do useful work without losing the original intent.
Skill / 02
Overseer
A safety-oriented workflow for auditing agent session changes, documentation drift, project memory, and recoverability.
Skill / 03
Lakon
A structured set of persona playbooks and templates for giving agents a repeatable voice, working style, and task-specific operating method.
03
About the operator
Search experience, product judgment, agent leverage.
Eight years around organic growth taught me to care about systems, not isolated tactics.
I do not present myself as a traditional full-stack engineer. I direct agent-built products through PRDs, architecture choices, acceptance criteria, E2E validation, code review, and iteration.
I started in SEO, moved through content systems and technical web delivery, then began using AI to make the work more executable. Today I translate a business or growth problem into a specification, direct coding agents through the build, and stay accountable for whether the result behaves properly.
That means the work can cross research, information architecture, automation, frontend, backend, and deployment. The connecting skill is not typing every line. It is keeping the problem, system, and evidence aligned from the first note to the shipped product.
Read the full profile04
Selected independent work
A compact ledger of systems shipped and repaired.
Wingoh
A combined website and organic-growth engagement covering design improvement, development, content structure, and ranking work for industry and product queries.
ShippedInsideVVIP
A recovery engagement for traffic lost during an HTML-to-WordPress migration, followed by a high-performance Astro rebuild and systematic on-page cleanup.
Recovered and rebuiltLINC.id
A website rebuild focused on reusable page structure, multilingual delivery, performance, and maintainable technical foundations.
ShippedBikinOnline
A commerce platform designed to run multiple storefronts while keeping tenant data, behavior, and release quality verifiable.
Pre-launch05
Field notes
Observations from the workbench.
Short notes on what I am learning while working with search systems, migrations, and coding agents.
Why I Write the PRD Before Directing Coding Agents
Prompting gets a prototype. A useful product needs decisions, boundaries, and a way to tell when the work is actually done.
Read entryMigration Recovery Starts With URL Intent
A recovery plan is less about moving pages and more about preserving the job each old URL was doing.
Read entryWhat Ranking Data Can and Cannot Prove
Search exports are useful evidence, but only when the duration, filters, and limits stay attached to the claim.
Read entryOpen channel
Leave a note on the desk.
If you are working through a search, automation, or product problem, send the context. I read every useful brief.