Primiso
About UsPricingDocs
Sign InGet Started
Documentation/Resources
Getting Started
  • What is Primiso
  • Organizations & Members
  • Projects
Resources
  • Contexts
  • Instructions
  • Skills
  • Prompt Templates
  • Checklists
  • Agent Profiles
Collaboration & Governance
  • Versioning & Publishing
  • Roles & Permissions
  • Activity
Library
  • Library
Connecting AI Tools
  • MCP & AI Integrations
Account & Billing
  • Account Settings
  • Billing & Plans

Instructions

AI behavior rules, coding conventions, naming standards, and security requirements — in one place.

Instructions capture the rules you want any AI tool (or new hire) to follow: AI behavior rules, coding conventions, naming standards, security requirements, documentation standards, and team workflows.

What an Instruction is for

Instructions work exactly like Contexts structurally — a title, description, Markdown content, draft/published status, and full version history — but they're the resource type to reach for when what you're writing is a rule to be followed, rather than background knowledge to be understood.

  • Use a Context for "here's how our system works."
  • Use an Instruction for "here's what you must always/never do."

Typical Instructions: "Naming Conventions," "No Raw SQL Outside the Repository Layer," "Every PR Needs a Test," "How to Handle Secrets in Code."

Creating an Instruction

  1. Open a project and go to its Instructions tab.
  2. Click Create, give it a title and optional description, and write the rule(s) in the Markdown editor. Numbered or bulleted lists work well for a set of related rules.
  3. Save — it's created as v1, in draft.

Write Instructions the way you'd want an AI assistant to actually read them: direct, imperative language ("Always...", "Never...") reads more reliably than a paragraph explaining the reasoning — save the reasoning for a linked Context if it's worth capturing.

Editing, versions, and publishing

Identical mechanics to Contexts: title/description edits are separate from content edits, every content save creates a new version rather than going live immediately, and an org admin explicitly sets a version as Main to publish it. See Versioning & Publishing for the full walkthrough.

Who can write

Creating, editing, publishing, and deleting an Instruction requires org-admin-level project access (owner/moderator). Everyone with project access can read every Instruction, draft or published.

Connecting Instructions to AI tools

Once published and granted to an MCP connection, an Instruction is exactly the kind of resource an AI coding assistant benefits most from having on hand automatically — see MCP & AI Integrations.

PreviousContextsNextSkills

On this page

What an Instruction is forCreating an InstructionEditing, versions, and publishingWho can writeConnecting Instructions to AI tools
Primiso

The centralized knowledge layer for organizations using AI.

Product

  • Pricing
  • Documentation
  • Contact

Company

  • About Us
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 Primiso. All rights reserved.