Help

AI Workstyle Export

A portable prompt framework designed to extract working habits, communication preferences, and domain context from an existing AI assistant to jump-start your work with Dobbin.

AI Tools

  • ChatGPT: Open a new chat and paste the prompt. The prompt is already written to force ChatGPT to pull from its saved memory and custom instructions.

  • Claude: Paste the prompt inside the specific Claude Project you use for your daily work. If you do not use Projects, just paste it into a new standard chat.

  • Google Gemini and Microsoft Copilot do not build cross-thread memory profiles across separate conversations, so there is no source to run an extraction prompt against.

Comprehensive Extraction Prompt

This 5-step AI Workstyle Export takes 10–15 minutes and offers the most precise calibration. It is ideal for anyone with extensive chat history or saved instructions in Claude or ChatGPT. Use this version whenever possible so your AI can audit its memory, remove stale habits, and give Dobbin an accurate baseline.

Paste the following bolded prompts into your AI of choice, making sure you answer any open questions between steps.

Step 1: Ground rules and inventory

I'm going to ask you a series of questions to build a work profile of me that I'll bring into another tool. Rules for every answer:

  • Only use your saved memory, custom instructions and our past conversations.
  • If you don't know something, say "unknown." Don't guess to fill gaps.
  • Leave out health, finances, family, relationships and other personal-life details.
  • End every answer with a short "Questions for you" list. Include anything you're unsure about, anything based on thin evidence, and anything that might be outdated. Write each one so I can answer it quickly (yes/no, or a short fill-in). I'll answer them in my next message.

First: tell me what you have access to about me (saved memory, chat history, custom instructions) and roughly how much.

[Address any open questions]

Step 2: Work facts

What do you know about my work? Cover three levels:

  1. My role: responsibilities and direct collaborators (by role).
  2. The company: what it does, how the organization works, core priorities, departments.
  3. Projects and functional areas: active initiatives, goals, reference docs or playbooks, and domain terms or acronyms, grouped by department or project.

Skip generic lists of everyday software.

[Address any open questions]

Step 3: How I want to be worked with

What do you do differently for me than you would for a default user? Cover length, tone, format, how much you push back, whether you ask questions or make assumptions, and what you explain versus skip. What rules or banned approaches have I told you to avoid? How do I define quality, and what do I trade off when time is tight (for example, speed versus thoroughness)?

[Address any open questions]

Step 4: Patterns

Based on how I use you: What tasks do I bring you most often? Where am I clearly an expert, and where am I still learning? How would you describe my writing voice, and what would you need to know to draft as me? What are my work strengths, and where do I tend to get stuck? Briefly give the evidence for each.

[Address any open questions]

Step 5: Compile

Compile everything into three ready-to-paste sections. Include my answers to your questions. Leave out anything I said was wrong. If something is a guess I never confirmed, don't put it in the sections. Put it in the open questions list at the end instead.

SECTION 1: INDIVIDUAL (Personal Profile in Dobbin HQ)

  • Working Style & Trade-offs

  • Personal Rules & Dislikes

  • My Role & Scope

  • My Voice

  • Expertise Map

SECTION 2: COMPANY OVERVIEW (Global Knowledge in Dobbin HQ)

  • Company Overview & Priorities

  • Organization & Departments

  • Company Lexicon

SECTION 3: CHANNEL KNOWLEDGE (department or project channels, e.g. #cs, #product, #launch)

One block per department or project from Step 2:

  • [Channel / Project Name]

    • Mission & Active Work (with dates)

    • Source of Truth Documents

    • Recurring Tasks

    • Domain Terms

Express Extraction Prompt

If you are short on time, use the 2-step Express version (3–5 minutes). Designed for quick onboarding or tools with limited memory, it captures your core role, trade-offs, voice, and rules so Dobbin can adapt immediately.

Paste the following bolded prompts into your AI of choice, making sure you answer any open questions between steps 1 and 2.

Step 1: Extract and audit

I'm building a work profile to transfer into another tool. Use your saved memory, custom instructions and our conversation history to answer the sections below. If something is unknown, write "unknown." Don't guess, and leave out all personal-life details.

  1. Role, company and projects:
    • My role, team and main collaborators (by role).
    • Company overview, core business priorities and company-wide terms.
    • Active projects, playbooks and reference docs, grouped by department or project.
  2. Working style and trade-offs: How you adjust response length, tone, format and pushback for me. How I define quality, what I trade off when time is tight (for example, speed versus thoroughness), and any rules or constraints I've given you.
  3. Tasks, expertise and voice: The tasks I bring you most often, where I'm an expert versus still learning, my writing voice, and acronyms or phrases I use a lot.

End with a "Questions for you" list. Include anything you're unsure about, anything based on thin evidence, anything that might be outdated, and big gaps in what you know about my work. Write each one so I can answer it quickly (yes/no, or a short fill-in).

[Address any open questions]

Step 2: Compile for transfer

Compile the final output into three ready-to-paste sections. Include my answers to your questions and leave out anything I said was wrong. If something is a guess I never confirmed, don't put it in the sections. Put it in the open questions list at the end.

SECTION 1: INDIVIDUAL (Dobbin HQ Bio)

  • How to work with me: tone, response length, format, pushback level, questions vs. assumptions, quality trade-offs.
  • Rules and constraints: things to avoid, banned phrases, hard boundaries.
  • Role and voice: role scope, direct collaborators (by role), writing voice, sample phrasing.
  • Expertise map: expert areas (skip the basics) vs. learning areas (explain more).

SECTION 2: COMPANY OVERVIEW (Global Knowledge Base)

  • Company overview and priorities: mission, main goals, operating principles.
  • Organization and structure: departments, who owns what, company-wide terms.

SECTION 3: CHANNEL KNOWLEDGE (Channel-Specific Knowledge Base)

One block per department, project or initiative:

  • [Channel / Project Name]
    • Active priorities: current goals, open problems, deadlines (with dates).
    • Source documents: playbooks, specs or templates for this area.
    • Recurring workflows: common tasks and questions for this area.
    • Project terms: project-specific acronyms and terms.

Loading Your Profile Into Dobbin

Where you add your AI Workstyle Export depends on whether the information is personal to your working style or relevant to the team, and whether you interact with Dobbin in a private space.

Add your Individual Context to your Dobbin HQ Bio

This context governs how Dobbin adapts to your personal tone, constraints, and quality trade-offs across all channels without exposing personal preferences to colleagues.

  1. Navigate to Dobbin HQ and open Home > Your Profile (or Getting Started > Your Bio).
  2. Paste the compiled SECTION 1: INDIVIDUAL text directly into the bio editor.

Add Your Company Overview To Your Global Knowledge Base

This context establishes company-wide background, core operating priorities, and universal vocabulary across all workspace conversations.

  1. Export this section as a document.
  2. Navigate to Dobbin HQ and open Knowledge Base from the sidebar.
  3. Upload the compiled SECTION 2: COMPANY OVERVIEW doc and select Global availability.

Add Your Channel Knowledge To Channel-Specific Knowledge Base

This context scopes project playbooks, current milestones, and specialized terminology to specific teams without creating noise across the rest of the workspace.

You can add to a channel-specific knowledge base either directly in Slack or within HQ.

To add it within Slack:

  1. Ask Dobbyn to add the document to its knowledge base from a Slack conversation in the correct channel.

To add it via HQ:

  1. Export this section as a document.
  2. Navigate to Dobbin HQ and open Knowledge Base
  3. Upload the compiled SECTION 3 as a document to the target channel