This repository, named 'AI Short' (ChatGPT-Shortcut), is a production-grade Docusaurus-based web application that serves as a curated, multilingual library of over 5,000 AI prompts for ChatGPT, Gemini, Claude, and similar tools. The application provides a searchable, tag-filterable interface with prompt cards, copy-with-tracking, and detailed pages featuring FAQs and related prompts. It supports 18 languages via separate Docusaurus builds and includes a browser extension (Chrome/Firefox) for quick access. Beyond the static prompt data, it offers a community platform with user accounts (OAuth), favorites, custom prompt creation, voting, comments, and a level system. The frontend is a React 19 SPA with Ant Design 6, featuring client-side caching, optimistic UI updates, and lazy-loaded components. The backend (Strapi) is not open-sourced but the API contracts are fully defined. Deployment options include standard (shared backend), offline (localStorage), and full self-hosted setups. The code demonstrates strong engineering practices: clean component decomposition, custom hooks for data management, a two-tier cache system with ETag support, and thoughtful accessibility patterns. The prompt data itself is static JSON, generated from a master file via a Python pipeline, and includes rich metadata for SEO and cross-referencing.
This repository is a full-stack Next.js application that serves as the world's largest open-source prompt library for AI. It provides a platform for users to create, share, discover, and manage prompts for various AI models (ChatGPT, Claude, Gemini, etc.). The core functionality includes CRUD operations for prompts with types (text, image, video, audio, skill, taste), voting, commenting, versioning, change requests, collections, and moderation tools. It features AI-powered capabilities such as semantic search via OpenAI embeddings, prompt improvement, translation, quality checking, and media generation through plugin-based providers (Fal.ai, Wiro.ai). The application supports multi-tenancy for self-hosting with configurable branding, authentication plugins (OAuth, OIDC, GitHub, Apple, Google), and storage backends (S3, DO Spaces). Beyond the web app, it includes a CLI tool (packages/prompts.chat) for browsing and running prompts locally, a Raycast extension for quick access, and an MCP server for integration with AI coding assistants. Additionally, it bundles an interactive educational book on prompt engineering (28+ chapters) and a gamified kids learning section, both fully localized into 17 languages. The codebase is well-structured with a plugin registry pattern, configuration-driven design, and extensive use of modern Next.js patterns (App Router, server components, streaming).
GistPad MCP is a Model Context Protocol (MCP) server that provides a comprehensive interface for managing GitHub Gists through AI assistants like GitHub Copilot and Claude Desktop. It exposes tools for CRUD operations on gists, file management within gists, comments, daily notes, archiving, starring, and reusable prompts. The server runs over stdio and uses the GitHub REST API via a custom typed fetch client. It features a caching layer with hourly refresh, resource subscriptions, and change notifications. The codebase is written in modern TypeScript (ES2024, Node.js 22+) with strict type safety, comprehensive tests for the file editing tool, and a clean modular architecture separating concerns into tools, server, store, and utilities. It demonstrates strong engineering practices including abstract base classes for stores, automatic tool annotation derivation, and careful error handling.
Promptify is a Python library for performing NLP tasks using large language models (LLMs) with structured, type-safe outputs. It provides a scikit-learn-like interface where users instantiate task classes (e.g., NER, Classify, QA, Summarize) and call them with plain text. The library uses LiteLLM as a universal backend to support 100+ providers (OpenAI, Anthropic, Ollama, etc.), Pydantic v2 for output schemas, Jinja2 for prompt templates, and tenacity for retries. Architecture follows a clean separation: Task classes (promptify/tasks) build prompts via PromptBuilder, send them via LLMEngine (which wraps LiteLLM), and parse responses via a safe Parser that never uses eval(). The package also includes a built-in evaluation framework (promptify/eval) with metrics for precision, recall, F1, accuracy, exact match, and ROUGE, plus dataset loading utilities. The code is well-structured, typed, and includes comprehensive tests. The primary artifact is the "promptify" Python package, installable via pip. The repository is not a data research project; it is a software library for developers.
This is a Claude Code plugin and resource library, not a deployable application or data pipeline: 27 slash commands, 9+ autonomous skills, 3 auditor subagents, and extensive prompt-engineering documentation that extend the Claude Code CLI. In production, the system functions as configuration-as-code content consumed by the Claude Code runtime — teaching the assistant how to create executable plans (PLAN.md is the prompt itself), chain meta-prompts, build MCP servers, manage subagent orchestration, run autonomous coding loops (the 'Ralph' technique), and apply iOS/macOS development expertise. The only real executable code is a handful of self-contained scripts: a TypeScript CLI for The Pirate Bay API, Python/TypeScript MCP server templates, project scaffolding shell scripts, and autonomous loop iteration scripts. The dominant architectural pattern is the 'router skill': a SKILL.md entry point with essential principles, an intake gate, a routing table, and progressive disclosure into workflows, references, templates, and scripts — implemented consistently across all skills with pure XML prompt structure and checkpoint-based plan execution. Despite being classified as an application (there is no data-research character — no notebooks, datasets, or pipelines), its substance is largely authored content rather than software. The craft is strong: consistent XML schemas across files, a genuine QA layer (skill-auditor agents), secret hygiene practices, and a well-developed checkpoint/auth-gate protocol for safe automation. However, the repo carries real drift risks: duplicated reference files (research-pitfalls.md, cli-observability.md are copied across skills), dangling references to not-yet-created files, tight coupling to Claude Code's evolving plugin API, version-specific Apple platform guidance that will age, and the included The Pirate Bay skill which depends on a fragile third-party API and presents a content-policy concern. An engineer seeking to reuse this should extract the self-contained templates and scripts (MCP server scaffolding, loop automation) and treat the reference material as opinionated prompt guidance rather than canonical documentation.
This repository is a curated collection of prompt examples for GPT models within the Microsoft Power Platform ecosystem. It contains over 100 prompts organized by product area: AI Builder, Copilot Studio, Power Apps, Power Automate, and Power Pages. Each prompt is stored as a markdown file with accompanying metadata (sample.json) and a README describing its purpose, usage, and authors. The repository does not contain any executable code, libraries, or runtime components; it is purely a reference library of natural language prompts intended to be copied and pasted into Power Platform tools. The prompts range from simple text generation (e.g., anagram creator, blog idea generator) to complex multi-modal analyses (e.g., construction site OSHA compliance, expense processor with receipt images). The repository is well-structured with consistent naming conventions, localization support, and a GitHub Actions workflow to validate sample metadata. While not a software application itself, it serves as a valuable resource for Power Platform developers and citizen integrators looking to leverage GPT capabilities.
This repository is primarily a large collection of GPT prompt templates (markdown files) designed for use with AI chat platforms like FlowGPT or gptcall.net. Each prompt file defines a specific role or task for the AI, such as a resume editor, coding tutor, fitness planner, or creative writing assistant. The repository also includes an Android application (OpenClaw and Codex) referenced in the README, along with Node.js scripts (update.mjs, db.mjs) for managing the prompt data. The prompts are structured with placeholders for user input and often request specific output formats, enabling users to import them into chat interfaces to obtain specialized AI behavior without crafting prompts from scratch. While the prompt library is extensive, it contains significant duplication, minimal-effort entries, and some policy-risking content (e.g., jailbreaks, NSFW role-play), which affects overall quality and reuse potential.
CL4R1T4S is a repository that functions as a curated archive of extracted system prompts, tool definitions, and behavioral instructions from major AI models and agent platforms. It contains no executable code, data pipelines, or analytical scripts. The entire repository consists of flat text and markdown files organized by vendor (e.g., OPENAI, ANTHROPIC, XAI, CURSOR, REPLIT), each containing what are claimed to be verbatim system prompts for models like ChatGPT, Claude, Grok, Gemini, and various coding agents like Devin, Cursor, Windsurf, and Replit. The repository's stated purpose is transparency — making visible the hidden instructions that shape AI behavior. However, from a data engineering or software architecture perspective, there is no data lineage to trace, no transformation logic to evaluate, and no code to assess for craftsmanship. The files are static documents with no programmatic relationship between them. There are no tests, no dependency manifests, no environment definitions, and no data processing logic of any kind. The collection has some research value as a comparative corpus for prompt analysis, but it is entirely unstructured as data. There are no schemas, no metadata standards, no versioning discipline, and no way to verify the authenticity or currency of the extracted prompts. The README itself contains signs of prompt injection attempts and unprofessional editorializing that undermine the project's credibility as a serious transparency effort. There are no reusable components, no engineering patterns, and no data operations present.