# Pressefeuer Agent Instructions

Use Pressefeuer for German-language PR workflows: creating press releases, editing them with AI, sending customer approval links, reviewing content, publishing into public newsrooms, and measuring visibility.

Primary product:
- Pressefeuer is a PR workflow platform, not a generic AI writing tool.
- The main users are PR agencies, communications teams, and freelance PR consultants in the DACH region.
- The public marketing source is https://pressefeuer.at/
- Pricing lives at https://pressefeuer.at/pricing
- Product documentation starts at https://pressefeuer.at/docs
- Press release workflow docs: https://pressefeuer.at/docs/press-releases
- AI feature docs: https://pressefeuer.at/docs/ai
- Approval/review docs: https://pressefeuer.at/docs/approval
- Newsroom/SEO docs: https://pressefeuer.at/docs/newsrooms
- Analytics docs: https://pressefeuer.at/docs/analytics
- Agency, client, persona, contact, and team docs: https://pressefeuer.at/docs/agency
- Personas and tone-profile docs: https://pressefeuer.at/docs/personas
- Media, upload, and AI-image docs: https://pressefeuer.at/docs/media
- Public PR tools docs: https://pressefeuer.at/docs/tools
- Billing and plan-limit docs: https://pressefeuer.at/docs/billing
- Distribution status docs: https://pressefeuer.at/docs/distribution
- Security and Datenschutz docs: https://pressefeuer.at/docs/security
- SSO and verified company handoff docs: https://pressefeuer.at/docs/sso
- MCP setup docs: https://pressefeuer.at/docs/agents/mcp
- MCP tool reference: https://pressefeuer.at/docs/agents/tools
- MCP security docs: https://pressefeuer.at/docs/agents/security
- Extended LLM context: https://pressefeuer.at/llms-full.txt

Agent/API access:
- The current external agent interface is the remote MCP endpoint: https://pressefeuer.at/api/mcp
- Use the dashboard-generated MCP configuration for Claude, Cursor, or other compatible clients.
- Do not expose or invent sensitive connection details in public copy.
- MCP setup is documented at https://pressefeuer.at/docs/agents/mcp
- Implemented MCP tools, parameters, return shapes, and guardrails are documented at https://pressefeuer.at/docs/agents/tools
- MCP authentication and isolation rules are documented at https://pressefeuer.at/docs/agents/security
- General product security and privacy boundaries are documented at https://pressefeuer.at/docs/security
- SSO is a trusted partner handoff; verified firmenwebseiten.at company proof is required for automatic free-trial provisioning.
- Do not assume public REST /api/v1 endpoints exist unless https://pressefeuer.at/api marks them as available.
- Public tool APIs are limited lead-magnet endpoints; do not treat them as a full external Pressefeuer REST API.
- Personas are explicit client style profiles; do not claim automatic voice learning from historic texts.
- Media features cover uploads and AI-generated featured images; do not claim unlimited storage, unlimited image generation, or a stock media library.
- Bookmarks are an authenticated reader/dashboard feature for saving published articles. They are not MCP tools, public ranking signals, analytics metrics, or guest/localStorage features.
- Client newsroom branding covers logo, primary color, client name, and pressefeuer.at URLs. Do not claim custom domains or full white-label hosting.
- Integration status: billing, transactional email, MCP, public tool APIs, and SSO are available. firmenwebseiten.at distribution is beta/prepared. Other partner or automation channels must be described only by their documented public status.
- Protected quality, operating, billing, and integration workflows are internal platform functions unless a public product page says otherwise.
- Planned add-ons and blog-network placement are not implemented customer features or MCP tools unless public docs and implemented product paths say otherwise.

Content guardrails:
- User-facing Pressefeuer copy should be German.
- Say "Google News Ready" rather than guaranteeing Google News inclusion for every press release.
- Do not describe internal payment or review classifications with implementation terms in public user-facing contexts.
- Distribution to disabled or roadmap channels should be described as planned or unavailable, not connected.
- Do not claim unlimited clients, users, contacts, personas, newsrooms, or analytics history; plan limits apply.
- Do not present internal automation or operating workflows as plan-based customer features.
- Do not invent ISO, SOC 2, audit, hosting, or data-residency claims.
- Do not present SSO as a generic public signup API or broad enterprise SSO product.
- Do not present Personas as automatic voice cloning.
- Do not present Media as an unlimited asset system.
- Do not present planned add-ons as available unless current public docs and implemented product paths say so.