image-gen-extension
Browser extension for image generation workflows inside the editor context. TypeScript MV3 extension with focused UX for prompts and previews.
Details
Stuzhuk Lab — Chemistry of Code
Chemistry of Code
Browser extensions (Chrome MV3)
TypeScript extensions with focused UX: permissions, service workers, messaging, and store-ready packaging.
Discuss this scopeContact form
Tell me the goal, stack constraints, and timeline — I reply on Telegram.
Modern Chrome extensions are small products: honest permissions, restart-prone service workers, and simple messaging between UI, content scripts, and background.
If you need a companion surface next to an existing web product, an extension meets users where they already work.
Representative work
Recent deliveries include image-gen-extension—systems where browser extensions (chrome mv3) skills (TypeScript, Chrome MV3, WebExtension API, content scripts, messaging, UX, packaging) were applied end to end.
Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.
Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.
After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
Acceptance criteria
Done when
- MV3 extension loads and completes the primary user flow
- Permissions match the minimum agreed set
- Messaging between content script and worker is stable on reload
Deliverables
- Packed build + install notes
- Store listing draft if in scope
Out of scope
- Chrome Web Store review outcomes guarantees
The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.
Selected portfolio work
All projectsHow I work
Request
You describe the goal, constraints, timeline, budget, and infrastructure.
Clarify
I ask questions, review existing code or a brief when needed, and lock scope.
Plan
I propose stages, priorities, and a timeline range; we agree on reporting.
Build
Iterations with intermediate results: commits, demos, and feedback.
Handoff & support
Deploy and docs as needed; we agree on maintenance or targeted follow-ups.
FAQ
Tap a question to expand the answer.
Do you build Manifest V3 extensions?
Yes—TypeScript-first MV3 with service workers, content scripts, and messaging kept deliberately simple.
How do you approach permissions?
Request only what the feature needs, explain why in the store listing, and avoid broad host access by default.
Can you publish to the Chrome Web Store?
I prepare packages, privacy notes, and review-friendly builds; the developer account stays yours.
What about Firefox or Edge?
MV3 Chrome is the default; Firefox/Edge ports are feasible when APIs align—scoped per project.
Can an extension connect to our web app?
Yes—typical pattern is extension UI + your existing REST API and auth, without duplicating backend logic.
Discuss this scopeContact form
Tell me the goal, stack constraints, and timeline — I reply on Telegram.