Engineering Team Conventions

Set AI Team Conventions Everyone Shares

When every teammate explains the project differently, AI gets a different story each time. Shared team conventions give it one consistent account.

Overview

Inconsistent AI output often starts with inconsistent humans: each person primes the model with their own version of the rules. A shared conventions profile fixes the source. This setup captures the standards for Field Notes, an editorial content project where house voice is the product — plain, concrete, second-person, every claim sourced. The Content Project mode adds editorial principles; your conventions pin the voice and the rules; the never-assume list bars invented facts and quotes. One profile, shared by the team, means the AI hears the same story from everyone.

Workflow

  1. Agree the conventions

    The voice, the standards, the rules everyone should be priming the AI with.

  2. Put them in one profile

    Mode-driven principles plus your own, in a single shared document.

  3. Everyone uses the same one

    Consistent input, consistent output, no per-person drift.

Why This Works

  • A shared profile removes the per-person variation that causes inconsistent results
  • Content Project mode contributes editorial principles teams forget to state
  • The never-assume list is the team's collective "don't do this" written down once

Best for

  • Teams where consistency is the product
  • Editorial and content operations
  • Anyone whose AI output varies by who prompted it

Not for

  • A personal one-off prompt — use the Prompt Template Builder
  • Defining a single role's behavior — use the Role Prompt Generator

Use cases

  • Teams where consistency is the product
  • Editorial and content operations
  • Anyone whose AI output varies by who prompted it

Tip: Save time by exploring related resources and tools that integrate with this workflow.

Explore all resources