Act as a Senior Federal Proposal Manager and Technical Editor with 20+ years of experience in [AGENCY_NAME] procurements. Your goal is to create a comprehensive Proposal Style Guide for the following opportunity: [OPPORTUNITY_NAME].

### INPUT CONTEXT
- Solicitation/RFP Number: [RFP_NUMBER]
- Primary Service: [SERVICE_TYPE]
- Target Audience: [AUDIENCE_TYPE] (e.g., Technical Evaluation Board, Contracting Officer)

### STYLE GUIDE REQUIREMENTS
Generate a structured style guide that includes the following sections:

1. **Voice and Tone**: Define how we should sound (e.g., authoritative, partner-oriented, mission-focused). Specify the use of active vs. passive voice in the context of federal commitments.
2. **Terminology & Taxonomy**: Provide a table of 'Use This' vs. 'Not That' terms based on the specific agency's culture and the RFP's specific nomenclature.
3. **Compliance Formatting**: Detail rules for acronym introduction, citation styles for past performance, and formatting for 'Features, Benefits, and Proof Points'.
4. **The 'Win Theme' Integration**: Instructions on how to weave the theme of [PRIMARY_WIN_THEME] into technical descriptions.
5. **Evaluation Optimization**: Specific guidance on using 'Action Verbs' that align with the LPTA or Tradeoff source selection process.
6. **Prohibited Language**: List 'fluff' words or unsubstantiated claims (e.g., 'world-class', 'unique') that evaluators often penalize.

### CONSTRAINTS
- Adhere to GPO (Government Publishing Office) style basics unless otherwise specified.
- Ensure the tone bridges the gap between technical expertise and executive summary readability.
- Focus on 'Substantiation'—every claim must be followed by a 'Because' or 'As evidenced by'.

Deliver the output in a clean, Markdown-formatted document ready for distribution to a writing team.