TWCarter Prompt Builder

Description

TWCarter Prompt Builder helps visitors improve how they communicate with AI. It is a coaching application rather than a general chatbot. The coach can ask focused clarification questions, explain how a stronger prompt works, and provide a ready-to-copy prompt for use in the visitor’s preferred AI tool.

Current features include:

• Conversational prompt coaching with up to three clarification rounds.
• Recognition of prompts that are already strong enough to use.
• Browser microphone input when supported by the visitor’s browser.
• A five-request daily visitor allowance with administrator exemption.
• Signed clarification sessions and short-lived preview authorization.
• Privacy-conscious operational activity logging.
• Optional conversation-text logging, disabled by default on new installations.
• Operations Center, activity viewer, native AI telemetry, settings, and retention cleanup.
• Adaptive Memory Foundation with dedicated storage and version-history tables. Memory services are disabled by default and do not automatically save or retrieve user memories in this release.

TWCarter Prompt Builder preserves its educational purpose. Adaptive memory is being developed to personalize coaching without silently collecting visitor prompts or bypassing the coaching process.

AI Provider Configuration

TWCarter Prompt Builder supports two AI-provider paths:

• Native OpenAI, implemented inside TWCarter Prompt Builder through the WordPress HTTP API.
• WordPress AI Compatibility, using the optional AI and AI Provider for OpenAI plugins when an administrator chooses that compatibility path.

Native OpenAI is now the default provider for new installations. AI and AI Provider for OpenAI are no longer declared as required plugins. The WordPress AI Compatibility path remains available when those plugins are installed, providing an optional compatibility path.

External Services

TWCarter Prompt Builder uses OpenAI as an external AI service when a visitor submits a prompt for coaching or requests an Example Preview. Native OpenAI requests are sent to https://api.openai.com/. An OpenAI account and API key are required when Native OpenAI is selected. OpenAI API usage may incur charges under the administrator’s OpenAI account.

Prompt text, clarification answers, coaching instructions, and Example Preview content needed to fulfill the request are sent to OpenAI using the provider selected by the site administrator. Native OpenAI sends the request directly from the WordPress server through the WordPress HTTP API. WordPress AI Compatibility sends it through the installed WordPress AI Client and OpenAI provider plugin. TWCarter Prompt Builder does not send AI request content to TWCarter Technology Consulting for processing.

When Native OpenAI is selected, the administrator supplies an OpenAI API key in TWCarter Prompt Builder Settings. The saved key is used server-side only, is not included in public browser JavaScript, and is not printed back into the settings screen after saving.

These requests occur only after a site administrator configures an AI provider and a visitor submits a coaching or Example Preview request. TWCarter Prompt Builder does not use the OpenAI connection for advertising or independent visitor tracking.

Use of OpenAI is subject to OpenAI’s applicable business/API terms, service terms, and privacy practices. Site administrators are responsible for reviewing those terms and for configuring the OpenAI provider appropriately for their site.

OpenAI Services Agreement: https://openai.com/policies/services-agreement/

OpenAI Service Terms: https://openai.com/policies/service-terms/

OpenAI Privacy Policy: https://openai.com/policies/privacy-policy/

Browser speech recognition, when available, is provided by the visitor’s browser and browser vendor. Visitors can always type instead of using voice input.

Privacy

TWCarter Prompt Builder separates operational activity logging from conversation-text logging.

Operational activity can record events such as opening the coach, starting voice input, submitting a prompt, receiving a clarification, completing coaching, requesting a preview, encountering an error, or leaving before completion. Visitor identifiers are stored as anonymized hashes rather than full IP addresses.

Conversation-text logging is disabled by default on new installations. If a site administrator enables it, visitor prompt text and coach response text for completed AI interactions can be stored locally in the site’s WordPress database for the configured retention period. The default retention period is 30 days. Administrators can disable conversation logging independently of operational activity logging.

Adaptive Memory is disabled by default. Version 4.0.0 does not automatically create memories, retrieve memories, reflect on a user’s profile, create embeddings, or inject memories into AI requests.

Visitors should not enter confidential, sensitive, or secret information into TWCarter Prompt Builder.

Site administrators should update their site’s privacy policy to describe their actual configuration and any external AI provider they enable.

Deactivation and Uninstall

Deactivating TWCarter Prompt Builder stops its scheduled log-cleanup event but preserves plugin settings, the saved provider configuration, activity data, and Adaptive Memory Foundation tables so the plugin can be reactivated without losing configuration or history.

Deleting the plugin through the WordPress Plugins screen performs an uninstall. Uninstall removes TWCarter Prompt Builder settings, including the saved OpenAI API key, plugin-owned temporary values and scheduled events, operational/conversation activity tables, and Adaptive Memory Foundation tables and version history. This deletion is permanent.