Workflows with clear boundaries
Turn a research, document, or content task into defined steps, structured outputs, and human review points. Use a simple automation when an agent is not needed.
AI agent engineer / full-stack developer
Hi, I'm Ruo.I build and fix software.
I help small teams build AI workflows, connect tools through MCP and APIs, and get existing software working. We start with one useful task, clear boundaries, and a way to check the result.
Code, checks, and handover notes are included.
AI agent engineering
I combine full-stack development with AI workflows that read information, use tools, and produce work someone can check. The job includes the software around the model, not just the prompt.
MCP and tool integration
Connect AI clients to document publishing and existing APIs. Define tool inputs, access permissions, and explicit approval before publishing or changing external data.
Evaluation and failure handling
Check outputs against source material and sample tasks. Add bounded retries, usage limits, failure reporting, and repeatable tests before expanding the scope.
A useful agent needs a clear task, limited access, and a way to tell when it is wrong. I do not promise unrestricted autonomy.
See current AI engineering workSelected work
A few projects from my practice. Client details have been anonymized.
Incident recovery
Legacy WordPress Recovery
Reproduced the failure in staging, isolated incompatible paths, and built a controlled recovery and release sequence.
WordPressPHPNginxMySQL
Read the case study 
Payments and back office
China Payment Gateway Integration
Mapped checkout and callback verification, implemented traceable failure paths, and prepared reconciliation views for operations.
DrupalPayment APIsPHPRedis
Read the case study 
CRM automation
SuiteCRM + WordPress Automation
Mapped source fields, added duplicate handling and assignment rules, and created a QA handover for production.
SuiteCRMWordPressREST APIsEmail automation
Read the case study What to expect
Scope before code
Deliverables, acceptance criteria, and exclusions are agreed first.
Verifiable delivery
Work is delivered through focused code changes, tests, build results, and handover notes.
Minimum necessary change
The goal is to remove the blocker, not turn every task into a rewrite.
How I can help
Small, focused projects. Scope and price agreed before work begins.
Bug Fix Sprint
Diagnosis, implementation, tests, and a focused PR for one reproducible issue.
Discuss this projectTypical delivery
- Root-cause note and bounded implementation
- Relevant tests or reproducible verification
- Focused PR and handover notes
Not included: Unlimited investigation or architecture rewrite
Test & Release Sprint
Create an automated baseline for a critical journey or remove a build, CI, or release blocker.
Discuss this projectTypical delivery
- One critical automated path
- Repeatable build or release command
- Failure notes and remaining risks
Not included: Full test-suite coverage
AI Agent & Integration Sprint
Build one bounded AI workflow or MCP tool integration for an existing product, with defined inputs, outputs, and approval points.
Discuss this projectTypical delivery
- One workflow or tool integration with structured outputs
- Sample-task evaluation, error handling, and approval checks
- Bounded retries, usage limits, and handover notes
Not included: Model fees, model training, unrestricted autonomy, and full multi-agent platforms
Multilingual SEO & i18n
Implement localized routes, metadata, canonicals, sitemaps, structured data, and a maintainable content flow.
Discuss this projectTypical delivery
- Localized route and metadata baseline
- Canonical, hreflang, sitemap, and schema
- Maintainable translation handover
Not included: Large-scale human translation or content operations
From first message to handover
Share the issue
Expected behavior, actual behavior, reproduction steps, and any repo or demo you are authorized to share.
Confirm the scope
Receive written deliverables, acceptance criteria, exclusions, and a quote.
Implement and verify
Changes are made in a focused branch or PR and checked against the agreed criteria.
Deliver and hand over
Receive code, verification results, merge or deployment notes, and known follow-ups.
Ways to work together
Paid diagnosis
For problems whose root cause is unclear and cannot yet be quoted responsibly.
Fixed-scope sprint
For one bounded outcome with a clear acceptance path.
Monthly maintenance
For recurring fixes, release support, and gradual technical-debt cleanup.
No unlimited revisions, 24/7 on-call promise, or guaranteed outcome before the system is inspected.
Common questions
Can you fix an issue without learning the entire codebase first?
A paid diagnosis can come first. Fixed-price implementation begins only when the reproduction path, relevant modules, and acceptance criteria are clear enough.
Do you accept urgent work?
You can state the urgency, but acceptance depends on current availability, access conditions, and risk. No deadline is promised before the scope is reviewed.
Will you sign an NDA?
An NDA can be reviewed when the project requires it. Code, business data, and screenshots are not published without authorization, with or without an NDA.
How does payment work?
The payment method, milestones, acceptance window, and any refund conditions are confirmed in writing before work begins. Small bounded tasks may require prepayment or platform escrow.
Is support included after delivery?
Each scope includes a written acceptance window. New features and issues outside the agreed scope are quoted separately.
Do you use AI coding tools?
Tools may assist research, testing, and implementation, but delivery is judged by working code, test results, and human review. Client secrets are not submitted to unauthorized third-party services.
Tell me about your project.
Share only information and links you are authorized to disclose. I will first confirm whether the work fits a bounded sprint.
Prefer email?ruo@deng.in