Adding Genesis Context

June 24, 2026 · View on GitHub


Table of Contents


Overview

When you build apps with Taskade Genesis, you can upload reference files to provide context and guidance. The additional context helps AI understand your requirements, match your brand, and follow specific design patterns — producing apps that feel like they were custom-built by your team.

Any files you upload are automatically added to the Media tab and become part of your Workspace DNA, enriching all future app builds and AI agent responses.


What You Can Use as Context

Taskade Genesis works with a wide range of file types to understand your requirements:

Brand & Design Files

File TypeWhat to UploadHow Genesis Uses It
Brand guidelines (PDF)Color codes, typography, logo usage, design principlesMatches your exact brand identity
Logo files (PNG, JPG)Primary logos, variations, icons, brand marksPlaces logos and creates consistent visual identity
Color palettesHex codes, color combinations, visual hierarchyApplies your exact color scheme throughout the app
Website screenshotsCurrent site design, layout patterns, UI elementsReplicates your existing design language
Mockups / wireframesApp layouts, user interface designs, navigation flowsBuilds to your exact specifications

Data & Structure Files

File TypeWhat to UploadHow Genesis Uses It
Existing forms (PDF)Contact forms, registration forms, surveysRecreates your form structure digitally
Data examplesTable structures, field definitions, sample recordsCreates matching database schemas
Workflow documentsProcess flows, SOPs, business rulesBuilds automation logic and business rules
Spreadsheets (XLSX, CSV)Customer data, inventory lists, schedulesPre-populates databases and creates appropriate views
Code snippetsValidation rules, integration examplesImplements specific logic requirements

Reference Materials

File TypeWhat to UploadHow Genesis Uses It
App screenshotsUI inspiration, feature examples, interaction patternsReplicates design patterns you like
Competitor toolsScreenshots of competitor appsBuilds competitive alternatives
Process documentationStandard procedures, user manuals, training materialsCreates apps that follow your processes
Requirements docsFeature specs, acceptance criteria, use casesImplements exact feature requirements
API/Tech docsAPI specs, integration guides, config filesConnects to your existing systems

{% hint style="info" %} Connecting Genesis to Taskade programmatically? See the Public API reference. {% endhint %}

Supported Upload Formats

CategoryFormats
DocumentsPDF, DOCX, TXT, MD, PPTX, XLSX, CSV, EPUB
ImagesPNG, JPG, GIF, SVG, WebP
Web sourcesYouTube videos, blog URLs, tweets, Reddit posts, news articles
Cloud storageGoogle Drive, Dropbox, Box, OneDrive

Provide App Context

There are two ways to provide context depending on where you are in the building process.

Initial Prompt (New App)

When first creating an app, attach context alongside your prompt:

StepAction
1Open Taskade Genesis and type your initial app prompt
2Add files: Drag & drop into the prompt box, or click the Attachment button
3Choose source: Upload Files (device), Add from Workspace (existing files), or Add from Cloud (cloud storage)
4Submit the prompt — Genesis creates the app using your text + uploaded context

Example prompt with context:

"Build a customer portal for my consulting firm. Use the brand guidelines I've uploaded for colors and fonts. The wireframe shows the layout I want. The spreadsheet has our current client list."

Follow-Up Prompts (Existing App)

After Genesis creates your app, upload additional context to refine it:

StepAction
1Open your Genesis app in Preview mode
2Add files: Drag & drop into the chat box, or use the Attachment button
3Ask Genesis to update the app using the new context

Example follow-up prompts:

Context AddedPrompt
Brand PDF"Update the contact form to match our brand guidelines. Use the colors and fonts specified in the uploaded PDF."
Competitor screenshot"Make our dashboard layout more like this competitor screenshot, but keep our brand colors."
Data spreadsheet"Import the customer data from this spreadsheet into the app's database."
Process document"Update the booking workflow to match the steps in this SOP document."
Logo files"Replace the placeholder logo with our uploaded logo files."

Context Best Practices

PracticeWhyExample
Upload brand files firstSets the visual foundation for everythingBrand PDF + logos before any styling prompts
Include data samplesHelps Genesis create accurate database schemas5-10 sample records with all field types
Show, don't just tellScreenshots and mockups are more precise than wordsUpload a wireframe instead of describing layout
Add incrementallyToo much context at once can dilute focusBrand first, then data, then workflows
Use specific file namesHelps you reference files in prompts"brand-guidelines-2025.pdf" not "document1.pdf"
Include edge casesPrevents gaps in logic"Here's an example of a canceled order..."

How Context Powers Workspace DNA

Every file you upload becomes part of your workspace's living memory:

Context AddedDNA ImpactFuture Benefit
Brand guidelinesAll future apps use your brand automaticallyConsistent brand across every app
Data samplesAI agents understand your data structuresSmarter agent responses and queries
Process documentsAutomations follow your business rulesMore accurate workflow generation
Competitor screenshotsGenesis understands your market positionBetter feature recommendations
Customer dataDatabases pre-populated and properly structuredFaster app deployment

Workspace DNA hint: Context uploads increase the richness of your workspace memory, which directly improves your Intelligence Score and makes every future app smarter.


What's Next

GuideWhat You'll Learn
Image GenerationGenerate custom images for your apps
Advanced FeaturesUse your brand context to customize app appearance
Agent Knowledge & MemoryTrain AI agents on your uploaded files
Projects & DatabasesHow uploaded data becomes structured databases