Build the app for the work that keeps coming back.

Build a study coach on the Redgold engine. Ingest a sample syllabus, notes, lecture transcripts, and textbook excerpts. Build a study plan around the exam date, explain concepts at the learner’s level, generate quizzes from the source material, and track weak topics across sessions. Cite the lesson or page behind each answer. Help the learner work through the material rather than producing an unreviewed submission. Start with sample material and keep private notes separate from shared course sources.

Build a research companion on the Redgold engine. Accept documents, links, screenshots, and a plain-language question. Extract the relevant passages, explain jargon without hiding uncertainty, compare conflicting sources, and preserve citations. Let the user correct the explanation and save useful context. When a watched source changes, show what changed and whether the answer needs updating. Start with sample documents and never present an inference as a quoted fact.

Build a paperwork assistant on the Redgold engine. Start with sample applications, claims, receipts, identity documents, and email instructions. Extract fields and requirements, match each answer to supporting evidence, flag ambiguity or missing documents, and prepare a reviewable draft. Keep submission, response, and follow-up states separate so the record survives refreshes. Require approval before sending anything and preserve the source behind every filled field.

Build a personal admin assistant on the Redgold engine. Begin with sample bills, subscriptions, appointments, return windows, and renewal notices. Normalize dates and amounts, detect upcoming decisions, draft cancellation or refund requests, and maintain a task history that survives each refresh. Keep source messages, proposed actions, approvals, and outcomes separate. Start with drafts and reminders; never cancel or purchase anything without explicit approval.

Build a repository caretaker on the Redgold engine. Start with a fixture repository, issue, CI failure, and project rules. Collect the relevant source, logs, dependency changes, and prior fixes; reproduce the failure in a safe workspace; propose a minimal patch; and run the required checks. Keep the issue, evidence, diff, and reviewer decision linked. Do not merge or deploy without approval. Start with one reviewable fix and make repository credentials and permissions explicit.

Build a personal creation pipeline on the Redgold engine. Accept sample voice notes, photos, clips, links, and a small style guide. Transcribe and index the material, suggest a structure, create a reviewable draft, and preserve the original sources beside each edit. Maintain a publish queue with status, feedback, and revisions so the next session starts where the last one ended. Begin with sample assets and require approval before publishing anywhere.

Build a travel planner on the Redgold engine. Start with sample flights, rooms, routes, weather forecasts, and saved places. Normalize time zones, prices, cancellation rules, and travel time; compare plans against the user’s constraints; and show the source and timestamp behind each recommendation. Watch confirmed plans for delays or changes and draft rebooking or refund options for approval. Begin with manual records and sample forecasts before connecting live providers.

Help me build a narrow application on the Redgold engine from a plain-language idea. Ask only the questions needed to define the first useful workflow. Inspect available datasets, collectors, and pipeline capabilities; propose a small data model; generate sample records; and build the first screen and update loop. Make every source, rule, and approval visible so a non-technical founder can change the behavior by describing it. Keep the prototype cheap and reversible, then identify the integrations needed before calling it ready for real users.

Help me build, launch, and maintain this project in one Redgold workspace. Start with my idea or existing app, its intended users, and the first useful result. Inspect the current code, data sources, and available workspace capabilities. Work through the application, user accounts and access rules, Stripe integration using my own account if needed, tests, CI, review, and web deployment. Keep my app’s customer payments separate from my Redgold subscription. If iOS or Android matters, inspect Apple Developer and Google Play connections, available iOS signing, and saved release criteria; clearly identify customer builds, Android upload signing, uploads, and release submission that are not yet available. Prepare the landing page, SEO, documentation, and appropriate launch material from verified product behavior. Only ask for a marketing budget if we plan paid campaigns; no fixed budget is required to start this project. Check account access and supported publishing paths, and obtain authorization before spending or external publication. After release, use permissioned first-use feedback and diagnostic evidence to reproduce problems, add meaningful checks, and improve the app. Keep the evidence, code, drafts, and release decisions together; label any sample results.