Prompt Library
204 Prompts — Alle Kategorien
Matcher — Top-3 aehnliche Prompts
Improver — Prompt verbessern
| Name | Kategorie | Vorschau | Variablen | Rating | Modell | Tags |
|---|---|---|---|---|---|---|
| Codex Architecture Review | Analysis | Du bist ein Senior Systems Architect. Analysiere diese Codebase-Struktur: {{interface_map}} Bewerte: Coupling/Cohesion, Dependency Direction, API Co | interface_map | ★★★★ ☆ | — | |
| Codex Regex Generator | Code | Erstelle einen {{type}} Ausdruck fuer: {{description}} Gib zurueck: 1. Den Ausdruck 2. Erklaerung jedes Teils 3. 3 Testfaelle (2 Match, 1 No-Match) | type, description | ★★★★ ☆ | — | |
| Codex Performance Profiler | Analysis | Du bist ein Performance-Experte. Analysiere diesen Code: {{code}} 1. Top-3 Bottlenecks mit Erklaerung 2. Konkreter Fix pro Bottleneck 3. Caching/Laz | code | ★★★★ ☆ | — | |
| Codex Compose Hardening | DevOps | Pruefe diese docker-compose.yml auf Security und Best Practices: {{compose}} Checke: Resource Limits, Network Isolation, Volume Permissions, Healthc | compose | ★★★★ ☆ | — | |
| Codex Anomaly Report | System | Analysiere diese System-Metriken auf Anomalien: {{metrics}} Fuer jede Anomalie: Was ist ungewoehnlich, moegliche Ursache, empfohlene Aktion, Dringli | metrics | ★★★★ ☆ | — | |
| Codex Brand Package | Creative | Erstelle ein Brand-Paket fuer {{brand_name}} im Stil {{style}}: 1. 5 Namens-Varianten mit Begruendung 2. Farbpalette (Primary, Secondary, Accent, Bac | brand_name, style | ★★★★ ☆ | — | |
| Agent Discussion: Moderator | Flow | Du bist Moderator einer Diskussion zwischen {{model_a}} und {{model_b}} zum Thema: {{topic}}. Fasse die Argumente beider Seiten zusammen, bewerte Stae | model_a, model_b, topic | ★★★★ ☆ | — | |
| Relay: Task Delegation | Flow | Du erhaeltst eine Aufgabe via Relay-Kanal {{channel}}. Aufgabe: {{task}}. Lese den Kontext der bisherigen Nachrichten und liefere deinen Beitrag. Antw | channel, task | ★★★★ ☆ | — | |
| Code Explanation | Code | Explain the following {{language}} code in plain language for a {{audience}} audience. ```{{language}} {{code}} ``` Structure your explanation: 1. H | language, code, audience | ★★★★ ☆ | claude-3.5-haiku | explain,documentation,learning |
| Migration Plan | Code | Create a step-by-step migration plan for: {{migration_task}} Current state: {{current_state}} Target state: {{target_state}} Include: 1. Pre-migrati | migration_task, current_state, target_state | ★★★★ ☆ | claude-3.7-sonnet | migration,database,planning |
| Terraform Module | DevOps | Write a Terraform module for: {{resource}} Cloud provider: {{provider}} Requirements: - Parameterized with sensible defaults - Include variables.tf, | resource, provider | ★★★★ ☆ | ollama/qwen2.5-coder:7b | terraform,iac,devops,cloud |
| GitHub Actions Workflow | DevOps | Create a GitHub Actions CI/CD workflow for a {{language}} project. Requirements: - Trigger: push to main + PR to main - Steps: lint, test, build, opt | language, deploy_target, matrix_versions | ★★★★ ☆ | ollama/qwen2.5-coder:7b | github-actions,ci-cd,devops |
| Literature Review | Research | Conduct a structured literature review on: {{topic}} Format: ## Overview Brief introduction to the field (3-5 sentences). ## Key Concepts Definition | topic | ★★★★ ☆ | openrouter/qwen3-coder-plus | research,literature,survey |
| Data Analysis Plan | Analysis | Create a data analysis plan for the question: {{question}} Dataset description: {{dataset}} Include: 1. Hypothesis formulation (null + alternative) | question, dataset | ★★★★ ☆ | claude-3.7-sonnet | data-analysis,statistics,eda |
| Technical Blog Post | Text | Write a technical blog post about: {{topic}} Target audience: {{audience}} Desired length: {{length}} Structure: - Hook/problem statement (first 2 s | topic, audience, length | ★★★★ ☆ | claude-3.7-sonnet | blog,writing,technical |
| Email Vorlage Professionell | Text | Schreibe eine professionelle E-Mail fuer den Zweck: {{zweck}} Empfaenger: {{empfaenger}} Kontext: {{kontext}} Gewuenschter Ton: {{ton}} Anforderunge | zweck, empfaenger, kontext, ton | ★★★★ ☆ | claude-3.5-haiku | email,german,business,writing |
| Changelog Generator | Text | Generate a user-friendly changelog for the following git log: ``` {{git_log}} ``` Format as Keep a Changelog (https://keepachangelog.com): ## [{{ver | git_log, version, date | ★★★★ ☆ | claude-3.5-haiku | changelog,release,git |
| Yoga Newsletter DE | Creative | Schreibe einen monatlichen Yoga-Newsletter fuer die Community. Monat: {{monat}} Hauptthema: {{thema}} Aktuelles Angebot: {{angebot}} Veranstaltungen: | monat, thema, angebot, veranstaltungen | ★★★★ ☆ | claude-3.5-haiku | yoga,newsletter,german,creative,email |
| SDXL Portrait Prompt | Pixel | Generate an SDXL-optimized portrait prompt for: {{subject}} Ethnicity/style: {{style}} Lighting: {{lighting}} Background: {{background}} POSITIVE PR | subject, style, lighting, background | ★★★★ ☆ | claude-3.5-haiku | sdxl,portrait,stable-diffusion,pixel |
| ComfyUI Workflow Description | Pixel | Describe a ComfyUI workflow for generating: {{goal}} Model: {{model}} (e.g. FLUX.1-dev, SDXL, SD1.5) LoRA if needed: {{lora}} Special techniques: {{t | goal, model, lora, techniques | ★★★★ ☆ | claude-3.5-haiku | comfyui,workflow,stable-diffusion,pixel |
| Z-Image Style Transfer | Pixel | Create a style transfer prompt for Z-Image / img2img pipeline. Source image description: {{source}} Target style: {{target_style}} Style strength: {{ | source, target_style, strength | ★★★★ ☆ | claude-3.5-haiku | img2img,style-transfer,pixel,z-image |
| Logo Design Brief | Pixel | Create a detailed logo design brief for: {{brand}} Industry: {{industry}} Values: {{values}} Target audience: {{audience}} Include: 1. Visual direct | brand, industry, values, audience | ★★★★ ☆ | claude-3.7-sonnet | logo,design,branding,pixel |
| API Integration Plan | Flow | Create an integration plan for connecting {{service_a}} with {{service_b}}. Use case: {{use_case}} Data direction: {{direction}} (A→B / B→A / bidirec | service_a, service_b, use_case, direction | ★★★★ ☆ | claude-3.7-sonnet | api,integration,flow,automation |
| Sprint Planning | System | Create a sprint plan for the following backlog items. Sprint goal: {{goal}} Team capacity: {{capacity}} story points Sprint duration: {{duration}} we | goal, capacity, duration, backlog | ★★★★ ☆ | claude-3.7-sonnet | agile,sprint,planning,scrum |
| Knowledge Base Article | Text | Write a knowledge base article for: {{topic}} Audience: {{audience}} (technical level: {{level}}) Category: {{category}} Structure: # [Clear, search | topic, audience, level, category, tags, date | ★★★★ ☆ | claude-3.5-haiku | knowledge-base,documentation,writing |
| API Documentation | Text | Generate OpenAPI 3.0 documentation for the following API endpoint. Endpoint: {{method}} {{path}} Purpose: {{purpose}} Request body: {{request_schema} | method, path, purpose, request_schema, response_schema, auth | ★★★★ ☆ | ollama/qwen2.5-coder:7b | api,documentation,openapi,rest |
| Yoga Social Media Post DE | Creative | Erstelle einen Social-Media-Post fuer {{plattform}} zum Thema Yoga. Thema: {{thema}} Anlass: {{anlass}} (z.B. World Yoga Day, Monatsstart) Emoji-Stil | plattform, thema, anlass, emoji_stil, hashtag_anzahl | ★★★★ ☆ | claude-3.5-haiku | social-media,german,yoga,creative |
| n8n workflow tagged project:* with rag-watch | Flow | Create an n8n flow tagged `project:{project_id}` with auto-import to RAG via `n8n-rag-watch.service`. Setup: 1. Author flow JSON in n8n UI (https://n | {'name': 'project_id', 'description': 'from .agent/projects.yaml'}, {'name': 'flow_name', 'description': 'slug'}, {'name': 'trigger', 'description': 'webhook/cron/etc'}, {'name': 'action', 'description': 'what it does'} | ★★★★ ☆ | claude-3.5-haiku | stack-aware,n8n,workflow,rag,inotify |
| Knowledge Governance Board — surface contradiction | Analysis | Investigate a contradiction signal at `/governance/knowledge/` (AP56 board) for `{topic}`. Workflow: 1. Open https://orchestrator.joelduss.xyz/govern | {'name': 'topic', 'description': 'short slug'}, {'name': 'topic_description', 'description': 'long description'} | ★★★★ ☆ | claude-3.7-sonnet | stack-aware,knowledge-governance,ap56,contradictions,ap11 |
| Audit Glug Plugin Manifests | Analysis | Audit all installed Glug plugins by scanning /nvmetank1/projects/glug/plugins/*/manifest.toml. For each plugin: 1. Parse id field — must match patter | — | ★★★★ ☆ | openai/gpt-4.1 | stack-aware,glug,plugin,audit,manifest |