Project Purpose
The purpose of this project is to extract structured context from simulated websites (“gyms”) like Redfin, Airbnb, or Linear. Workers must capture Tool Overview, Environment, Actions (with limitations), and UI Description in a comprehensive and organized format.
Task Instructions
Extract Context into Four Sections:
Tool Overview: What the tool is and its purpose. Environment: User setup, roles, pre-existing data. Actions (with limitations): All possible actions with navigation paths; explicitly note limitations. UI Description: Full list of interactable elements on every form/page, including input types and dropdown choices.
Preserve Hierarchy and Formatting: Use headers and sub-headers accurately. Maintain clean, structured formatting for LLM consumption.
Be Comprehensive and Precise: Capture every interactable item systematically. List dropdown options exactly unless already provided in the Environment. Use clear, testable language — no vague terms like “etc.” or “various.”
High-Level Definitions
Tool Overview – Description of the product’s purpose and domain. Environment – Current state (user role, accounts, datasets, configurations). Action – A state-changing operation with measurable outcome (e.g., Create Budget). Limitation – Explicit note of what the system cannot do or where actions are restricted. UI Description – Comprehensive list of interface elements, fields, and inputs, with types (e.g., dropdown, text field, date picker). Atomic Action – The smallest indivisible action (e.g., Add Transaction), not bundles of actions.
✅ Acceptable Submissions include:
Clearly written sections organized under the correct headers and sub-headers Full listing of all actions with navigation paths and any limitations Comprehensive UI descriptions covering every interactable item, with input data types specified Dropdowns/choice lists explicitly written out (unless already described in the Environment section) Formatting consistent with the Firefly example (hierarchical, clean, structured)
❌ Unacceptable Submissions include:
Missing one or more required sections (e.g., no UI Description) Incomplete or vague descriptions (e.g., “several options” instead of listing exact choices) Mixing capabilities or tags (these are added later by AI, not by workers) Poor formatting that breaks hierarchy and makes the file unusable by an LLM Skipping interactable UI elements, fields, or dropdown options that are visible in the gym
Examples of Incorrect Work:
Writing “Frequency dropdown with multiple options” instead of listing: daily, weekly, monthly, yearly Placing “User role: Admin” under UI Description instead of Environment Combining multiple actions into one vague entry like “manage accounts” instead of atomic actions like “Add Account,” “Edit Account,” “Delete Account.”
Next, please read through the
