TPEE is ’n Windows-toep wat u help om beter instruksies vir AI-instrumente soos ChatGPT en Claude te skryf — sodat u die antwoorde kry wat u werklik wou hê, minder op vermorste tokens spandeer, en elke prompt privaat op u eie masjien hou. 100% vanlyn.
TPEE is a Windows 10/11 desktop application. It installs on your PC and runs entirely offline, so buying it from a phone works but installing it does not — open tpee.app on the computer you will use, and the trial, the download and the licence all work there. There is no macOS or Linux build yet, and there is no cloud version. If you want the Linux or the Apple build, put your name on the list — you will be written to once, when that build exists, and not before.
Kry TPEE — vanaf $49 Probeer dit in die blaaier
Start the 14-day free trial — the full editor, no card. Ready to buy? See which plan fits.
Offline prompt engineering editor for Windows 10 and 11 · one-time USD $49, $99 or $299 · no subscription. The editors you can click on this page are the real interface, running in your browser with sample text — what you type is not sent anywhere. See the plans.
Looking for one specific thing? The Windows prompt editor, the prompt engineering tool it is built to be, the prompt builder that turns thirteen sections into one prompt, and the dictionary of AI that defines the 90 terms the course uses — each page answers that question on its own.
40+ years of experience condensed in TPEE
Die toep, reg in u blaaier — klik op die spyskaarte
Interaktiewe replika van die tpee.exe-kruisbalk. Kieslyste maak oop soos in die werklike app; die items is slegs ter illustrasie — die aflaai doen die werklike werk.
Die 5-stap Prompt Enhancing Workflow — merk die vierkant, klik dan op die pyltjies
Complete the prompt sections as you would in normal prompt editing.
Interaktiewe replika van die “USE PROMPT ENHANCING WORKFLOW”. Merk die vierkant, loop dan die stappe met die pyltjies of die genommerde sirkels — die kleure verander presies soos in die toep. Die aflaai doen die regte werkvloei. Lees hoe dit werk ↓
Prompt OnBoarding — the toolbar toggle opens the floating checklist
👁 TPEE can see: 0 of 6 working-environment rows ready · 0 of 13 sections written
Next step: READ THE USER'S MANUAL AND COMPLETE ALL LESSONS
1. Before you start
2. Working environment
3. Fill the prompt sections
4. Use the Prompt Enhancing Workflow
5. Finish and copy
Interaktiewe replika van die app se OnBoarding-skakelaar en sy swewende Prompt OnBoarding-kontrolelys — net 'n demo, om die werklike toepassing te simuleer. Druk die skakelaar om die kontrolelys te wys of te versteek, presies soos die nutsbalkknoppie in die app doen; merk die rye en die vordering, die lewende opsomming en die Volgende-stap-reëls dateer op dieselfde manier op. In die werklike app skakel hierdie knoppie die venster slegs vir die huidige sessie om — die merkie onder Preferences is die een wat besluit of die venster daar sal wees by die volgende opstart.
Die 🗑 Clipboard-Clear all-knoppie langs Copy to Clipboard en Preview is die app se derde knipbordbeheer. Dit maak TPEE se eie knipbord en ook die Windows-knipbordgeskiedenis leeg (die lys wat jy met Win+V oopmaak), sodat 'n prompt wat jy in 'n kletsvenster gekopieer het nie daarna deur enigiemand by die sleutelbord weer uit die geskiedenis geplak kan word nie. Dit flits groen en oranje terwyl dit werk en bly groen sodra die knipbord bewysbaar leeg is. Op hierdie bladsy is dit net dieselfde animasie — 'n demo, om die werklike toepassing te simuleer; niks in jou blaaier se knipbord word aangeraak nie.
Interaktiewe demo van die toep se 📋 Copy to Clipboard- en 👁 Preview-knoppies — net ’n demo, om die regte toepassing te simuleer: die knoppies werk presies soos die toep, maar die prompt agter hulle is ’n vaste, volledige voorbeeld (die GreenHouse-One-projek) met al 13 redigeerderafdelings ingevul. In die regte toep kopieer en voorskou hulle U afdelings.
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.
TPEE keeps six paths on screen so you always know where your project lives: the Working Directory, the two Prefix History folders (chats-and-actions and session-start), your Prompts folder, your TPEE Settings folder and your PRDs folder. That is a tall block, so one button folds it away when you need the vertical space back. This is the button and the six rows, exactly as the app draws them.
Interaktiewe replika van die Show/Hide location-skakelaar en die ses padrye — net 'n demo, om die werklike toepassing te simuleer. Druk die knoppie: wanneer die paneel gewys word, lees dit Hide location of… en die ses rye is sigbaar; druk dit weer en dit lees Show location of… met die rye toegevou. In die app is dieselfde skakelaar ook 'n merkblokkie op die Preferences-kieslys, en dit word tussen sessies onthou.
Hoe voel dit om ’n prompt in TPEE te redigeer? Elk van die 13 afdelingsredigeerders word as ’n interaktiewe replika van die regte toepassing gewys, reg hier in u blaaier — een redigeerder op ’n slag. Die eerste is die opsionele Top of Prompt-redigeerder en die laaste is die opsionele Bottom of Prompt-redigeerder; die twaalf genommerde redigeerders sit tussen hulle, presies soos in die toep.
The Top of Prompt editor — the optional block that sits above the Persona editor. Switch it on and TPEE keeps a five-line Session Number heading at the top of the box; type your own framing below it, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown
● GREEN: Concise, specific content that sets the stage for the entire prompt.
● YELLOW: Generic or repeated opening text.
💡 TIP: Content here is shown ABOVE the Persona section. TPEE keeps the five-line Session Number heading at the top: "This is Session Number: NNNN", then "The Project Prefix is "PREFIX"". NNNN is the number in your file name and it follows CREATE NEXT PROMPT, NNNN-1 is the session before it, the first Read line names that session's chat and action log, the second names this session's own session-start record, and the fifth line quotes the Working Directory and says the work stays inside it; your own text below the heading is never touched.
This interactive replica of the app's Top of Prompt editor works exactly like the real thing — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rule for this block (5 words or more scores Good, 2 or more Needs Work), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Top of Prompt to Clipboard button. It is the box the app draws above the Persona editor, and the text in it is copied to the clipboard as part of the whole prompt — Top first, then the thirteen numbered sections, then Bottom. One honest difference — in the app the five-line heading follows your file name and moves with CREATE NEXT PROMPT, and the box is not saved with a prompt; this browser replica shows the heading of one real session (0742) and keeps your text only while the page is open.
Die Persona-redigeerder, presies soos in die regte toep — tik u eie persona, of klik op die 📋 -- Select or Type ---knoppie om uit 275 gereedgemaakte persona's te kies, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Persona-redigeerder werk presies soos die regte ding — dieselfde 275-persona-biblioteek in die 📋 -- Select or Type ---keuselys (tik in die filterkassie om dit te vernou; wanneer presies een naam pas, pas die toep dit dadelik toe), dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel, dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy Persona to Clipboard-knoppie. Een eerlike verskil — die toep stoor u persona in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
Die Instructions-redigeerder, presies soos in die regte toep — tik u eie instruksies, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Instructions-redigeerder werk presies soos die regte ding — dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel (begin met 'n sterk werkwoord soos analyze, create of explain, wees spesifiek en vermy vae woorde soos good of nice), dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy Instructions to Clipboard-knoppie. Een eerlike verskil — die toep stoor u instruksies in u promptlêer; hierdie blaaierreplika hou hulle net terwyl die bladsy oop is.
Die Context-redigeerder, presies soos in die regte toep — tik u eie konteks, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Context-redigeerder werk presies soos die regte ding — dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel (goeie konteks is insiggewend maar bondig: die toep tel woordaantal teen teksdigtheid), dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy Context to Clipboard-knoppie. Een eerlike verskil — die toep stoor u konteks in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
Die Technical Specs-redigeerder, presies soos in die regte toep — tik u eie tegniese spesifikasies, of klik op die 📟 -- Select Hardware ---knoppie om uit 230 ontwikkelingsborde te kies en die specs outomaties in te vul, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Technical Specs-redigeerder werk presies soos die regte ding — dieselfde 🔧 Hardware / Development Board-keuse met 230 borde (tik in die Filter-kassie om die lys te vernou; wanneer presies een bord pas, kies die toep dit dadelik), dieselfde bordfoto's (die toep se eie ingeboude foto's, vir die web verklein — klik op 'n foto om dit te vergroot), dieselfde outomatiese invul wat die gekose bord se platform, MCU, kenmerke en beste gebruik in die redigeerder skryf, dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel (spesifieke hardware, beperkings, presiese getalle en eenhede), dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy Technical Specs to Clipboard-knoppie. Twee eerlike verskille — die toep stoor u specs in u promptlêer terwyl hierdie replika hulle net terwyl die bladsy oop is hou, en die toep se 📂 Open Image Folder-knoppie (dit maak Windows Explorer oop) bestaan nie op die web nie.
Die Format-redigeerder, presies soos in die regte toep — spesifiseer presies hoe u wil hê die uitset geformateer moet word, kyk hoe die lewendige Quality:-aanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Format-redigeerder werk presies soos die regte ding — dieselfde vastehoogte-monoruim-redigeerder, dieselfde lewendige Quality:-aanwyser (Poor / Needs Work / Good) wat by elke sleuteldruk met die toep se eie reëls hertel (noem 'n struktuur soos JSON, 'n tabel of 'n kolpuntlys, plus spesifieke soos koppies, afdelings of markdown), dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy Format to Clipboard-knoppie. Een eerlike verskil — die toep stoor u formaat in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
Die Audience-redigeerder, presies soos in die regte toep — beskryf wie die uitset sal lees of gebruik, kyk hoe die lewendige Quality:-aanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Audience-redigeerder werk presies soos die regte ding — dieselfde vastehoogte-monoruim-redigeerder, dieselfde lewendige Quality:-aanwyser (Poor / Needs Work / Good) wat by elke sleuteldruk met die toep se eie reëls hertel, dieselfde 📋 Quality Guidance-teks en -kleure ('n spesifieke gehoor met 'n ervaringsvlak tel die beste), en 'n werkende 📋 Copy Audience to Clipboard-knoppie. Een eerlike verskil — die toep stoor u gehoor in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
Die Tone-redigeerder, presies soos in die regte toep — beskryf die kommunikasiestyl wat u wil hê, kyk hoe die lewendige Quality:-aanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Tone-redigeerder werk presies soos die regte ding — dieselfde vastehoogte-monoruim-redigeerder, dieselfde lewendige Quality:-aanwyser (Poor / Needs Work / Good) wat by elke sleuteldruk met die toep se eie reëls hertel, dieselfde 📋 Quality Guidance-teks en -kleure ('n spesifieke kommunikasiestyl tel die beste), en 'n werkende 📋 Copy Tone to Clipboard-knoppie. Een eerlike verskil — die toep stoor u toon in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
Die Data-redigeerder, presies soos in die regte toep — spesifiseer u databronne, verwysings of dokumentasie, kyk hoe die lewendige Quality:-aanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Data-redigeerder werk presies soos die regte ding — dieselfde vastehoogte-monoruim-redigeerder, dieselfde lewendige Quality:-aanwyser (Poor / Needs Work / Good) wat by elke sleuteldruk met die toep se eie reëls hertel, dieselfde 📋 Quality Guidance-teks en -kleure (spesifieke databronne met presiese weergawes en afdelings tel die beste), en 'n werkende 📋 Copy Data to Clipboard-knoppie. Een eerlike verskil — die toep stoor u data in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
Die Example(s)-redigeerder, presies soos in die regte toep — wys konkrete inset/uitset-voorbeelde, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Example(s)-redigeerder werk presies soos die regte ding — dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel (dit soek konkrete inset/uitset-pare of frases soos for instance en such as, en beloon verskeie voorbeelde), dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy Example(s) to Clipboard-knoppie. Een eerlike verskil — die toep stoor u voorbeelde in u promptlêer; hierdie blaaierreplika hou hulle net terwyl die bladsy oop is.
Die Graphics-redigeerder, presies soos in die regte toep — beskryf die diagramme en visuele elemente wat u wil hê, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Graphics-redigeerder werk presies soos die regte ding — dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel, en dieselfde 📋 Quality Guidance-teks en -kleure ('n spesifieke diagramtipe met inhoud, aantekeninge en doel tel die beste). Twee eerlike notas — die Graphics-afdeling het geen kopieerknoppie in die toep nie (presies hier weerspieël), en die toep stoor u grafika-besonderhede in u promptlêer terwyl hierdie blaaierreplika hulle net terwyl die bladsy oop is hou.
Die MCP Servers-redigeerder, presies soos in die regte toep — noteer die MCP-bedienerkonfigurasies wat u prompt moet aanhaal, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se MCP Servers-redigeerder werk presies soos die regte ding — dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel, dieselfde 📋 Quality Guidance-teks en -kleure, en 'n werkende 📋 Copy MCP Servers to Clipboard-knoppie. Twee eerlike notas — hierdie afdeling is konfigurasieteks vir u prompt: TPEE self koppel nooit aan enige MCP-bediener nie (dit is 100% vanlyn deur ontwerp), en die toep stoor u teks in u promptlêer terwyl hierdie blaaierreplika dit net terwyl die bladsy oop is hou.
The Verification of Results & Outcome editor, exactly as in the real app — say how you will check the result and what good and excellent look like, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown to see what makes it score GREEN
● GREEN: You name what GOOD and EXCELLENT look like AND the check you will run - 'I will verify your work by running the module on Ubuntu 24.04 and comparing the three sample outputs with section 4; good is all three matching, excellent is all three matching with the reasons for each difference written down.'
● YELLOW: A check is named but no standard - 'I will run it and see if it looks right.'
💡 TIP: Start with 'I will verify your work by ...' and then add three things: WHAT you will check (a test to run, a file or page to open, a number to read, a person to ask), WHEN you will check it (after every step, at the end, before you send it on), and what GOOD and EXCELLENT look like - so the model knows what it is aiming at. A check you cannot describe is a standard the model cannot meet. Examples: 'I will verify your work by running cargo test and reading the pass count' / 'I will verify your work by comparing every price with the supplier PDF' / 'I will verify your work by asking three real users to sign up once, unaided.'
This interactive replica of the app's Verification of Results & Outcome editor works exactly like the real thing — 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 (naming what GOOD and EXCELLENT look like and the check you will run scores best), and a working 📋 Copy Verification to Clipboard button. One honest difference — the app saves this section into your prompt file; this browser replica keeps it only while the page is open.
Die Agents-redigeerder, presies soos in die regte toep — definieer die AI-agente wat u prompt moet orkestreer, kyk hoe die lewendige kwaliteitsaanwyser by elke sleuteldruk hertel, en maak die 📋 Quality Guidance-keuselys oop om te sien wat dit GREEN laat tel
● 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.
Hierdie interaktiewe replika van die toep se Agents-redigeerder werk presies soos die regte ding — dieselfde lewendige kwaliteitsaanwyser (✗ rooi Poor, ⚠ geel Needs Work, ✓ groen Good) wat by elke sleuteldruk met die toep se eie reëls hertel, dieselfde 📋 Quality Guidance-teks en -kleure (spesifieke agentdefinisies met rolle, vermoëns en werkvloei tel die beste), en 'n werkende 📋 Copy Agents to Clipboard-knoppie. Een eerlike verskil — die toep stoor u agentskonfigurasie in u promptlêer; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
The Bottom of Prompt editor — the optional block that sits below the Agents editor. Switch it on and TPEE keeps a two-line closing instruction at the bottom of the box; type your own sign-off above it, watch the live quality indicator re-score on every keystroke, and open the 📋 Quality Guidance dropdown
● GREEN: Concise, specific closing content that wraps up the prompt.
● YELLOW: Generic or repeated closing text.
💡 TIP: Content here is shown BELOW the Agents section. TPEE keeps the two-line closing instruction at the bottom of this box: the first line asks the model to write up this session's chats and actions (the ones you typed) and names the file to save them in, the second asks for the record the NEXT session needs and names its file. The two numbers follow your file name and move with CREATE NEXT PROMPT; your own text above them is never touched.
This interactive replica of the app's Bottom of Prompt editor works exactly like the real thing — the same live quality indicator (✗ red Poor, ⚠ yellow Needs Work, ✓ green Good) that re-scores on every keystroke with the app's own rule for this block (5 words or more scores Good, 2 or more Needs Work), the same 📋 Quality Guidance text and colours, and a working 📋 Copy Bottom of Prompt to Clipboard button. It is the box the app draws below the Agents editor, and the text in it is copied to the clipboard as part of the whole prompt — Top first, then the thirteen numbered sections, then Bottom. One honest difference — in the app the two closing lines follow your file name and move with CREATE NEXT PROMPT, and the box is not saved with a prompt; this browser replica shows the closing lines of one real session (0742) and keeps your text only while the page is open.
Egte, ongeretoegeerde skerms van die toep — die produk is die bewys.
Elke skerm is 'n egte 1080×2340-vaslegging — blaai deur al sewe kategorieë in die volledige galery.
Wat doen TPEE se funksies eintlik? Elk word as 'n interaktiewe replika van die regte toepassing gewys, reg hier in u blaaier — een funksie op 'n slag.
Die User's Manual-knoppie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die User's Manual wys die volledige handleiding presies soos dit met die toep kom — dieselfde drie dokumente, dieselfde inhoudsopgawe. Laai die toep af om altyd die nuutste uitgawe by u te dra.
Die Learning-menu se Open Learning Center-knoppie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die Learning Center - TPEE Professional AI Course wys die volledige kursus presies soos dit met die toep kom — dieselfde 94 lesse en dieselfde 282 vasvra-vrae, dieselfde vensteruitleg. Neem ’n regte vasvra: dit word presies soos in die toep nagesien. Een eerlike verskil — die toep stoor studentevordering op die skyf; hierdie blaaierreplika hou dit net terwyl die bladsy oop is. Of lees drie van die mees gevraagde vrae gratis op die web: wat prompt-ingenieurswese is, wat MCP-bedieners is, en wat ’n AI-agent is. Die hele kursus is ook aanlyn: al 94 lesse, gratis om te lees.
The Learning menu's ClassRoom Presentation button, click it to see a sample
Hierdie replika wys die twee aanbiedingsmodusse van die venster wat die app lewer: al drie TV-MIRE-projektorkaarte met die PLUGE- en veilige-sone-balke, en die lesskyfies wat dieselfde 94 lesse en 282 vasvravrae as die Leersentrum bevat. Bied 'n les aan, klik op 'n kolpunt om dit uit te lig, skakel 🗒 Lecturer Notes aan, of skakel ⌨ Keys aan (af by verstek) en bestuur die skyfies met die pyltjiesleutels, Space, Page Up / Page Down en Home / End. Die venster se derde modus, 🗓 Course Organizer, is die dosent se beplanner en word langs hierdie kaart beskryf: die kursusnaam en -ligging, sy begin- en einddatum en -tyd, 'n bewerkbare dag van lesblokke en pouses, 'n Done-merkie met die opgetekende tyd vir elke kolpunt en elke les, 'n skatting van die ure en dae wat die kursus sal neem — en 'n kursuskalender wat vra op watter weeksdae die kursuslesings plaasvind, watter datums af is, en hoeveel speling om te laat vir 'n kursus wat bly groei, en dan 'n maanderooster van 42 selle teken en die beplanningsvraag in een reël beantwoord: of die dae wat jy gereserveer het genoeg is. Vier eerlike verskille: hierdie replika teken die twee aanbiedingsmodusse, nie die Course Organizer nie; dit stoor niks — die leslys se breedte en die notas-verdeler stel terug wanneer jy dit sluit, terwyl die app albei behou totdat jy TPEE sluit; Maximize vul hierdie blaaier-oortjie, nie 'n projektorskerm nie; en dit teken een donker skyfie, terwyl die app se uitligstrook jou tema volg. F1-hulp is slegs op Windows beskikbaar.
The PRD Innovator menu, click it to see everything it can do
This replica shows the whole PRD Innovator: the menu with New, Open and Save PRD and the four Quick Start rows; the Economic Sectors Day to Day Work family of one hundred and thirty-nine offices in thirty-seven sectors of activity, each sector switchable on or off; the seventeen smart blocks every office PRD carries; the PRD Editor window with its twelve sections and its Generate Prompt button; and the one-box search that finds any office by name, its summary or its sector. Click the rail on the left to walk through each part. One honest difference: this replica is read-only — it opens no file and writes nothing — and the app itself is fully offline.
The editor toolbar's OnBoarding toggle and the floating window it opens
TPEE open met 'n 27-step checklist in 'n swewende venster, voordat jy 'n woord van die handleiding gelees het: die nutsbalkknoppie lees Using OnBoarding totdat jy dit afskakel. Die stappe word gegroepeer in die volgorde waarin jy werklik werk — Voordat jy begin (lees die User's Manual, voltooi die lesse), die werkomgewing (die Working Directory, die vier Prefix-, Prompts- en TPEE Settings-paaie, File Name and Project Prefix), die prompt (die opsionele Top of Prompt-redigeerder, die twaalf afdelings, die opsionele Bottom of Prompt-redigeerder), die Prompt Enhancing Workflow, en die afrondende bewegings (Preview, Clipboard-Clear all, Copy to Clipboard, plak in jou kletsvenster). Waar TPEE 'n stap self kan sien, sê dit so langs die ry — 'n gids is ingestel of nie, 'n afdeling het teks of nie — en een knoppie merk elke stap wat TPEE al kan sien. Rye wat jou eie oordeel is, dra geen kenteken nie, want niks in die program kan hulle sien nie, en om anders te beweer sou 'n leuen wees. Niks wat jy merk word na skyf geskryf nie: die merke hou vir die loop, en die enigste instelling wat hierdie funksie onthou, is die Preferences-merkie wat besluit of die venster daar sal wees wanneer jy TPEE die volgende keer begin. F1-hulp is slegs op Windows beskikbaar.
Die IDE-kombinasiekassie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die toep se IDE-kombinasiekassie wys die 59 IDE-profiele presies soos hulle met die toep kom — dieselfde lys, dieselfde keusegedrag, dieselfde statuslyn. In die regte toep dryf die gekose IDE ook promptformatering, uitvoer, telling en die optimeringswenke. Die IDE-lys word weekliks in die regte toep opgedateer — laai die toep af om altyd die nuutste IDE-profiele by u te dra.
Die Model-kombinasiekassie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die toep se Model-kombinasiekassie wys die 187 AI-modelle oor 23 verskaffers presies soos hulle met die toep kom — dieselfde lys, dieselfde tik-om-te-filtreer-kassie, dieselfde verskaffergroepe, dieselfde keusegedrag, dieselfde statuslyn. In die regte toep dryf die gekose model ook promptformatering, telling, die optimeringswenke en die PRD-kragopwekker — en by eerste bekendstelling kies die toep self sy verstek, Claude Fable 5. Die modellys word weekliks in die regte toep opgedateer — laai die toep af om altyd die nuutste modelprofiele by u te dra.
Die Show API Limits-knoppie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die toep se API Character Limits-paneel wys die 187 AI-modelle oor 23 verskaffers presies soos hulle met die toep kom — dieselfde verskafferkolomme, dieselfde kaarte, dieselfde pryse, dieselfde nuutste-eerste-orde. Twee eerlike verskille: in die regte toep vul die gekleurde staaf op elke kaart met u lewendige prompt se karaktertelling en skuif groen → geel → oranje → rooi soos u die model se limiet nader (hier sit dit op 0%), en die goue raam volg u gekose model (die toep kies Claude Fable 5 by eerste bekendstelling). Die limiete en pryse word weekliks in die regte toep opgedateer — laai die toep af om altyd die nuutste getalle by u te dra.
Die Show Kimi / Commands-knoppie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die toep se per-model opdragverwysingspaneel wys dieselfde vanlyn opdragblaaie presies soos hulle met die toep kom — dieselfde 16 modelfamilie-blaaie, dieselfde tutorial, dieselfde “Selected:”-banier. Die replika begin op Kimi K3, dus lees die knoppie “Show Kimi / Commands” en maak die “Kimi / Commands (reference)”-venster oop; kies enige model in die Model-kombinasiekassie hierbo en die knoppie en die venster volg outomaties — Models / Commands verander met die gekose model, presies soos die regte toep (’n GLM-model maak nou sy eie GLM-blad oop, en ’n Hermes-model maak die Hermes-blad oop). Die opdragblaaie word weekliks in die regte toep opgedateer — laai die toep af om altyd die nuutste opdragte by u te dra.
Die Show Tips-knoppie, klik daarop om 'n voorbeeld te sien
Hierdie interaktiewe replika van die toep se Optimization Tips-paneel wys dieselfde konteksbewuste wenke presies soos hulle met die toep kom — dieselfde wenk-enjin, dieselfde vier kategorieë (📐 Structure, 🎨 Style, 📏 Length, ⚡ Features), dieselfde kleure. Die wenke word vir die IDE en die model bereken wat in die IDE- en Model-kombinasiekassies hierbo gekies is en verander outomaties met u keuse, presies soos in die regte toep — probeer dit: maak die wenke oop, kies dan 'n ander IDE of model hierbo en kyk hoe die venster volg (by eerste bekendstelling kies die toep self Cursor + Claude Fable 5). Die optimeringswenke word weekliks in die regte toep opgedateer — laai die toep af om altyd die nuutste wenke by u te dra.
Die 📋 Projects Prefixes-knoppie, klik daarop om die Projects Prefixes Library-venster te sien
Hierdie interaktiewe replika wys die toep se File Name / Project Prefix-nutsbalkry en die 📋 Projects Prefixes Library-venster presies soos hulle met die toep kom — dieselfde velde, dieselfde verstekke (File Name “prompt.txt”, Project Prefix “T1042CW”), dieselfde Add / vinnig-toevoeg / kies / verwyder-gedrag, dieselfde statusboodskappe. Alles werk: tik 'n voorvoegsel, voeg dit by die biblioteek, klik op 'n gestoorde voorvoegsel om dit in die Project Prefix-veld te laai, verwyder een met die 🗑-knoppie — gestoorde voorvoegsels noem u lêers PREFIX_Pmt_NNNN.txt (bv. T1042CW_Pmt_0001.txt). Een eerlike verskil — die toep stoor u biblioteek in sy voorkeurlêer sodat dit herbeginne oorleef; hierdie blaaierreplika hou dit net terwyl die bladsy oop is.
0 sections found
Offline tutorial system: lessons, quizzes, students, scores. No AI call, no MCP server, no external connection.
TV-MIRE - Colour Bars + ALIGNMENT TARGET (offline, no network, no AI call)
Lecturer Notes is on. Make your browser window taller to see the notes.
The PRD Innovator turns a rough idea into a structured Product Requirements Document. Open the menu and pick how you want to begin.
New PRD asks what kind of platform you are building and opens a document already shaped for it. Open and Save PRD read and write your own PRD files. The four Quick Start rows skip the form and begin straight away, each naming the PRD after the platform type.
The Quick Start rows ask what kind of software you are building. The Economic Sectors Day to Day Work rows ask what kind of office is doing the work. Each one opens a PRD already filled in with that office's daily requirements — the recurring tasks, the workflow, the deadlines, the records and the compliance rules.
139 of 139 offices are switched on across 37 sectors of activity.
The offices are filed under thirty-seven sectors of activity. Switch a sector on or off with the tick beside it and its whole shelf appears or disappears; two buttons turn every sector on, or every sector off, in one click. The whole tree sits in its own scroll area, so it stays usable as the family keeps growing.
Each Day to Day Work PRD ends its Requests the Assistant Will Receive section with seventeen blocks that turn a description into a brief an office can actually hand to an assistant:
Every block is written in that office's own terms — a pharmacy, a quarry, a law firm and a bakery each get their own words — so the template is a real brief rather than a description.
Any PRD opens in the PRD Editor window, a real, movable, resizable window with Maximize, Minimize and Restore. Its twelve sections are:
Each section carries a quality indicator and a character count, and the window closes with a Requests the Assistant Will Receive section. A Generate Prompt button turns the whole document into a ready-to-paste prompt, and Save, Save As and Open write and read your PRD files in the folder you chose under the Location panel.
With one hundred and thirty-nine offices, browsing the tree is fine when you know the sector and hopeless when you do not. One box searches every office in every sector at once.
3 office(s) match 'pharmacy' - by office name, summary or sector name - click one to open its PRD
A hit says why it matched — the office name, its summary or its sector — and where it sits inside its own sector. Above the box, a Today's office to try row opens a different office every day, in date order, so the whole family gets seen.
Nothing you type into a PRD leaves your machine. The app makes no outbound call except the two you switch on yourself: the update check and Send Feedback.
Current prefix: T1042CW
No saved prefixes yet. Add one above.
Alles in TPEE bestaan om een vraag te beantwoord: is hierdie prompt gereed? Die telling vertel u. Die afdelings wys u hoekom.
Die Use Prompt Enhancing Workflow-knoppie verander promptskryf in 'n begeleide gesprek: TPEE vou u prompt tussen 'n Pre-Prompt en 'n Post-Prompt, u plak die bondel in enige LLM-klets, en die model help u om die prompt voordat u dit ooit gebruik te verbeter. Hoe dit werk ↓
Prominent featurePersona, Instructions, Context, Technical Specs, Format, Audience, Tone, Data, Examples, Graphics, MCP Servers, Verification of Results & Outcome, Agents — thirteen sections, each with a GREEN/YELLOW/RED readiness indicator, rolled into a 0–100 quality score.
187 modelprofiele oor 23 verskaffers, met pryse, konteksvensters en API-karakterlimiete — sodat die prompt wat u skryf by die model pas wat u werklik sal laat loop.
Formateer een keer, voer enige heen uit: 59 IDE-profiele insluitend Cursor, VS Code-variante, Claude Code, Kiro en Windsurf.
'n Plaaslike promptbiblioteek met weergawegeskiedenis en outomatiese rugsteun hou elke konsep veilig op u masjien.
PRD Innovator omskep ruwe idees in gestruktureerde vereistes.
Claude Team Designer en die Team Management-suite organiseer multi-agent-werk.
94 lesse en 282 vasvra-vrae, ingebou. TPEE hou nie net u prompts nie — dit leer die kunsvlyt.
'n Katalogus van ontwikkelingsborde met foto's, vir prompt-ingenieurs wat ook bisse stoot.
Hoëkontras-, kleurblindheid-ondersteunings- en laevisie-tema's maak die redigeerder bruikbaar vir almal in die span.
TPEE loop vanaf u USB-stokkie, sodat u oral kan leer waar u gaan: steek die USB-stokkie in enige Windows-versoenbare rekenaar, dubbelklik op die TPEE.exe-lêer daarop (geen installasie nodig nie) en gaan voort om op die pad te leer. U leervordering word op die USB-stokkie gehou — niks word geïnstalleer op die rekenaar waarin u dit ingesteek het nie.
Prominent featureMoenie net 'n prompt skryf nie — voer eers 'n gesprek met die LLM oor dit. Een knoppie in die boonste paneel lei u deur vyf stappe, en alles gebeur met plaaslike lêers en u knipbord. TPEE kontak nooit 'n LLM nie; u dryf die gesprek.
Pre-Prompt + Your Prompt + Post-Prompt → clipboard → LLM chat → TPEE_Pmt_0001_Enhanced.txt100% plaaslik: merkerslyne raam u prompt soos skeiers in 'n seriële protokol, begeleidingslêers woon langs u prompt, en die enigste vervoer is u knipbord. Geen netwerk nie, geen rekening nie, geen middelman nie.
PRD Innovator
The PRD Innovator's second family of one-click starts asks what kind of office is doing the work, not what kind of software you are building. thirty-seven sectors of activity, one hundred and thirty-nine offices, and every office opens a PRD that is already filled in with its daily requirements - then names the number it lives by, when to stop and hand back to a person, what the assistant must never do, what must happen at month end, where the office will be in three to five years and what the assistant must do first thing each morning - nineteen smart blocks per office. The whole family, every sector and every office card, is on its own page so this page stays quick to read.
Gebou vir individue, studente, werksoekers en spanne.
Die volledige redigeerder, telling en IDE-uitvoer op u eie masjien — geen rekening nodig om te skryf nie.
Volledige toep, 4 maande se opdaterings.
USD $49 · one-timeVolledige toep, 4 maande se opdaterings.
USD $49 · one-timeTeam Management (gedeelde templates, taaktoewysing, span-canvasse) is in die toep ingebou. Die spanplan is nog nie te koop nie — sien pryse vir huidige planne.
'n Ontwikkelingsbord-katalogus met foto's, vir ingenieurs wat ook bisse stoot.
94 lesse en 282 vasvra-vrae, ingebou. TPEE hou nie net u prompts nie — dit leer die kunsvlyt.
91 lesse · 240 vasvra-vrae · by elke plan ingesluit
Every plan is the full app. These are the numbers in the build you download today.
Offline by design: no account, no telemetry, and no call home beyond the release check and the feedback form you choose to use. One-time purchase, 14-day refund, Toptronic® Lifetime Warranty.
TPEE is the productivity tool of choice for all AI work, and especially for people who keep at it. Here is why, in plain terms.
One-time purchase, 14-day refund, Toptronic® Lifetime Warranty. Windows 10 and 11. Built for people who use AI every day, and for the long term.
Code-signed releases are published every two weeks. Information about builds we have not yet signed is published for reference, because it is useful to see what is coming.
What you are entitled to under the maintenance plan is the code-signed release, and it arrives on that schedule — not every day.
Code-signed is what you download. Nothing unsigned is ever offered for sale or for download.
The full editor, at no cost, and no credit card. What the trial does not include is new signed releases, priority release access, a refund window or the Lifetime Warranty — and when the 14 days end the editor keeps working: it simply stops receiving new builds, and nothing is switched off. Your Licence / order key comes by email, and the app verifies it under Help > Your Details.
No card is taken for the trial and nothing is charged when it ends. Buying any plan later is recognised by the same email, so the app picks your updates up on its next check — nothing to re-install, and your work is untouched.
Start on the 14-day free trial if you like — it is the same full editor, free and with no card. Every plan is the same full app; what changes is how long you receive updates, and the licence you buy.
| Plan | Free trial | Student | Starter | Professional Recommended |
|---|---|---|---|---|
| Price | Free — no card | USD $49 one-time | USD $99 one-time | USD $299 one-time |
| How long you have it | 14 days | Yours to keep | Yours to keep | Yours to keep |
| The app | Full editor | Full editor | Full editor | Full editor |
| Updates included | None | 4 months | 6 months | 12 months |
| Priority release access | — | — | — | Yes |
| Commercial use | — | — | Yes | Yes |
| Refund | — | 14 days | 14 days | 14 days |
| Lifetime Warranty | — | Yes | Yes | Yes |
Licence terms and the MSI installer are listed on each plan card below. The app keeps working after the updates window ends — the window is how long you keep receiving new signed releases.
Eenmalige aankoop. Opdaterings is by elke plan ingesluit — geen intekennings nie.
Prices are in US dollars, and Stripe charges the USD amount. The figure under each plan is an approximate local-currency equivalent for — your own bank converts it, at its rate.What happens after you pay: every plan is a one-time purchase — USD $49, $99 or $299 — the app keeps working forever, and every plan carries a 14-day refund, no questions asked.
USD $49 eenmalig
Approx. local equivalent: — you are charged USD $49 by Stripe.
Buy it now · USD $49 once, no approval step, no subscription
USD $99 eenmalig
Approx. local equivalent: — you are charged USD $99 by Stripe.
One-time USD $99 · 6 months of updates · the app keeps working forever after
USD $299 eenmalig
Approx. local equivalent: — you are charged USD $299 by Stripe.
One-time USD $299 · 12 months of updates · 14-day refund, no questions asked
USD $299 eenmalig
Approx. local equivalent: — you are charged USD $299 by Stripe.
One-time USD $299 · delivered by email to the recipient · 12 months of updates
Not sure which one is you? Find your line:
The plans do not differ in the app. Every plan is the full app — what changes is how long updates continue after you buy (4, 6 or 12 months of updates) and how many people may use one licence (1 user on Starter, 1 commercial user on Professional). When the update window ends the app keeps working; you simply stop receiving new builds.
Already hold a licence? Extend your updates with a maintenance plan — or see what a licence includes.
There is a 14-day free trial — the full editor, no card. A trial copy carries no updates and no Lifetime Warranty; the paid plans carry both, and every paid 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 $99 (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. The refund is paid through Stripe minus what the refund costs us: a flat fee of 15% of the amount plus USD 5, together with administrative, accounting, financial, exchange-rate, legal and other processing fees charged to us by your purchase and your refund instruction. The full wording is on the terms of purchase page. 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.
Any defect of the features of the product purchased from us, and during the maintenance period, but additionally, any feature of the product purchased and during the maintenance period, which has a defect when running on your hardware, we warranty we will make it work to satisfaction during the lifetime of the product. For example, if you purchased a TPEE Pro with 12 months of maintenance, the initial product and all its subsequent releases during those months of maintenance are covered, and we warrant that we will ensure the product purchased and the releases covered during the maintenance, works as expected on your hardware during the LifeTime of the product.
Use the feedback form on this page, or the feedback form in the app (Help > Send Feedback), and select the Warranty Claim category. Explain what is not correct and how to reproduce it, then send your warranty claim.
Every licence includes a window of updates: 4 months on Student, 6 on Starter and 12 on Professional. When that window ends the app keeps working exactly as it does today — what stops is the arrival of new signed releases. A maintenance plan extends the window, at the price that belongs to the licence you already hold. Nothing is re-installed and nothing is re-typed: we match the email address you bought with.
USD $19 one-time
One-time USD $19 · added to the licence you already hold
USD $59 one-time
One-time USD $59 · added to the licence you already hold
USD $99 one-time
One-time USD $99 · added to the licence you already hold
USD $59 one-time
One-time USD $59 · the beta-tester maintenance rate
Maintenance is bought for a licence you already hold. If your updates window has already ended, the new months are added from today — no time is lost, and there is no gap to explain to anyone. If you renew early, the months are added to the end of the window you still have. If the address you pay with is not the address we hold a paid licence for, the payment still completes — we record the order, we email you the same day, and we add the months by hand. You are never charged into silence.
Thank you for your suggestions, inputs and feedback in helping me make and improve the Toptronic® Prompt Engineering Editor, especially from the early alpha and beta builds sent to you. A special thanks to the engineers working at these companies shown here for your continuous feedback and suggestions you emailed me. That shaped TPEE and continues to improve it. You will recognise many of the features that started from your suggestions and feedback. Thank you, and thank you on behalf of all the users. Keep your feedback and suggestions coming; we're building TPEE together.
All product names, logos and brands are the property of their respective owners. They are shown for identification only. No endorsement or affiliation is implied. I wanted to name all the contributors, but for legal reasons I could not name the individuals. You know who you are. Thank you very much.
engineers at these companies also sent feedback on our Toptronic® Assistant.
Reguit antwoorde, geen fynskrif nie.
Ja — die toep maak geen netwerkoproepe tydens looptyd nie. Geen telemetrie nie, geen rekening nodig om prompts te skryf nie. Verifieer met u firewall; ons moedig dit aan. (Die webwerf en die Stripe-betaalproses is natuurlik aanlyn.)
Ja — dit is veilig, en u kan dit self in ’n minuut nagaan. Elke weergawe wat ons verkoop, is met ’n EV-sertifikaat in die naam van Toptronic Ltd onderteken. SmartScreen kan steeds ’n waarskuwing wys die eerste keer wat dit ’n splinternuwe ondertekende installeerder sien, want ’n lêer bou sy reputasie by Windows oor tyd op, nie op die oomblik dat dit onderteken word nie — die waarskuwing sê dus niks oor die lêer nie. Om voort te gaan, klik op ‘More info’ en dan op ‘Run anyway’ — daardie twee knoppies se byskrifte is in die taal waarin u Windows gestel is. Voordat u dit laat loop, bevestig dat die aflaai ons s’n is: die gepubliseerde lêernaam en sy SHA-256 moet ooreenstem, en die sertifikaat moet Toptronic Ltd noem. As die naam, die uitgewer of die hash nie ooreenstem nie, stop en e-pos ons eerder. Stap-vir-stap verifiëring is op ons sekuriteitsbladsy.
Ja — daar is ’n gratis proeftydperk van 14 dae. Dit is die volledige redigeerder, sonder koste en sonder kredietkaart: voer u e-posadres op die tuisblad in en ons stuur vir u ’n aflaaiskakel. Die proeftydperk sluit nie nuwe ondertekende weergawes, prioriteitstoegang tot weergawes, ’n terugbetalingsvenster of die Lewenslange Waarborg in nie, en wanneer die 14 dae verby is, bly die redigeerder werk — dit hou net op om nuwe boue te ontvang. As u enige plan koop, begin u opdaterings, en tpee.app ken reeds u e-posadres, so die toep haal hulle op met sy volgende kontrole: niks om weer te installeer nie. Sien die pryse-afdeling vir die drie betaalde planne.
Each of the 13 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.
59 profiele, insluitend Cursor, VS Code en sy variante, Claude Code, Kiro en Devin Desktop — plus ’n algemene formateerder as u instrument nie gelys is nie.
187 modelprofiele oor 23 verskaffers, met pryse, konteksvensters en API-karakterlimiete. TPEE roep hierdie modelle nie vir u nie — dit help u om prompts te skryf wat by hulle pas.
Albei. Dieselfde toep, dieselfde build: MSI vir 'n normale Windows-installasie, ZIP om van oral af te loop (geen adminregte nodig nie).
Net Windows 10 en 11, vir nou. Dit is 'n inheemse Rust/egui-toep, en ons ondersteun liewer een platform behoorlik as drie swak.
Aanvaarde beta-toetsers kry 30% af op die Professional-plan (kode BETA30) in ruil vir kort maandelikse terugvoer. Besonderhede en aansoek: beta-program.
Vergelyk dit met ’n ChatGPT Plus- of Claude Pro-intekening — sien die syfers op die pryse-bladsy.
TPEE maak geen netwerkoproepe tydens looptyd nie. Geen MCP-verbindings nie, geen analitiek nie, geen huis-toe-oproepe nie. U kan dit met u eie firewall verifieer — ons moedig dit aan.
Receive updates information — enter your details and confirm by email. No spam, unsubscribe any time.
Nuwe TPEE-builds, aflaaiskakels en opdateringsnuus — van updates@tpee.app.
Nuutste kenmerke en die TPEE-nuusbrief — van news@tpee.app.
Koop TPEE Professional as ’n geskenk. Die ontvanger kry die lisensie per e-pos met die boodskap “This is the Gift of the Future” en u naam as die gewer.
Ons het u voornaam, van en e-pos nodig sodat ons u lisensie, u kwitansie en u aflaaiskakel kan stuur. Betaling word veilig deur Stripe verwerk.
The live Toptronic® sites, side by side. Every one of them is built, run and answered by the same small team that answers you here.