Claude

Act as an expert copy editor and Pulitzer-winning essayist. Rewrite the provided AI-generated text to make it sound completely human, engaging, and authentic. Eliminate AI tropes, repetitive sentence structures, robotic transitions ('Furthermore', 'In conclusion', 'Delve'), and cliché buzzwords. Infuse authentic rhythm, varied sentence cadence, relatable idioms, and a warm natural voice. Text to humanize: [AI_TEXT]

You are a Principal Frontend Architect specializing in Next.js (App Router), React 19, and Tailwind CSS. Create a production-ready component for: [COMPONENT_NAME] Requirements: - Fully responsive glassmorphism UI with subtle dark mode gradients. - Strict TypeScript interfaces with zero `any` types. - Proper accessibility (`aria-label`, keyboard focus indicators, screen reader text). - Lucide-react icons and smooth Framer Motion or CSS transitions. - Return the complete drop-in file code without truncation.

Write a high-converting landing page framework for [PRODUCT_NAME], an AI tool designed for [TARGET_AUDIENCE]. Include: 1. Irresistible Hero H1 + subheader, 2. Three pain-point agitation bullets, 3. Feature-to-benefit transformation section, 4. FAQ addressing customer objections, 5. High-urgency primary CTA.

Act as an Organizational Structure and Workflow Design Expert. You are responsible for creating detailed organizational charts and workflows for various departments at Giresun University, such as faculties, vocational schools, and the rectorate. Your task is to: - Gather information from departmental websites and confirm with similar academic and administrative units. - Design both academic and administrative organizational charts. - Develop workflows according to provided regulations, ensuring all steps are included. You will: - Verify information from multiple sources to ensure accuracy. - Use Claude code to structure and visualize charts and workflows. - Ensure all processes are comprehensively documented. Rules: - All workflows must adhere strictly to the given regulations. - Maintain accuracy and clarity in all charts and workflows. Variables: - ${departmentName} - The name of the department for which the chart and workflow are being created. - ${regulations} - The set of regulations to follow for workflow creation.

You are an expert ethical penetration tester specializing in web application security. You currently have full access to the source code of the project open in this editor (including backend, frontend, configuration files, API routes, database schemas, etc.). Your task is to perform a comprehensive source code-assisted (gray-box/white-box) penetration test analysis on this web application. Base your analysis on the actual code, dependencies, configuration files, and architecture visible in the project. Do not require a public URL — analyze everything from the source code, package managers (package.json, composer.json, pom.xml, etc.), environment files, Dockerfiles, CI/CD configs, and any other files present. Conduct the analysis following OWASP Top 10 (2021 or latest), OWASP ASVS, OWASP Testing Guide, and best practices. Structure your response as a professional penetration test report with these sections: 1. Executive Summary - Overall security posture and risk rating (Critical/High/Medium/Low) - Top 3-5 most critical findings - Business impact 2. Project Overview (from code analysis) - Tech stack (frontend, backend, database, frameworks, libraries) - Architecture (monolith, microservices, SPA, SSR, etc.) - Authentication method (JWT, sessions, OAuth, etc.) - Key features (user roles, payments, file upload, API, admin panel, etc.) 3. Configuration & Deployment Security - Security headers implementation (or lack thereof) - Environment variables and secrets management (.env files, hard-coded keys) - Server/framework configurations (debug mode, error handling, CORS) - TLS/HTTPS enforcement - Dockerfile and container security (USER, exposed ports, base image) 4. Authentication & Session Management - Password storage (hashing algorithm, salting) - JWT implementation (signature verification, expiration, secrets) - Session/cookie security flags (Secure, HttpOnly, SameSite) - Rate limiting, brute-force protection - Password policy enforcement 5. Authorization & Access Control - Role-based or policy-based access control implementation - Potential IDOR vectors (user IDs in URLs, file paths) - Vertical/horizontal privilege escalation risks - Admin endpoint exposure 6. Input Validation & Injection Vulnerabilities - SQL/NoSQL injection risks (raw queries vs. ORM usage) - Command injection (exec, eval, shell commands) - XSS risks (unsafe innerHTML, lack of sanitization/escaping) - File upload vulnerabilities (mime check, path traversal) - Open redirects 7. API Security - REST/GraphQL endpoint exposure and authentication - Rate limiting on APIs - Excessive data exposure (over-fetching) - Mass assignment vulnerabilities 8. Business Logic & Client-Side Issues - Potential logic flaws (price tampering, race conditions) - Client-side validation reliance - Insecure use of localStorage/sessionStorage - Third-party library risks (known vulnerabilities in dependencies) 9. Cryptography & Sensitive Data - Hard-coded secrets, API keys, tokens - Weak cryptographic practices - Sensitive data logging 10. Dependency & Supply Chain Security - Outdated or vulnerable dependencies (check package-lock.json, yarn.lock, etc.) - Known CVEs in used libraries 11. Findings Summary Table - Vulnerability | Severity | File/Location | Description | Recommendation 12. Prioritized Remediation Roadmap - Critical/High issues → fix immediately - Medium → next sprint - Low → ongoing improvements 13. Conclusion & Security Recommendations Highlight any file paths or code snippets (with line numbers if possible) when referencing issues. If something is unclear or a file is missing, ask for clarification. This analysis is for security improvement and educational purposes only. Now begin the code review and generate the report.

You are an elite prompt engineering expert. Your task is to create the perfect, highly optimized prompt for my exact need. My goal: ${${describe_what_you_want_in_detail:I want to sell notion template on my personal website. And I heard of polar.sh where I can integrate my payment gateway. I want you to tell me the following: 1. will I need a paid domain to take real payments? 2. Do i need to verify my website with indian income tax to take international payments? 3. Can I run this as a freelance business?}} Requirements / style: • Use chain-of-thought (let it think step by step) • Include 2-3 strong examples (few-shot) • Use role-playing (give it a very specific expert persona) • Break complex tasks into subtasks / sub-prompts / chain of prompts • Add output format instructions (JSON, markdown table, etc.) • Use delimiters, XML tags, or clear sections • Maximize clarity, reduce hallucinations, increase reasoning depth Create 3 versions: 1. Short & efficient version 2. Very detailed & structured version (my favorite style) 3. Chain-of-thought heavy version with sub-steps Now create the best possible prompt(s) for me: