How closetgeekshow/gptpromptexperiments works
Project type and purpose
• From the README (“a collection of prompts I’ve tried for various purposes”) and file tree, this is an open-source “prompt experiments” repository. It is essentially a knowledge-base and interactive demo collection, not a traditional full-stack application. Its primary purpose is to store, organize, and run prompt-engineering experiments (markdown files) and small browser-based demos (the flems subfolder).
File structure
• Top-level directories:
• Approaches – curated prompt workflows (Story→Charts→Code, Story→Tasks→Code, etc.)
• Generic – general prompting recipes (code repair, doc comments, refactor, etc.)
• flems – a mini front-end code sandbox using flems-sfc.js & HTML, hosting live examples
• scratchpad – ad-hoc prompt/testing notes
• Root files: LICENSE, README.md describe the project
• No backend or database; the only “runtime” component is the flems client (JavaScript in browser).
• No build scripts or CI present; mostly static markdown and static HTML/JS.
Extract additional insights from the README
• Emphasis on breaking down prompts into stages (Story→Tasks→Code, etc.)
a. Main components
1) Prompt Repository
– A collection of Markdown files organized under Approaches, Generic, scratchpad
2) Interactive Demo Runner (flems)
– flems-sfc.js + index.html in flems/src loads Single File Components (.flems files)
3) User Environment
– Local Editor (VSCode, etc.) reading/editing markdown & HTML/JS
– Web Browser rendering flems demos
4) Source Control / Host
– GitHub (repo storage, versioning)
b. Relationships & Data Flow
– User edits markdown prompts in local editor → commits to GitHub
– flems HTML/JS reads .flems files → browser renders interactive components
– User interacts with demos in browser → tests prompt outputs live
c. Architectural Patterns
– Static content repository (markdown + static site assets)
– Modular folder structure by purpose (Approaches vs. Generic vs. scratchpad vs. demos)
– Single-page demo runner pattern (flems)
d. Key technologies
– Markdown (prompt definitions)
– flems-sfc.js, HTML, CSS, Vanilla JS (interactive demo)
– Git/GitHub (source control)
Detail
• That flems is the only runtime component.