Work
Work index for systems I can explain, verify, and extend.
A scannable index of Agentic Engineer and full-stack web developer work: local-first automation, workflow infrastructure, media systems, and client-side tooling. Each entry favors constraints, stack, proof, and verification over broad title labels.
Categories
AI Workflow ToolingMedia AutomationLocal Desktop AutomationMinecraft Client SystemsDeveloper Workflow AutomationCompliance Workflow Tooling
Stack Signals
TypeScriptNode.jsCLIClickUp visibilityGitHub workflowNext.jsPrismaPostgresNode workerFFmpegDockerElectron
Local-first control plane for turning project intent into durable plans, tickets, sprint execution, review evidence, and approval-gated release work.
Proof Points
- Local artifacts preserve intake, tickets, sprint state, evidence, review packets, and resumable handoffs.
- Next-action and development-loop workflows keep agent work grounded in explicit state and verification.
- ClickUp is treated as a visibility mirror rather than the source of truth.
Verification
- CLI workflow runs produce durable status, audit, and handoff artifacts.
- Tasks move through sprint states with recorded implementation and verification evidence.
- Push and deployment paths are separated, reviewed, and auditable.
TypeScriptNode.jsCLIClickUp visibilityGitHub workflow
Pipeline for turning selected Minecraft Twitch VODs into reviewed YouTube Shorts with quality gates before publishing.
Proof Points
- VOD-centered review flow keeps quality checks before publication.
- Worker pipeline covers download, transcription, scoring, rendering, and upload preparation.
- Local and production Docker paths support repeatable operation.
Verification
- Pipeline features are verified from real storage and database state.
- Rendered clips remain review-gated before upload.
- Metadata is grounded in transcript and correction data.
Next.jsTypeScriptPrismaPostgresNode workerFFmpegDocker
Local desktop assistants for Google Photos backup and cleanup with explicit confirmation before destructive actions.
Proof Points
- Manual Google login avoids password storage and security bypass behavior.
- Local validation and dedupe reporting happen before cleanup.
- Destructive actions require explicit confirmation.
Verification
- Backup and cleanup states are designed around local evidence.
- Deletion remains gated behind user confirmation.
- Public description avoids private account and library details.
ElectronReactTypeScriptLocal storageGoogle Takeout workflow
Fabric and Meteor client-side systems for repetitive game workflows with version targeting, navigation, and safety behavior.
Proof Points
- Animal Hunter Addon targets Minecraft 26.1.2 with Baritone navigation and cleanup behavior.
- TeeGoals Utility handles repetitive inventory tasks with safety-oriented disconnect behavior.
- LibrarianTradeFinder work covers villager trade search, profession waits, filtering, and regression debugging.
Verification
- Version-specific Gradle builds and manual game acceptance checks are part of the workflow.
- Safety pauses and stop conditions are treated as core behavior.
- Public copy stays architectural and avoids private server procedures.
JavaFabricMeteor ClientBaritoneMinecraft client modding
Standalone Codex-first control plane for studying, reproducing, implementing, verifying, reviewing, and handing off SolarPlus Jira tickets.
Proof Points
- Ticket study, reproduction, implementation, verification, review, and handoff are separated into durable, resumable phases.
- Local and remote evidence stays tied to the ticket lifecycle instead of disappearing into chat history.
- External writes remain behind explicit approval and handoff boundaries.
Verification
- Workflow is described at a safe architecture level.
- Private Jira, source-control, documentation, and server references are withheld.
- Approval gates apply before external comments, status changes, pushes, deployments, or server updates.
Node.jsCLI workflowCodexJiraMCP BrowserRunbooks
Self-serve Philippine environmental-compliance calendar and evidence organizer, beginning with a free public PCO renewal readiness checker.
Proof Points
- The public checker uses dated official sources and clearly separates verified guidance from draft content.
- The first release is free and requires no login, while authentication, document storage, billing, and government integrations remain explicitly deferred.
- Release checks cover TypeScript, linting, local tests, production builds, browser flows, accessibility, and dependency auditing.
Verification
- A single local check runs typechecking, linting, tests, and the production build.
- Playwright release checks exercise representative browser and accessibility flows.
- Protected-preview, production, rollback, and DNS checks are documented as explicit release gates.
Next.jsTypeScriptCloudflare PagesPlaywrightNode.js