Summary
Reverse-engineering summary
A prompt pack to rebuild a Refine-like React meta-framework and wrap it with a commercial hosted layer for enterprise CRUD apps.
Pack
Refine Cloud Wrapper Reconstruction Pack
Builder
Founding engineer building a commercial framework extension or investor-backed platform team
Build objective
Recreate the framework’s core CRUD/admin primitives from scratch, then design the smallest hosted layer that converts OSS adoption into enterprise revenue.
Prompt sequence
Build-from-scratch prompt sequence
Prompt 1
MAP THE FRAMEWORK SURFACE
Identify the reusable framework primitives, extension points, and package boundaries to recreate from scratch.
Expected output
A module map with core packages, adapter surfaces, example categories, and a list of inferred but unverified extension seams.
Use when
Before writing any new code or product spec.
Expand prompt
Analyze the Refine repository as a React meta-framework for CRUD-heavy internal tools, admin panels, dashboards, and B2B apps. Reconstruct the product surface around the documented hooks and concerns: authentication, access control, routing, networking, state management, and i18n. Use the repo signals from package.json, the examples for auth-antd, auth-auth0, auth-google-login, access-control-casbin, access-control-cerbos, access-control-permify, audit-log-provider, and app-crm-minimal to infer the core modules and plugin seams. Produce a greenfield architecture map that separates framework core, adapters, example apps, docs site, and build tooling. Call out what is clearly present versus what is only implied by the examples.
Prompt 2
RECREATE THE CORE CRUD RUNTIME
Define the minimum runtime primitives needed to rebuild the framework’s core developer value.
Expected output
A framework spec with package boundaries, public API names, hook contracts, and key type-safety decisions.
Use when
When starting the base library design for a new product.
Expand prompt
Design a fresh TypeScript React framework that recreates Refine’s core developer experience for CRUD-heavy apps. Model the essential primitives around list/detail/create/edit workflows, data fetching, mutation hooks, table/grid helpers, form state, routing, and access control. Use the issue signals about useDataGrid keystroke flooding, useFieldArray SPA revisit state loss, and BaseKey UUID support to harden the API design from day one. Specify the package boundaries, public hooks/components, and the type system needed to support REST and GraphQL backends. Do not copy implementation details; rebuild the product intentionally from scratch.
Prompt 3
DESIGN THE OPINIONATED CLOUD LAYER
Turn the OSS framework into a monetizable hosted service with a clear enterprise wedge.
Expected output
A hosted-product blueprint with tier boundaries, onboarding flow, dashboard modules, and enterprise feature gates.
Use when
After the base framework surface is defined.
Expand prompt
Design the commercial hosted layer that sits on top of a Refine-like framework. Base it on the repo’s strongest commercialization signals: deploy is present, CI is present, tests/observability/billing are missing, and the target use cases are enterprise CRUD apps. Rebuild the wrapper around deployed app onboarding, environment management, release visibility, audit logs, basic observability, and performance controls. Include what should be self-serve versus enterprise-only. Keep the scope aligned to a cloud/runtime add-on, not a generic SaaS dashboard.
Prompt 4
MODEL THE AUTH AND ACCESS-CONTROL EXAMPLES
Convert example apps into canonical production patterns that a buyer can copy.
Expected output
Three starter-template specs with screens, providers, config variables, and deployment prerequisites.
Use when
When defining starter templates and migration paths.
Expand prompt
Use the example packages auth-antd, auth-auth0, auth-chakra-ui, auth-google-login, access-control-casbin, access-control-cerbos, access-control-permify, and audit-log-provider to reconstruct the most valuable starter kits for a B2B admin framework. Design three production templates: one for auth plus role-based access, one for policy-based access control, and one for audit-heavy internal tools. For each, define required screens, provider wiring, environment variables, and the minimum code needed to get to a secure first deployment. Emphasize that the original repo has partial auth evidence but no env_example, so the rebuild should include explicit setup artifacts.
Prompt 5
PLAN THE DOCS-TO-DISTRIBUTION FUNNEL
Rebuild the docs and examples into a conversion funnel that drives adoption into the hosted layer.
Expected output
A docs IA, tutorial order, and conversion funnel from example usage to hosted signup or sales contact.
Use when
When planning growth and developer acquisition.
Expand prompt
Reconstruct the documentation and example strategy for a framework that has strong OSS pull but only partial docs evidence. Use the repo’s README headings, Docusaurus documentation package, and example-heavy structure to design a docs system that teaches framework adoption and then funnels users into the hosted layer. Include how to present the difference between headless core, UI adapters, access-control examples, and commercial cloud features. Produce a site map, tutorial sequence, and conversion points from docs to cloud trial.
Prompt 6
DEFINE THE QUALITY BARRIERS
Set the minimum trust bar needed before selling a hosted wrapper to enterprise buyers.
Expected output
A quality checklist with test coverage goals, telemetry events, release gates, and upgrade-safety requirements.
Use when
Before launching a paid layer or SLA offering.
Expand prompt
Using the repo’s evidence gaps and issue highlights, define the non-negotiable quality gates for a commercial Refine reconstruction. Focus on missing tests, missing observability, missing env_example, and the recent issues around key typing, form state, and request throttling. Propose a test strategy, release checks, observability events, and upgrade safety checks that would make a hosted runtime credible for enterprise use. Keep this grounded in the repo’s current signal: deploy and CI are present, but production trust signals are incomplete.
Prompt 7
PRIORITIZE THE FIRST PAID PRODUCT
Choose the smallest commercial feature set most likely to convert OSS users into paid customers.
Expected output
A ranked monetization shortlist, a recommended first paid offer, and the validation criteria for launch.
Use when
After mapping the framework and cloud layer options.
Expand prompt
Rank the first paid features for a Refine-like commercial wrapper. Use the repo’s commercialization paths: hosted cloud built around the framework, enterprise support and commercial SLAs, and paid performance, deployment, or observability add-ons. Score each option against evidence from the repository: strong OSS distribution, active cadence, deploy and CI present, tests and observability missing, and a framework archetype rather than a standalone SaaS app. Recommend the first paid offer, the ICP, the packaging, and the proof needed before expanding scope.