Step 1 of 11
Define the affiliate agent scope and data model
Set the exact product scope, entities, relationships, and success metrics before building screens or AI features.
Keep version 1 narrow: one operator, manual affiliate offer entry, tracked clicks, recorded earnings, and AI content generation.
Create the initial architecture for an AI affiliate marketing agent application. Include a concrete data model for affiliate programs, offers, campaigns, content assets, tracked links, click events, conversions, earnings entries, and compliance rules. Also define the main user flows: add an offer, create a campaign, generate content, use tracked links, record conversions or earnings, and view reporting. Generate the actual schema and wire it into the app foundation so later steps can build on real persisted data.
Expected after this step
A working project scaffold with persistent data structures and clear app sections for offers, campaigns, content, link tracking, and analytics.
Should not happen
- ✕AI builds a pretty dashboard with hardcoded sample metrics instead of computing from stored click and revenue data
- ✕AI generates content but does not attach it to campaigns, offers, or persistent records
- ✕AI adds affiliate links directly without implementing tracked redirect or click logging
- ✕AI claims conversion tracking exists but only stores a placeholder field with no input path or import flow
Verify before continuing
Do not move on until every check is true. The complete button stays locked until then.
Do not continue if…
- !AI builds a pretty dashboard with hardcoded sample metrics instead of computing from stored click and revenue data
- !AI generates content but does not attach it to campaigns, offers, or persistent records
- !AI adds affiliate links directly without implementing tracked redirect or click logging
- !AI claims conversion tracking exists but only stores a placeholder field with no input path or import flow
- !AI ignores disclosure requirements and creates risky promotional copy
- !AI builds campaign cards and statuses visually but does not persist status changes in the database
If the AI messes this up
Use this when the AI fakes progress or breaks the feature. It forces a real fix.
The current build is too shallow. Replace any placeholder data structures with real persistent models for offers, campaigns, content assets, tracked links, click events, conversions, and earnings. Update the app so all future pages read from and write to these real records instead of mock data.