> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prophic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Instructions: AI Governance per Stage

> Add AI governance rules to each Prophic pipeline stage. Custom Instructions enforce your tech stack, terminology, and formatting from the first generation.

Custom Instructions are AI governance rules attached to a specific pipeline stage. When Prophic runs that stage (Requirement Analysis, Functional Specification, Work Breakdown, or Proposal generation), it applies your instructions before drafting, so output follows your team's standards from the first pass.

## Where to find them

Open **Configurations** in the left navigation, then select **Custom Instructions**.

## What Custom Instructions can do

* Enforce your preferred tech stack in **Technical Specifications**.
* Flag specific requirement categories during **Requirement Analysis**.
* Enforce a formatting convention across documents.
* Apply an effort buffer to certain task categories in the **WBS**.
* Use client-specific terminology in any stage.

## Add an instruction

<Steps>
  <Step>
    Open **Configurations**, then **Custom Instructions**.
  </Step>

  <Step>
    Click **Add Instruction**.
  </Step>

  <Step>
    Write the guidance text.
  </Step>

  <Step>
    Select one or more pipeline stages where it applies.
  </Step>

  <Step>
    Save the instruction.
  </Step>
</Steps>

The instruction applies to the next generation of the selected stages.

## Example instructions

<Accordion title="Tech stack override for Technical Specifications">
  Always recommend Next.js for the frontend, PostgreSQL for the database, and AWS Lambda for serverless compute. Do not suggest Firebase or MongoDB unless the brief explicitly requires them.
</Accordion>

<Accordion title="Non-functional requirement flagging for Requirement Analysis">
  Flag accessibility (WCAG 2.1 AA), GDPR compliance, and performance budgets (Lighthouse score above 90) as mandatory non-functional requirements for every project.
</Accordion>

<Accordion title="QA and integration buffer for Work Breakdown">
  Add a 15% complexity factor to any task that involves third-party API integration or cross-browser QA. Label these tasks clearly in the WBS.
</Accordion>

<Accordion title="Client-specific terminology for any stage">
  When working with Acme Corp, use the term "platform" instead of "application" and refer to end users as "members" rather than "users".
</Accordion>

## How instructions interact with regeneration

Instructions apply to new generations. Existing outputs do not retroactively change. Regenerate the affected stage to apply an updated instruction.

<Note>
  Custom Instructions are included on Pro, Teams, and Enterprise plans.
</Note>

<CardGroup cols={2}>
  <Card title="Configuration Templates" icon="layers" href="/setup/configuration-templates">
    Bundle service roles with rates and buffers for consistent estimates.
  </Card>

  <Card title="Pre-Sales Workflow" icon="book-open" href="/concepts/pre-sales-workflow">
    Understand how the five pipeline stages build on each other.
  </Card>
</CardGroup>


## Related topics

- [Service Roles: Your Library of Team Personas](/setup/service-roles-and-rates.md)
- [How AI Credits Work in Prophic](/concepts/ai-credits.md)
- [Proposal Templates: Branded PDF and DOCX Layouts](/setup/proposal-templates.md)
- [Prophic Plans, Pricing, and Billing Details](/plans-and-billing.md)