Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
Scene Card Writer is a local-first story planning utility for writers who want structured scene cards, POV balance, chapter tension checks, rewrite queues, manuscript surgery packets, and exportable outline variants w...
$4.99 · In-app purchases
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Your first Build Kit is free with a verified email.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for Scene Card Writer: map the core Productivity workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Scene Card Writer is a local-first story planning utility for writers who want structured scene cards, POV balance, chapter tension checks, rewrite queues, manuscript surgery packets, and exportable outline variants without an account, AI API, cloud workspace, or subscription. Create scene cards, track chapter beats, point of view, locations, character pressure, scene tension, revision status, and review the next concrete rewrite action before drafting. What you can do: - Create and edit local scene cards - Track chapter, beat, POV, location, characters, status, and tension - Review a prioritized rewrite queue for missing outcomes, weak conflicts, outline-only scenes, and continuity checks - Copy a manuscript surgery packet with scene-by-scene rewrite actions - Review a chapter revision map with tension, POV, missing outcomes, weak conflicts, and outline-only flags - Capture each scene's goal, conflict, outcome, and drafting note - Review POV lanes with chapter counts, average tension, and open flags - Copy chapter outlines, POV outlines, conflict-only passes, rewrite queues, and revision checklists - Keep story material private on device Scene Card Writer stores records locally on device. There is no account, no subscription, no in-app purchases, no advertising SDK, no analytics SDK, no tracking, no AI API, no cloud sync, and no developer-server upload. Story outlines leave the device only when you choose to copy or share them through iOS.
Written user reviews are not shown here. Check current App Store reviews >
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: Difficulty in organizing large numbers of scenes
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Lack of collaboration features
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Limited export options for scripts
Validate with people who use this workflow before building.
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
Not assessed in a Build Kit yet.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.