The starting point
Turn an early product concept and structured founder answers into an organized, reviewable PRD package and implementation handoff instead of starting from a blank specification.
This is the public-facing AppArchitect case study and deliberately relies only on evidence from public repositories: fvckfac3/apparchitect-final and the empty fvckfac3/AppArchitect-Foundation placeholder. It must not incorporate private workspace or orchestration evidence. The public product direction is an interview-to-PRD suite for translating early concepts into organized, reviewable requirements and build handoffs. All listed service opportunities are proposals, not shipped functionality.
What’s implemented
- Auth-gated interview spanning product, audience, features, privacy, roles, technical needs, integrations, design, testing, and monetization
- Rule-based follow-ups, answer validation/quality scoring, and suggestions
- Conditional agent-team composition with roles and dependency/interaction edges
- V2 template-filled PRD suite generation, agent PRDs, collaboration map, user guide, progress states, and validation
- Optional AI enhancement endpoint with provider fallback, origin checks, optional bearer token, input bounds, and timeouts
- Supabase-backed project/document-version persistence, phase tracking, restore, subscription/quota reads, and billing UI wiring
- Browser-side Markdown/JSON/HTML export plus PDF print flow and Word-compatible HTML .doc export
Technical approach & boundaries
Technology
- TypeScript, React 18, React Router, Vite 6, SWC
- Tailwind CSS v4, Framer Motion, Lucide React
- Bun-oriented Hono server with static serving
- Supabase Auth/Postgres/Edge Functions
- Stripe-related checkout, portal, webhook, and subscription functions
- Optional Anthropic, Vercel AI Gateway, and DeepSeek providers
Limitations & readiness
- Substantial source implementation / portfolio prototype. Publish configuration exists, but production deployment, customers, users, quantified outcomes, and production guarantees are unverified.
- README is only 72 bytes and lacks setup, architecture, demo, or verification documentation
- No verified production URL, deployment, clients, metrics, outcomes, or end-to-end test proof
- Supabase, Stripe, and AI depend on external configuration, deployed functions/schema, and provider keys
- AI enhancement is best-effort and can return template output with default/unspecified placeholders
- Pricing-copy claims such as SSO/SAML, audit retention, API access, GitHub export, ZIP, and collaboration are not independently verified
- PDF depends on browser printing and Word export is HTML saved as .doc
- AppArchitect-Foundation is public but empty, so it supplies no implementation evidence
Inside the idea.
Public project notes and a separate visual interpretation.
Stack
- TypeScript, React 18, React Router, Vite 6, SWC
- Tailwind CSS v4, Framer Motion, Lucide React
- Bun-oriented Hono server with static serving
- Supabase Auth/Postgres/Edge Functions
- Stripe-related checkout, portal, webhook, and subscription functions
- Optional Anthropic, Vercel AI Gateway, and DeepSeek providers
Implemented notes
- Auth-gated interview spanning product, audience, features, privacy, roles, technical needs, integrations, design, testing, and monetization
- Rule-based follow-ups, answer validation/quality scoring, and suggestions
- Conditional agent-team composition with roles and dependency/interaction edges
- V2 template-filled PRD suite generation, agent PRDs, collaboration map, user guide, progress states, and validation
- Optional AI enhancement endpoint with provider fallback, origin checks, optional bearer token, input bounds, and timeouts
- Supabase-backed project/document-version persistence, phase tracking, restore, subscription/quota reads, and billing UI wiring
- Browser-side Markdown/JSON/HTML export plus PDF print flow and Word-compatible HTML .doc export
Repository links
Conceptual provenance. The alternate view is an original portfolio diagram based only on this public project record. It is not a product screenshot, live data, or a claim about a shipped interface.
What this could become for you.
These are proposed client adaptations—not claims that they have already been delivered.
Potential engagements & deliverables
- founder discovery-to-PRD sprint with normalized brief, MVP requirements, acceptance criteria, and Markdown/HTML package
- agent-ready build handoff with team roster, responsibility matrix, dependency map, architecture brief, and implementation checklist
- PRD quality/gap review with completeness scoring, ambiguity log, advisory safety/privacy checklist, traceability matrix, and revisions
- documentation maintenance with versioned PRD updates, change summaries, and validated export formats
- separately scoped productization covering schema/auth persistence, Stripe test-mode wiring, provider configuration, and smoke tests
Related work
- Public family sources: fvckfac3/apparchitect-final (substantial prototype) and fvckfac3/AppArchitect-Foundation (empty specifications placeholder).