TPEE is a Windows app that helps you write better instructions for AI tools like ChatGPT and Claude — so you get the answers you actually wanted, spend less on wasted tokens, and keep every prompt private on your own machine. 100% offline.
Get TPEE — from $20 Try it in the browser
The app, right in your browser — click the menus
Interactive replica of the tpee.exe top bar (Build 294). Menus open like the real app; the items are illustrative — the download does the real work.
The 5-step Prompt Enhancing Workflow — tick the square, then click the arrows
Complete the prompt sections as you would in normal prompt editing.
Interactive replica of the “USE PROMPT ENHANCING WORKFLOW” (Build 294). Tick the square, then walk the steps with the arrows or the numbered circles — the colours change exactly as in the app. The download does the real workflow. Read how it works ↓
Interactive demo of the app's 📋 Copy to Clipboard and 👁 Preview buttons (Build 294) — a demo only, to simulate the real application: the buttons work exactly like the app, but the prompt behind them is a fixed, complete example (the GreenHouse-One project) with all 12 editor sections filled in. In the real app they copy and preview YOUR sections.
This is what will be copied to the clipboard:
You are a senior embedded firmware engineer with 15 years of experience shipping low-power sensor products on ESP32 hardware. You specialise in C/C++ for the Arduino framework, non-blocking state machines, and explaining design decisions clearly to mixed-skill teams. 1. Review the current firmware in the Data section and identify every blocking call. 2. Refactor loop() into a non-blocking state machine with named states. 3. Add hysteresis and a minimum run time to the fan and pump outputs. 4. Comment every function with one line stating its contract. 5. Flag anything that could fail after 30 days of unattended operation. We are building GreenHouse-One, a climate controller for a 3 m x 2 m hobby greenhouse. The first prototype worked for a week, then the pump relay stuck ON because loop() blocked for 47 seconds during a Wi-Fi reconnect and the watchdog reset the board mid-cycle. The firmware must run unattended for months. This is version 2 of the firmware and the hardware is already built, so pin assignments cannot change. Hardware Platform: ESP32-S3-DevKitC-1 (8 MB PSRAM, dual-core 240 MHz). Sensors: SHT31 temperature/humidity on I2C 0x44 (SDA GPIO8, SCL GPIO9), DS18B20 soil temperature on GPIO4, capacitive soil moisture on ADC1_CH3. Actuators: fan relay GPIO12, pump relay GPIO13, both active-LOW. Power: 5 V 2 A supply; the pump draws 800 mA. Toolchain: Arduino IDE 2.3 with the arduino-esp32 core 3.x. Target: 24/7 operation with Wi-Fi telemetry every 60 s. Answer in Markdown with exactly four headings: ## Diagnosis, ## Refactored Code, ## Wiring Notes, ## Test Checklist. All code in fenced blocks with the language tag. List every behavioural change as a before/after pair under ## Diagnosis. Two developers maintain this project: an electronics engineer with a strong C background who is new to FreeRTOS, and a final-year student. Both read C fluently; neither has shipped a 24/7 embedded product before. Direct and methodical. Explain WHY each change matters, not just WHAT changed. No marketing language, no hedging. Cite the datasheet section when you make a hardware claim. Attached below: main.ino (current firmware, 340 lines), the SHT31 datasheet section 4.5 (measurement timing), the relay module schematic, and a serial log excerpt showing the 47-second watchdog reset during the Wi-Fi reconnect at 03:12:44. input: The fan relay chatters when the temperature hovers at the setpoint. output: Add 2 C hysteresis — fan ON at setpoint + 2, OFF at setpoint - 1 — plus a 30-second minimum run time, implemented as explicit states in the state machine under ## Refactored Code. Include an ASCII wiring table under ## Wiring Notes: SHT31 SDA -> GPIO8, SCL -> GPIO9 with 4.7k pull-ups; DS18B20 data -> GPIO4 with a 4.7k pull-up; soil moisture signal -> GPIO3 (ADC1_CH3); fan relay IN -> GPIO12; pump relay IN -> GPIO13; common ground rail mandatory. None. This project is developed fully offline and TPEE never connects to any MCP server. All reference material the model needs is attached in the Data section. If the work is split across agents: Agent 1 reviews sensor timing and I2C error handling, Agent 2 refactors the Wi-Fi reconnect path, Agent 3 writes the hardware test checklist. Merge their findings into one consistent answer before replying.
What is it like to edit a prompt in TPEE? Each of the 12 section editors is shown as an interactive replica of the real application, right here in your browser — one editor at a time.
The Persona editor, exactly as in the real app — type your own persona, or click the 📋 -- Select or Type -- button to pick from 275 ready-made personas, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Be specific about expertise - 'You are an expert Rust programmer with 10 years experience in systems programming and embedded development' vs vague 'You are helpful'
● YELLOW: Basic role definition - 'You are a programming assistant' or 'Act as a code reviewer'
💡 TIP: Think about what specific knowledge, experience, or perspective the AI should have for your task.
This interactive replica of the app's Persona editor works exactly like the real thing (Build 294) — the same 275-persona library in the 📋 -- Select or Type -- dropdown (type in the filter box to narrow it; when exactly one name matches, the app applies it straight away), the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules, the same 📋 Quality Guidance text and colours, and a working 📋 Copy Persona to Clipboard button. One honest difference — the app saves your persona into your prompt file; this browser replica keeps it only while the page is open.
The Instructions editor, exactly as in the real app — type your own instructions, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Use precise action verbs - 'Analyze the memory management patterns and explain potential memory leaks' vs 'Make the code better'
● YELLOW: Basic actions - 'Review this code' or 'Explain how this works'
💡 TIP: Start with strong verbs: analyze, create, design, implement, optimize, debug, refactor, document. Be specific about what you want done.
This interactive replica of the app's Instructions editor works exactly like the real thing (Build 294) — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules (start with a strong action verb like analyze, create or explain, be specific, and avoid vague words like good or nice), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Instructions to Clipboard button. One honest difference — the app saves your instructions into your prompt file; this browser replica keeps them only while the page is open.
The Context editor, exactly as in the real app — type your own context, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Relevant background info - 'This is a real-time embedded system with 64KB RAM constraints, using Rust no_std' vs generic context
● YELLOW: Basic context - 'This is for a web application' or 'Working on a school project'
💡 TIP: Include technical constraints, target environment, performance requirements, or specific domain knowledge needed. Keep it focused and relevant.
This interactive replica of the app's Context editor works exactly like the real thing (Build 294) — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules (good context is informative but concise: the app scores word count against text density), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Context to Clipboard button. One honest difference — the app saves your context into your prompt file; this browser replica keeps it only while the page is open.
The Technical Specs editor, exactly as in the real app — type your own technical specifications, or click the 📟 -- Select Hardware -- button to pick from 230 development boards and auto-fill the specs, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Detailed technical requirements - 'ARM Cortex-M4 @ 168MHz, 1MB Flash, 192KB RAM, SPI interface @ 10MHz max, <100µs interrupt latency, MISRA-C compliance'
● YELLOW: Basic specs - 'Microcontroller with 1MB memory, fast SPI' or 'Embedded system requirements'
💡 TIP: Include specific hardware (processor, memory, interfaces), performance constraints (timing, power), standards compliance (MISRA, ISO), and environmental requirements (temperature, EMI). Use exact numbers and units.
This interactive replica of the app's Technical Specs editor works exactly like the real thing (Build 294) — the same 🔧 Hardware / Development Board Selection with 230 boards (type in the Filter box to narrow the list; when exactly one board matches, the app selects it straight away), the same board photos (the app's own bundled photos, resized for the web — click a photo to enlarge it), the same auto-fill that writes the selected board's platform, MCU, features and best-for into the editor, the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules (specific hardware, constraints, exact numbers and units), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Technical Specs to Clipboard button. Two honest differences — the app saves your specs into your prompt file while this replica keeps them only while the page is open, and the app's 📂 Open Image Folder button (it opens Windows Explorer) does not exist on the web.
The Format editor, exactly as in the real app — specify exactly how you want the output formatted, watch the live Quality: indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Precise format specs - 'Return as JSON with fields: {"issue": string, "severity": 1-5, "fix": string}' or 'Markdown with ## headers, code blocks, and bullet points'
● YELLOW: Basic format - 'JSON format' or 'As a numbered list'
💡 TIP: Specify exact structure, field names, data types, headers, or markup. Think about how you want to consume the output.
This interactive replica of the app's Format editor works exactly like the real thing (Build 294) — the same fixed-height monospace editor, the same live Quality: indicator (Poor / Needs Work / Good) that re-scores on every keystroke with the app's own rules (name a structure like JSON, a table or a bullet list, plus specifics like headers, sections or markdown), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Format to Clipboard button. One honest difference — the app saves your format into your prompt file; this browser replica keeps it only while the page is open.
The Audience editor, exactly as in the real app — describe who will read or use the output, watch the live Quality: indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Specific audience with experience level - 'Senior embedded systems engineers familiar with ARM Cortex-M and real-time constraints' vs generic 'developers'
● YELLOW: Basic audience - 'C++ programmers' or 'Students learning Rust'
💡 TIP: Consider experience level, domain knowledge, technical background, and what they already know vs. what needs explanation.
This interactive replica of the app's Audience editor works exactly like the real thing (Build 294) — the same fixed-height monospace editor, the same live Quality: indicator (Poor / Needs Work / Good) that re-scores on every keystroke with the app's own rules, the same 📋 Quality Guidance text and colours (a specific audience with an experience level scores best), and a working 📋 Copy Audience to Clipboard button. One honest difference — the app saves your audience into your prompt file; this browser replica keeps it only while the page is open.
The Tone editor, exactly as in the real app — describe the communication style you want, watch the live Quality: indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Specific communication style - 'Technical and precise, like code review comments with constructive suggestions' vs generic 'professional'
● YELLOW: Basic tone - 'Formal and detailed' or 'Casual and friendly'
💡 TIP: Think about formality level, technical depth, teaching style, and emotional approach. Match the tone to your audience and purpose.
This interactive replica of the app's Tone editor works exactly like the real thing (Build 294) — the same fixed-height monospace editor, the same live Quality: indicator (Poor / Needs Work / Good) that re-scores on every keystroke with the app's own rules, the same 📋 Quality Guidance text and colours (a specific communication style scores best), and a working 📋 Copy Tone to Clipboard button. One honest difference — the app saves your tone into your prompt file; this browser replica keeps it only while the page is open.
The Data editor, exactly as in the real app — specify your data sources, references or documentation, watch the live Quality: indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Specific data sources - 'Use ARM Cortex-M4 reference manual section 4.3.2 and MISRA-C 2012 Rule 11.3 for pointer casting guidelines' vs generic references
● YELLOW: Basic data - 'Company coding standards' or 'Project requirements document'
💡 TIP: Include specific standards, documentation sections, code repositories, or datasets. Be precise about version numbers and relevant sections.
This interactive replica of the app's Data editor works exactly like the real thing (Build 294) — the same fixed-height monospace editor, the same live Quality: indicator (Poor / Needs Work / Good) that re-scores on every keystroke with the app's own rules, the same 📋 Quality Guidance text and colours (specific data sources with exact versions and sections score best), and a working 📋 Copy Data to Clipboard button. One honest difference — the app saves your data into your prompt file; this browser replica keeps it only while the page is open.
The Example(s) editor, exactly as in the real app — show concrete input/output examples, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Clear input/output pairs - 'Input: unsafe { ptr.read() } Output: {"issue": "Unsafe pointer dereference", "severity": 4, "fix": "Add null check before dereferencing"}'
● YELLOW: Basic examples - 'For example: check memory allocation' or 'Like analyzing malloc() calls'
💡 TIP: Show concrete before/after examples. Demonstrate the exact input format and desired output structure. Multiple examples show edge cases.
This interactive replica of the app's Example(s) editor works exactly like the real thing (Build 294) — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules (it looks for concrete input/output pairs or phrases like for instance and such as, and rewards several examples), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Example(s) to Clipboard button. One honest difference — the app saves your examples into your prompt file; this browser replica keeps them only while the page is open.
The Graphics editor, exactly as in the real app — describe the diagrams and visual elements you want, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Specific visual requirements - 'Generate UML sequence diagram showing memory allocation flow with timing annotations and error paths' vs generic 'make a diagram'
● YELLOW: Basic graphics - 'Flow chart of the process' or 'Simple block diagram'
💡 TIP: Specify diagram type, content details, annotations, colors, layout, and purpose. Think about what visual elements will clarify your technical content.
This interactive replica of the app's Graphics editor works exactly like the real thing (Build 294) — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules, and the same 📋 Quality Guidance text and colours (a specific diagram type with content, annotations and purpose scores best). Two honest notes — the Graphics section has no copy button in the app (mirrored here exactly), and the app saves your graphics details into your prompt file while this browser replica keeps them only while the page is open.
The MCP Servers editor, exactly as in the real app — note the MCP server configurations your prompt should cite, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Specific MCP server configurations with endpoints and capabilities
● YELLOW: Basic server names or generic configurations
💡 TIP: Configure Model Context Protocol servers for enhanced AI capabilities and tool integration.
This interactive replica of the app's MCP Servers editor works exactly like the real thing (Build 294) — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules, the same 📋 Quality Guidance text and colours, and a working 📋 Copy MCP Servers to Clipboard button. Two honest notes — this section is configuration text for your prompt: TPEE itself never connects to any MCP server (it is 100% offline by design), and the app saves your text into your prompt file while this browser replica keeps it only while the page is open.
The Agents editor, exactly as in the real app — define the AI agents your prompt should orchestrate, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: Specific agent definitions with roles, capabilities, and workflows
● YELLOW: Basic agent names or simple configurations
💡 TIP: Define AI agents with specific roles, capabilities, and interaction patterns for complex task automation.
This interactive replica of the app's Agents editor works exactly like the real thing (Build 294) — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rules, the same 📋 Quality Guidance text and colours (specific agent definitions with roles, capabilities and workflows score best), and a working 📋 Copy Agents to Clipboard button. One honest difference — the app saves your agents configuration into your prompt file; this browser replica keeps it only while the page is open.
Real, unretouched screens of the app — the product is the proof. Click or tap any screen to expand it.
Every screen is a real 1080×2340 capture — click or tap any screenshot to expand it full screen, or browse all seven categories in the full gallery.
What do TPEE's functions actually do? Each one is shown as an interactive replica of the real application, right here in your browser — one function at a time.
The User's Manual button, click it to see a sample
This interactive replica of the User's Manual shows the complete manual exactly as it ships with the app (Build 294) — the same three documents, the same table of contents. Download the app to always carry the latest edition with you.
The Learning menu's Open Learning Center button, click it to see a sample
This interactive replica of the Learning Center - TPEE Professional AI Course shows the complete course exactly as it ships with the app (Build 294) — the same 83 lessons and the same 249 quiz questions, the same window layout. Take a real quiz: it is graded exactly like in the app. One honest difference — the app saves student progress to disk; this browser replica keeps it only while the page is open. Or read three of the most-asked questions for free on the web: what prompt engineering is, what MCP servers are, and what an AI agent is. The whole course is online too: all 83 lessons, free to read.
The IDE combobox, click it to see a sample
This interactive replica of the app's IDE combobox shows the 34 IDE profiles exactly as they ship with the app (Build 294) — the same list, the same selection behaviour, the same status line. In the real app the chosen IDE also drives prompt formatting, export, scoring and the optimization tips. The IDE list is updated weekly in the real app — download the app to always carry the latest IDE profiles with you.
The Model combobox, click it to see a sample
This interactive replica of the app's Model combobox shows the 191 AI models across 20 providers exactly as they ship with the app (Build 294) — the same list, the same type-to-filter box, the same provider groups, the same selection behaviour, the same status line. In the real app the chosen model also drives prompt formatting, scoring, the optimization tips and the PRD generator — and on first run the app pre-selects its default, Claude Fable 5. The model list is updated weekly in the real app — download the app to always carry the latest model profiles with you.
The Show API Limits button, click it to see a sample
This interactive replica of the app's API Character Limits panel shows the 191 AI models across 20 providers exactly as they ship with the app (Build 294) — the same provider columns, the same cards, the same pricing, the same newest-first order. Two honest differences: in the real app the coloured bar on each card fills with your live prompt's character count and shifts green → yellow → orange → red as you approach the model's limit (here it sits at 0%), and the gold frame follows your selected model (the app pre-selects Claude Fable 5 on first run). The limits and pricing are updated weekly in the real app — download the app to always carry the latest numbers with you.
The Show Kimi / Commands button, click it to see a sample
This interactive replica of the app's per-model command reference panel shows the same offline command sheets exactly as they ship with the app (Build 294) — the same 16 model-family sheets, the same tutorial, the same "Selected:" banner. The replica starts on Kimi K3, so the button reads "Show Kimi / Commands" and opens the "Kimi / Commands (reference)" window; pick any model in the Model combobox above and the button and the window follow automatically — Models / Commands change with the selected model, exactly like the real app (a GLM model now opens its own GLM sheet, and a Hermes model opens the Hermes sheet (Build 294)). The command sheets are updated weekly in the real app — download the app to always carry the latest commands with you.
The Show Tips button, click it to see a sample
This interactive replica of the app's Optimization Tips panel shows the same context-aware tips exactly as they ship with the app (Build 294) — the same tip engine, the same four categories (📐 Structure, 🎨 Style, 📏 Length, ⚡ Features), the same colours. The tips are computed for the IDE and the model selected in the IDE and Model comboboxes above and change automatically with your selection, exactly like in the real app — try it: open the tips, then pick another IDE or model above and watch the window follow (on first run the app itself pre-selects Cursor + Claude Fable 5). The optimization tips are updated weekly in the real app — download the app to always carry the latest tips with you.
The 📋 Projects Prefixes button, click it to view the Projects Prefixes Library window
This interactive replica shows the app's File Name / Project Prefix toolbar row and the 📋 Projects Prefixes Library window exactly as they ship with the app (Build 294) — the same fields, the same defaults (File Name "prompt.txt", Project Prefix "T1042CW"), the same Add / quick-add / select / remove behaviour, the same status messages. Everything works: type a prefix, add it to the library, click a saved prefix to load it into the Project Prefix field, remove one with the 🗑 button — saved prefixes name your files PREFIX_Pmt_NNNN.txt (e.g., T1042CW_Pmt_0001.txt). One honest difference — the app saves your library to its preferences file so it survives restarts; this browser replica keeps it only while the page is open.
0 sections found
Offline tutorial system: lessons, quizzes, students, scores. No AI call, no MCP server, no external connection.
Current prefix: T1042CW
No saved prefixes yet. Add one above.
Everything in TPEE exists to answer one question: is this prompt ready? The score tells you. The sections show you why.
The Use Prompt Enhancing Workflow button turns prompt writing into a guided conversation: TPEE wraps your prompt between a Pre-Prompt and a Post-Prompt, you paste the bundle into any LLM chat, and the model helps you improve the prompt before you ever use it. How it works ↓
Prominent featurePersona, Instructions, Context, Technical Specs, Format, Audience, Tone, Data, Examples, Graphics, MCP Servers, Agents — twelve sections, each with a GREEN/YELLOW/RED readiness indicator, rolled into a 0–100 quality score.
191 model profiles across 20 providers, with pricing, context windows, and API character limits — so the prompt you write fits the model you'll actually run.
Format once, export anywhere: 34 IDE profiles including Cursor, VS Code variants, Claude Code, Kiro, and Devin Desktop.
A local prompt library with version history and automatic backups keeps every draft safe on your machine.
PRD Innovator turns rough ideas into structured requirements.
Claude Team Designer and the Team Management suite organize multi-agent work.
83 lessons and 249 quiz questions, built in. TPEE doesn't just hold your prompts — it teaches the craft.
A catalogue of development boards with photos, for prompt engineers who also push bits.
High-contrast, color-blind-support, and low-vision themes make the editor usable by everyone on the team.
TPEE runs from your USB stick, so you can learn anywhere you go: insert the USB stick into any Windows-compatible computer, double-click the TPEE.exe file on it (no installation required) and continue learning on the go. Your learning progress is kept on the USB stick — nothing is installed on the computer you plugged it into.
Prominent featureDon't just write a prompt. Have a conversation with the LLM about it first. One button in the top panel guides you through five steps using local files and your clipboard. TPEE never contacts an LLM; you drive the conversation.
Pre-Prompt + Your Prompt + Post-Prompt → clipboard → LLM chat → TPEE_Pmt_0001_Enhanced.txt100% local: marker lines frame your prompt like delimiters in a serial protocol, companion files live next to your prompt, and the only transport is your clipboard. No network, no account, no middleman.
Built for individuals, students, job seekers, and teams.
The full editor, scoring, and IDE export on your own machine — no account required to write.
Full app, 4 months of updates. Apply from the pricing section — we review applications ourselves.
USD $20 · pending approvalFull app, 4 months of updates. Apply from the pricing section — we review applications ourselves.
USD $20 · pending approvalTeam Management (shared templates, task assignment, team canvases) is built into the app. The team plan is not on sale yet — see pricing for current plans.
A development-board catalogue with photos, for engineers who also push bits.
83 lessons and 249 quiz questions, built in. TPEE doesn't just hold your prompts — it teaches the craft.
83 lessons · 249 quiz questions · included in every plan
One-time purchase. Updates are included with every plan — no subscriptions.
Estimate for · IPUSD $20 pending approval
Estimated:
USD $49 one-time
Estimated:
USD $99 one-time
Estimated:
USD $99 one-time
Estimated:
No free plan — every plan helps cover the infrastructure it runs on.
Accepted beta testers get 30% off the Professional plan with code BETA30 — see the beta program.
Put the price in context: ChatGPT Plus and Claude Pro are $20 a month — $240 a year, forever. TPEE is a one-time $49 (Starter) and keeps working after the 6 months of updates. A single afternoon of wasted API calls costs more than the licence.
Refunds: within 14 days of purchase, no questions asked — we issue the refund through Stripe minus the payment processor's non-refundable processing fees. Just email us from your order address.
Made by Toptronic® Limited, Hong Kong — a small team who answer their own email. Read who we are.
Prompt engineers work in every one of these companies behind these household names.
Straight answers, no fine print.
Yes — the app makes no network calls at runtime. No telemetry, no account needed to write prompts. Verify with your firewall; we encourage it. (The website and Stripe checkout are online, obviously.)
That warning appears for apps without an expensive EV code-signing certificate — not because something is wrong. Click “More info → Run anyway”. Before you do, verify your download against the SHA-256 hash we publish on our Security page.
No — running the infrastructure costs money, so every plan is paid. The Student and Job Seeker plans are USD 20.00 each, pending approval: apply from the pricing section and we review every application ourselves, then reply by email.
Each of the 12 prompt sections is checked for completeness and internal consistency, shown as GREEN/YELLOW/RED, and rolled into a 0–100 score. It won't write the prompt for you — it tells you when you've done the work.
34 profiles, including Cursor, VS Code and its variants, Claude Code, Kiro, and Devin Desktop — plus a general formatter if your tool isn't listed.
191 model profiles across 20 providers, with pricing, context windows, and API character limits. TPEE doesn't call these models for you — it helps you write prompts that fit them.
Both. Same app, same build: MSI for a normal Windows install, ZIP for run-from-anywhere (no admin rights needed).
Windows 10 and 11 only, for now. It's a native Rust/egui app, and we'd rather support one platform properly than three poorly.
Accepted beta testers get 30% off the Professional plan (code BETA30) in exchange for short monthly feedback. Details and application: beta program.
Compare it to a ChatGPT Plus or Claude Pro subscription — see the numbers on the pricing page.
TPEE makes zero network calls at runtime. No MCP connections, no analytics, no phone-home. You can verify that with your own firewall — we encourage it.
Receive updates — enter your details and confirm by email. No spam, unsubscribe any time.
New TPEE builds, download links, and update news — from [email protected].
Latest new features and the TPEE newsletter — from [email protected].
Buy TPEE Professional as a gift. The recipient receives the licence by email with the message “This is the Gift of the Future” and your name as the giver.
We need your first name, surname and email so we can send your licence, your receipt and your download link. Payment is processed securely by Stripe.