React / Next.js workflow surfaces
Interfaces where product judgment, state, routing, copy, and handoff details matter as much as component styling.
Neutral scoped-build proof
Product systems
For teams that need product surfaces, backend/API edges, data handoff, and implementation notes to move as one small system rather than a disconnected UI task.
Best when
The job is a bounded product system: a workflow, internal tool, productized integration, or design-system-backed suite with a clear delivery surface.
Delivery shape
A first slice should prove the workflow, clarify production risk, and leave the next maintainer with enough context to keep moving.
Fit
Good scoped-build fit
API-backed product features
Small systems that need frontend, backend, data shape, and integration boundaries to land together.
Internal tools and suites
Operator-facing tools, dashboards, or multi-surface product suites where the useful proof is workflow coherence.
Boundaries
Not a fit without more clarity
Pixel-only redesigns
A pure styling pass without product state, source constraints, or a maintained handoff is better handled as design support.
Unbounded platform rewrite
If the first milestone cannot fit in a scoped slice, the work needs planning, discovery, or a larger team model first.
Private proof as public proof
Internal demos, screenshots, and architecture diagrams stay TODO until they are approved for public use.
Proof
Proof map
available
project
Open Loop UI
React design-improvement package
Product-native improvement workflow with DOM selection, routing preview, adapter boundary, live demo, package, and docs.
available
project
Turtle Rock Coffee
Coffee product suite
Scoped product suite proof: home, library, brew, and taste surfaces tied through a shared product/design-system spine.
verified
professional
Complete.so
Founding Engineer
Founding engineer execution across backend rebuild, GraphQL, Python data pipeline, and HRIS/ATS integrations.
verified
professional
Tab For A Cause
Lead Full Stack Engineer
Product-surface ownership across a Next.js rewrite, shared component library, CI/CD, and growth-system outcomes.
available
project
Harmony
Local-first operator system for AI-agent fleets
Internal control-plane proof for issue DAGs, project graph state, agent prompts, validation gates, and code-agent execution.
todo
project
Harmony
Local-first operator system for AI-agent fleets
Operator-facing Electron/React surface over orchestration queues, runs, project graph state, and HTTP/SSE.
Milestones
First milestone examples
Route/workflow audit
Map the current workflow, data edge, ownership path, and the smallest product slice worth shipping first.
Integrated slice
Build one route, tool panel, integration flow, or API-backed UI with source refs and acceptance checks.
Handoff record
Document the shipped behavior, known risks, open TODO assets, and options for the next milestone.
Risks
Clarify before accepting work
Auth and data edge
What access, permissions, fake data, or anonymized examples are safe enough to use for the first slice?
Prototype versus production
Which constraints must be real now, and which are intentionally mocked until the next milestone?
Review path
Who reviews the workflow, screenshots, source claims, and public artifacts before anything becomes proof?
Maintenance owner
Who will own deployment, docs, operations, or future changes after the scoped slice lands?
Deferred
Future lanes
Deferred
AI workflows
Needs a tighter public AI-workflow proof set across Symphony, Job Pipeline, or Open Loop before rendering.
Deferred
Internal tools
Needs approved Harmony/Design Loop screenshots or diagrams in addition to the current Symphony control-plane assets.
Deferred
Product suite
Needs deterministic TRC screenshots, live-capture boundaries, and richer page copy before rendering as a standalone scoped-build vertical.
Continue in the channel where this was shared.
Continue in the channel where this was shared. Bring the current workflow, source-system constraints, timeline, decision owner, and the smallest useful first milestone.