Independent project service · 2026

Make one project
make sense.

For people who already have a goal, material, or a work in progress: finish a small frontend, work through a specific blocker, or check the evidence behind a project and CV claim.

Describe one project
01 / Build02 / Coach03 / Review

01—03 / Services

Three things, done clearly.

Scope, deliverables, acceptance, and exclusions are written down before work starts. Pricing follows a review of the material and the full time required.

01Small frontend build or finishBuild

You have copy, assets, references, or a partial build and need one page or one bounded improvement finished.

You provide
Final or near-final copy, licensed assets, references, existing code, and one feedback owner
Delivery
Responsive implementation, browser checks, source, run notes, and one in-scope revision
Excludes
Payments, accounts, complex databases, admin systems, and unlimited maintenance
Accepted when
Agreed pages and interactions run, desktop and mobile checks pass, and the work is transferable
Brief this service ↘
02Project improvement and walkthroughCoach

A project is underway but blocked on one specific outcome; you need review, debugging, and understanding.

You provide
A project you may share, its environment and errors, your current level, and the allowed support boundary
Delivery
Focused sessions, code review, test feedback, run notes, and one acceptance review
Excludes
Impersonation, assessed work, guaranteed merges, permanent maintenance, or all-stack emergency cover
Accepted when
You can run and explain the agreed change, with issues and next steps recorded
Brief this service ↘
03Project and CV evidence reviewReview

Review one project and its related CV lines for actual contribution, improvement priority, and truthful wording.

You provide
One project, its related CV lines, the target role, and an honest account of your contribution
Delivery
Code and contribution check, prioritised recommendations, one call, and evidence-based rewriting
Excludes
Invented experience, referrals, interview or offer guarantees, and repackaging someone else's work
Accepted when
Every claim maps to evidence and each recommendation is ranked by impact and effort
Brief this service ↘

Selected evidence / Not client work

See the process,
not the pitch.

These are self-directed teaching and capability samples. They are not client projects and do not imply prior revenue.

Sample 01

Build Weekend

From a simulated brief and acceptance criteria to a vanilla HTML, CSS, and JavaScript build. It includes goal selection, a dynamic summary, copy feedback, and desktop plus 390px browser checks.

  • RoleDesign, frontend, testing
  • BoundaryNo login, payment, or database
  • EvidenceSource, notes, screenshots
intake-summary.test.jsUTF-8
// Old code called .trim() on an optional field
- const stack = input.stack.trim();
+ const clean = (value) =>
+   String(value ?? "").trim();

TEST RESULT
✓ 4 passed  0 failed · 18ms

Sample 02

From failure to an explainable fix

A practice project could not produce a brief when an optional field was missing. The record keeps the reproduce, isolate, repair, test, and walkthrough path—not just a corrected snippet.

  • Before1 failed / TypeError
  • After4 tests passing
  • MethodReproduce, isolate, fix, explain

Working method

Align first. Then build.

  1. 01Fit

    Goal and material

  2. 02Scope

    Delivery and quote

  3. 03Payment

    Milestone and route

  4. 04Work

    Build and review

  5. 05Accept

    Test and handoff

AI may assist with decomposition, drafts, and checks. Wade confirms requirements, reviews code, runs tests, explains key implementation choices, and remains responsible for the agreed delivery.

Engagement and payment boundaries

Direct work uses written milestones; platform work follows platform escrow and withdrawal rules. Both parties verify the payment route and invoice needs before quoting. New outcomes require a scope change. No guarantees are made for offers, open-source merges, income, rankings, or unverified timelines.

About / Responsibility

Wade Wu
吴念泽

I work with frontend development, AI-assisted development, GitHub, and automation. At this stage I accept only small projects I can support with existing evidence, a clear scope, and real testing.

I own
Requirements, implementation review, test execution, explanation of key choices, and the agreed handoff.
I do not relabel
AI output, unmerged changes, practice work, or someone else's work as client experience.
I do not claim
To be a senior recruiter, a prominent open-source maintainer, a proven business coach, or able to guarantee offers and merges.

Before we start

A few things first.

Can we start with a rough idea?

We can first check fit, but a quote needs one primary outcome, the material you can provide, and a result we can test. Larger ideas are split into stages or paused.

Can you connect an existing form, booking tool, or deployment?

A link or bounded integration can be assessed, but an external handoff will not be described as a custom system. Access, data destination, cost, and maintenance ownership are agreed separately.

Can you help with coursework or open-source contributions?

Only when the applicable rules allow guidance on understanding, reproducing, changing, and testing. You must participate and describe your contribution honestly. No impersonation, assessed-work substitution, PR sales, or merge guarantees.

How does payment work, and can you issue an invoice?

The route depends on client location, platform rules, and Wade's account eligibility, which still requires personal verification. A commercial invoice is not a Chinese tax invoice; raise tax-invoice or entity requirements before quoting.

Start with one project

Begin with a clear description.

This worksheet creates a summary only on this page. It is not uploaded, stored, or sent automatically. Do not enter passwords, bank details, identity documents, or material you cannot share.

wunianze666@gmail.com ↗
Open email

Nothing has been generated or sent.