برومبتات للمبرمجين: مراجعة الكود، شرح الأخطاء، كتابة الاختبارات والتوثيق. أكثرها يعمل بكتلة الحافظة فتلصق كودك وتحصل على النتيجة مباشرة.
أغلب البرومبتات هنا بالإنجليزية لأنها اللغة الطبيعية للتعامل مع الكود، لكنها تعمل مع أي نموذج ذكاء اصطناعي.
الصق الكود أو رسالة الخطأ للحصول على نتيجة مبنية على كودك الفعلي.
Paste unfamiliar or legacy code and get a plain-language walkthrough, with dead code and possible bugs flagged.
Walk through this {{language}} code line by line and explain what it does, in plain language. Flag anything that looks like dead code, a workaround, or a potential bug.
{{CLIPBOARD}}
Get a secure, optimized Dockerfile tailored to your language and framework, ready to build and run.
Write a production-ready Dockerfile for a {{language}} app using {{framework}}. Use multi-stage builds where useful, minimize image size, and run as a non-root user. Notes: {{focus}}.
{{CLIPBOARD}}
Paste a diff or change summary and get a clean, conventional commit message ready to use.
Write a concise, conventional-commits style git commit message for the following change. Focus: {{focus}}. Include a short body only if the change needs more context than the subject line.
{{CLIPBOARD}}
Describe the flags and arguments your CLI needs and get ready-to-use parser boilerplate with help text.
Generate boilerplate for a {{language}} CLI tool using {{framework}} that accepts: {{focus}}. Include help text and basic input validation.
{{CLIPBOARD}}
Describe the schema change you need and get a migration script with both up and down steps, plus risk notes.
Write a {{language}} database migration that: {{focus}}. Target: {{framework}}. Include both the up and down migration, and note any risk of data loss.
{{CLIPBOARD}}
Paste a component or markup and get accessibility issues flagged with severity and concrete, ready-to-apply fixes.
Review this {{language}} component/markup for accessibility issues (WCAG 2.2), focusing on {{focus}}. List each issue with its severity and a concrete fix.
{{CLIPBOARD}}
Get a clear Big-O breakdown of your code's time and space complexity, with reasoning and a faster alternative if one exists.
Analyze the time and space complexity (Big-O) of this {{language}} code. Explain the reasoning per section and suggest a more efficient approach if one exists.
{{CLIPBOARD}}
Turn a diff or change summary into a clear PR description covering what, why, testing, and reviewer focus areas.
Write a pull request description for this change: {{focus}}. Include a summary, why it's needed, how it was tested, and any risks reviewers should focus on.
{{CLIPBOARD}}
Paste a JSON response and get clean, accurate TypeScript interfaces or types generated from it.
Generate {{language}} type definitions from this JSON sample. Use accurate types (no any), mark optional fields, and name the root type {{focus}}.
{{CLIPBOARD}}
Get a list of named code smells and anti-patterns in your code, each paired with a specific, actionable fix.
Scan this {{language}} code for code smells and anti-patterns (e.g. god objects, magic numbers, deep nesting). For each, name the smell and suggest a specific fix.
{{CLIPBOARD}}
Get a performance-focused review that pinpoints bottlenecks and suggests concrete, trade-off-aware optimizations.
Review this {{language}} code for performance issues, focusing on {{focus}}. Identify bottlenecks, their complexity impact, and suggest concrete optimizations with trade-offs.
{{CLIPBOARD}}
Describe your app's data requirements and get a normalized schema with tables, keys, and index suggestions.
Design a normalized {{language}} database schema for: {{focus}}. Include tables, columns with types, primary/foreign keys, and note any indexes worth adding.
{{CLIPBOARD}}
Get a focused security review flagging injection, auth, and secret-handling risks in a specific piece of code.
Perform a security review of this {{language}} code. Look for injection risks, auth/authorization gaps, unsafe deserialization, and secret handling issues. Framework: {{framework}}.
{{CLIPBOARD}}
Describe the endpoint or flow you need to load test and get a ready-to-run k6 script with thresholds.
Write a k6 load test script in {{language}} for this endpoint/flow: {{focus}}. Include realistic virtual user ramp-up and basic pass/fail thresholds.
{{CLIPBOARD}}
Paste code and get the design pattern it implements explained in plain terms, plus whether it's actually justified.
Identify and explain the design pattern(s) used in this {{language}} code. Describe the problem it solves here, its trade-offs, and whether a simpler approach would work.
{{CLIPBOARD}}
Turn a raw endpoint or handler function into complete, developer-friendly API documentation.
Write clear API documentation for this {{language}} endpoint, including method, path, parameters, request/response examples, and possible error codes. Style: {{framework}}.
{{CLIPBOARD}}
Generate a polished README section, installation, usage, or contributing, tailored to your project.
Write a {{focus}} section for a README.md, for a {{language}} project using {{framework}}. Keep it clear, scannable, and include a code example where relevant.
{{CLIPBOARD}}
Get a cleaner, simpler version of your code with an explanation of every change, without altering behavior.
Refactor the following {{language}} code to improve readability, reduce complexity, and follow {{framework}} best practices. Keep behavior identical and explain each change briefly.
{{CLIPBOARD}}
Generate a ready-to-use GitHub Actions workflow file for testing, building, or deploying your project.
Write a GitHub Actions workflow (.yml) for a {{language}} project using {{framework}} that runs on: {{focus}}. Include caching where it speeds up the build.
{{CLIPBOARD}}
Port a function, class, or script from one language to another while keeping the original logic intact.
Convert the following {{language}} code to {{framework}}, preserving logic and behavior exactly. Note any language-specific idioms or libraries used in the conversion.
{{CLIPBOARD}}
Turn a technical decision into a structured ADR: context, chosen option, alternatives, and consequences.
Write an Architecture Decision Record for the decision: {{focus}}. Include context, the decision, alternatives considered, and consequences. Project context: {{language}}/{{framework}}.
{{CLIPBOARD}}
Describe what data you need in plain English and get a ready-to-run SQL query matched to your schema.
Write a {{language}} SQL query for the following request against this schema: {{focus}}. Explain each clause briefly and flag any assumptions about table or column names.
{{CLIPBOARD}}
Automatically document functions and classes with proper docstrings and helpful inline comments.
Add clear {{language}} docstrings and inline comments to the code below, following the {{framework}} documentation style. Explain purpose, parameters, return values, and any non-obvious logic.
{{CLIPBOARD}}
Scan your code for environment variables and get a documented .env.example file, ready to commit safely.
Generate a .env.example file for a {{language}} project using {{framework}}, based on the environment variables referenced in this code. Add a one-line comment explaining each variable.
{{CLIPBOARD}}
Paste your commit history and get a clean, user-facing changelog entry grouped by type of change.
Write a user-facing changelog entry for version {{focus}}, grouped into Added/Changed/Fixed, based on the following commit messages or diffs.
{{CLIPBOARD}}
Generate a Kubernetes Deployment and Service YAML with resource limits and health checks for your app.
Write a Kubernetes manifest (Deployment + Service) for a {{language}} app using {{framework}}, including resource limits, health checks, and {{focus}}.
{{CLIPBOARD}}
Describe what you need to match and get a working regex with a plain-English breakdown.
Write a regular expression that matches: {{focus}}. Target language/engine: {{language}}. Include a short explanation of each part of the pattern and one example string it matches and one it rejects.
{{CLIPBOARD}}