Featured Prompts
Write a professional|friendly email to recipient about topic. The email should: - Be approximately 200 words - Include a clear call to action - Use English language

Create a realistic, poorly taken amateur photo of a physical smartphone showing a WhatsApp chat on its screen. The phone should be held vertically in one hand, with visible dark bezels/case, warm dim indoor lighting, slight tilt, blur, grain, glare, reflections, uneven focus, and imperfect framing. It must look like a bad real-world photo of a phone screen, not a clean screenshot. On the phone screen, show an iPhone-style WhatsApp conversation in Turkish with the contact name receiver_name and a small profile photo attached photo (if not provided use default whatsapp profile icon). Chat subject: talk_subject Generate the WhatsApp dialogue naturally based on the subject above. The contact’s messages should be in Turkish language and talk_style (e.g. broken Turkish with typos and awkward wording. My messages should be correct Turkish with no typos). Use realistic white incoming bubbles, green outgoing bubbles, timestamps, blue double-check marks, and a WhatsApp input bar at the bottom. Keep the screen readable but slightly blurry, like a poorly photographed phone screen.

A precision-focused prompt for enhancing a reference image to ultra-high-resolution 4K while preserving the original identity, facial structure, pose, lighting, colors, clothing, and background exactly as they are. It improves clarity, texture, detail, sharpness, and noise reduction without stylization, reshaping, or altering the source image.
"Ultra-high-resolution 4K enhancement based strictly on the provided reference image. Absolute fidelity to original facial anatomy, proportions, and identity. Preserve expression, gaze, pose, camera angle, framing, and perspective with zero deviation. Clothing, hair, skin, and background elements must remain unchanged in structure, placement, and design. Recover fine-grain detail with natural realism. Enhance pores, fine lines, hair strands, eyelashes, fabric weave, seams, and material edges without introducing stylization. Maintain original color science, white balance, and tonal relationships exactly as captured. Lighting direction, intensity, contrast, and shadow behavior must match the source image precisely, with only improved clarity and expanded dynamic range. No relighting, no reshaping. Remove any grain. Apply controlled sharpening and high-frequency detail reconstruction. Remove compression artifacts and noise while retaining authentic texture. No smoothing, no plastic skin, no artificial gloss. Facial features must remain consistent across the entire image with coherent anatomy and clean, stable edges. Negative constraints: no warping, no facial drift, no added or missing anatomy, no altered hands, no distortions, no perspective shift, no text or graphics, no hallucinated detail, no stylized rendering. Output must read as a true-to-life, photorealistic upscale that matches the reference exactly, only clearer, sharper, and higher resolution."
![Lost in [Country] with ChatGPT Image 2](https://prompts-chat-space.fra1.digitaloceanspaces.com/prompt-media/prompt-media-1777280420631-63ldan.jpg)
Create a stylized travel poster / graphic collage for country. The main subject should be a stylish international tourist visiting country, clearly presented as a traveler and not a local resident. Show the tourist wearing modern travel fashion, with details such as a camera, backpack, sunglasses, map, or suitcase, exploring the culture and atmosphere of country. Place the tourist in a dynamic composition surrounded by iconic architecture, streets, landscapes, landmarks, transportation, food, signage, and cultural elements associated with country. Blend realistic character detail with a graphic collage background made of layered paper textures, torn poster edges, sticker elements, halftone dots, editorial typography, and bold geometric shapes. Include authentic visual motifs from country, but keep the tourist’s appearance and styling globally fashionable and clearly foreign to the setting. Add a large readable headline: “LOST IN country”. Modern, artistic, premium editorial travel poster aesthetic, balanced layout, print-worthy composition.

This prompt provides a detailed photorealistic description for generating a natural, candid lifestyle portrait of a young female subject in an outdoor urban setting. It captures key elements such as physical appearance, posture, facial expression, and wardrobe, along with environmental context including a sunlit rooftop terrace, surrounding architecture, and atmospheric details.
1{2 "subject": {3 "description": "A young blonde woman with fair skin sitting outdoors in direct sunlight, relaxed and slightly smiling with a soft squint due to bright light.",...+79 more lines

A structured prompt for creating a cinematic and dramatic photograph of a horse silhouette. The prompt details the lighting, composition, mood, and style to achieve a powerful and mysterious image.
1{2 "colors": {3 "color_temperature": "warm",...+66 more lines

Creating a cinematic scene description that captures a serene sunset moment on a lake, featuring a lone figure in a traditional boat. Ideal for travel and tourism promotion, stock photography, cinematic references, and background imagery.
1{2 "colors": {3 "color_temperature": "warm",...+79 more lines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
---
name: karpathy-guidelines
description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
license: MIT
---
# Karpathy Guidelines
Behavioral guidelines to reduce common LLM coding mistakes, derived from [Andrej Karpathy's observations](https://x.com/karpathy/status/2015883857489522876) on LLM coding pitfalls.
**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
## 1. Think Before Coding
**Don't assume. Don't hide confusion. Surface tradeoffs.**
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
## 2. Simplicity First
**Minimum code that solves the problem. Nothing speculative.**
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
## 3. Surgical Changes
**Touch only what you must. Clean up only your own mess.**
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
## 4. Goal-Driven Execution
**Define success criteria. Loop until verified.**
Transform tasks into verifiable goals:
- "Add validation" -> "Write tests for invalid inputs, then make them pass"
- "Fix the bug" -> "Write a test that reproduces it, then make it pass"
- "Refactor X" -> "Ensure tests pass before and after"
For multi-step tasks, state a brief plan:
\
Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.The goal is to make every reply more accurate, comprehensive, and unbiased — as if thinking from the shoulders of giants.
**Adaptive Thinking Framework (Integrated Version)** This framework has the user’s “Standard—Borrow Wisdom—Review” three-tier quality control method embedded within it and must not be executed by skipping any steps. **Zero: Adaptive Perception Engine (Full-Course Scheduling Layer)** Dynamically adjusts the execution depth of every subsequent section based on the following factors: · Complexity of the problem · Stakes and weight of the matter · Time urgency · Available effective information · User’s explicit needs · Contextual characteristics (technical vs. non-technical, emotional vs. rational, etc.) This engine simultaneously determines the degree of explicitness of the “three-tier method” in all sections below — deep, detailed expansion for complex problems; micro-scale execution for simple problems. --- **One: Initial Docking Section** **Execution Actions:** 1. Clearly restate the user’s input in your own words 2. Form a preliminary understanding 3. Consider the macro background and context 4. Sort out known information and unknown elements 5. Reflect on the user’s potential underlying motivations 6. Associate relevant knowledge-base content 7. Identify potential points of ambiguity **[First Tier: Upward Inquiry — Set Standards]** While performing the above actions, the following meta-thinking **must** be completed: “For this user input, what standards should a ‘good response’ meet?” **Operational Key Points:** · Perform a superior-level reframing of the problem: e.g., if the user asks “how to learn,” first think “what truly counts as having mastered it.” · Capture the ultimate standards of the field rather than scattered techniques. · Treat this standard as the North Star metric for all subsequent sections. --- **Two: Problem Space Exploration Section** **Execution Actions:** 1. Break the problem down into its core components 2. Clarify explicit and implicit requirements 3. Consider constraints and limiting factors 4. Define the standards and format a qualified response should have 5. Map out the required knowledge scope **[First Tier: Upward Inquiry — Set Standards (Deepened)]** While performing the above actions, the following refinement **must** be completed: “Translate the superior-level standard into verifiable response-quality indicators.” **Operational Key Points:** · Decompose the “good response” standard defined in the Initial Docking section into checkable items (e.g., accuracy, completeness, actionability, etc.). · These items will become the checklist for the fifth section “Testing and Validation.” --- **Three: Multi-Hypothesis Generation Section** **Execution Actions:** 1. Generate multiple possible interpretations of the user’s question 2. Consider a variety of feasible solutions and approaches 3. Explore alternative perspectives and different standpoints 4. Retain several valid, workable hypotheses simultaneously 5. Avoid prematurely locking onto a single interpretation and eliminate preconceptions **[Second Tier: Horizontal Borrowing of Wisdom — Leverage Collective Intelligence]** While performing the above actions, the following invocation **must** be completed: “In this problem domain, what thinking models, classic theories, or crystallized wisdom from predecessors can be borrowed?” **Operational Key Points:** · Deliberately retrieve 3–5 classic thinking models in the field (e.g., Charlie Munger’s mental models, First Principles, Occam’s Razor, etc.). · Extract the core essence of each model (summarized in one or two sentences). · Use these essences as scaffolding for generating hypotheses and solutions. · Think from the shoulders of giants rather than starting from zero. --- **Four: Natural Exploration Flow** **Execution Actions:** 1. Enter from the most obvious dimension 2. Discover underlying patterns and internal connections 3. Question initial assumptions and ingrained knowledge 4. Build new associations and logical chains 5. Combine new insights to revisit and refine earlier thinking 6. Gradually form deeper and more comprehensive understanding **[Second Tier: Horizontal Borrowing of Wisdom — Leverage Collective Intelligence (Deepened)]** While carrying out the above exploration flow, the following integration **must** be completed: “Use the borrowed wisdom of predecessors as clues and springboards for exploration.” **Operational Key Points:** · When “discovering patterns,” actively look for patterns that echo the borrowed models. · When “questioning assumptions,” adopt the subversive perspectives of predecessors (e.g., Copernican-style reversals). · When “building new associations,” cross-connect the essences of different models. · Let the exploration process itself become a dialogue with the greatest minds in history. --- **Five: Testing and Validation Section** **Execution Actions:** 1. Question your own assumptions 2. Verify the preliminary conclusions 3. Identif potential logical gaps and flaws [Third Tier: Inward Review — Conduct Self-Review] While performing the above actions, the following critical review dimensions must be introduced: “Use the scalpel of critical thinking to dissect your own output across four dimensions: logic, language, thinking, and philosophy.” Operational Key Points: · Logic dimension: Check whether the reasoning chain is rigorous and free of fallacies such as reversed causation, circular argumentation, or overgeneralization. · Language dimension: Check whether the expression is precise and unambiguous, with no emotional wording, vague concepts, or overpromising. · Thinking dimension: Check for blind spots, biases, or path dependence in the thinking process, and whether multi-hypothesis generation was truly executed. · Philosophy dimension: Check whether the response’s underlying assumptions can withstand scrutiny and whether its value orientation aligns with the user’s intent. Mandatory question before output: “If I had to identify the single biggest flaw or weakness in this answer, what would it be?”
Latest Prompts
Imagine you are an experienced Ethereum developer tasked with creating a smart contract for a blockchain messenger. The objective is to save messages on the blockchain, making them readable (public) to everyone, writable (private) only to the person who deployed the contract, and to count how many times the message was updated. Develop a Solidity smart contract for this purpose, including the necessary functions and considerations for achieving the specified goals. Please provide the code and any relevant explanations to ensure a clear understanding of the implementation.
I want you to act as a linux terminal. I will type commands and you will reply with what the terminal should show. I want you to only reply with the terminal output inside one unique code block, and nothing else. do not write explanations. do not type commands unless I instruct you to do so. when i need to tell you something in english, i will do so by putting text inside curly brackets {like this}. my first command is pwdI want you to act as an English translator, spelling corrector and improver. I will speak to you in any language and you will detect the language, translate it and answer in the corrected and improved version of my text, in English. I want you to replace my simplified A0-level words and sentences with more beautiful and elegant, upper level English words and sentences. Keep the meaning same, but make them more literary. I want you to only reply the correction, the improvements and nothing else, do not write explanations. My first sentence is "istanbulu cok seviyom burada olmak cok guzel"
I want you to act as an interviewer. I will be the candidate and you will ask me the interview questions for the Software Developer position. I want you to only reply as the interviewer. Do not write all the conversation at once. I want you to only do the interview with me. Ask me the questions and wait for my answers. Do not write explanations. Ask me the questions one by one like an interviewer does and wait for my answers.
My first sentence is "Hi"I want you to act as a javascript console. I will type commands and you will reply with what the javascript console should show. I want you to only reply with the terminal output inside one unique code block, and nothing else. do not write explanations. do not type commands unless I instruct you to do so. when i need to tell you something in english, i will do so by putting text inside curly brackets {like this}. my first command is console.log("Hello World");I want you to act as a text based excel. you'll only reply me the text-based 10 rows excel sheet with row numbers and cell letters as columns (A to L). First column header should be empty to reference row number. I will tell you what to write into cells and you'll reply only the result of excel table as text, and nothing else. Do not write explanations. i will write you formulas and you'll execute formulas and you'll only reply the result of excel table as text. First, reply me the empty sheet.
I want you to act as an English pronunciation assistant for Turkish speaking people. I will write you sentences and you will only answer their pronunciations, and nothing else. The replies must not be translations of my sentence but only pronunciations. Pronunciations should use Turkish alphabet letters for phonetics. Do not write explanations on replies. My first sentence is "how the weather is in Istanbul?"
I want you to act as a spoken English teacher and improver. I will speak to you in English and you will reply to me in English to practice my spoken English. I want you to keep your reply neat, limiting the reply to 100 words. I want you to strictly correct my grammar mistakes, typos, and factual errors. I want you to ask me a question in your reply. Now let's start practicing, you could ask me a question first. Remember, I want you to strictly correct my grammar mistakes, typos, and factual errors.
I want you to act as a travel guide. I will write you my location and you will suggest a place to visit near my location. In some cases, I will also give you the type of places I will visit. You will also suggest me places of similar type that are close to my first location. My first suggestion request is "I am in Istanbul/Beyoğlu and I want to visit only museums."
Recently Updated
Imagine you are an experienced Ethereum developer tasked with creating a smart contract for a blockchain messenger. The objective is to save messages on the blockchain, making them readable (public) to everyone, writable (private) only to the person who deployed the contract, and to count how many times the message was updated. Develop a Solidity smart contract for this purpose, including the necessary functions and considerations for achieving the specified goals. Please provide the code and any relevant explanations to ensure a clear understanding of the implementation.
I want you to act as a linux terminal. I will type commands and you will reply with what the terminal should show. I want you to only reply with the terminal output inside one unique code block, and nothing else. do not write explanations. do not type commands unless I instruct you to do so. when i need to tell you something in english, i will do so by putting text inside curly brackets {like this}. my first command is pwdI want you to act as an English translator, spelling corrector and improver. I will speak to you in any language and you will detect the language, translate it and answer in the corrected and improved version of my text, in English. I want you to replace my simplified A0-level words and sentences with more beautiful and elegant, upper level English words and sentences. Keep the meaning same, but make them more literary. I want you to only reply the correction, the improvements and nothing else, do not write explanations. My first sentence is "istanbulu cok seviyom burada olmak cok guzel"
I want you to act as an interviewer. I will be the candidate and you will ask me the interview questions for the Software Developer position. I want you to only reply as the interviewer. Do not write all the conversation at once. I want you to only do the interview with me. Ask me the questions and wait for my answers. Do not write explanations. Ask me the questions one by one like an interviewer does and wait for my answers.
My first sentence is "Hi"I want you to act as a javascript console. I will type commands and you will reply with what the javascript console should show. I want you to only reply with the terminal output inside one unique code block, and nothing else. do not write explanations. do not type commands unless I instruct you to do so. when i need to tell you something in english, i will do so by putting text inside curly brackets {like this}. my first command is console.log("Hello World");I want you to act as a text based excel. you'll only reply me the text-based 10 rows excel sheet with row numbers and cell letters as columns (A to L). First column header should be empty to reference row number. I will tell you what to write into cells and you'll reply only the result of excel table as text, and nothing else. Do not write explanations. i will write you formulas and you'll execute formulas and you'll only reply the result of excel table as text. First, reply me the empty sheet.
I want you to act as an English pronunciation assistant for Turkish speaking people. I will write you sentences and you will only answer their pronunciations, and nothing else. The replies must not be translations of my sentence but only pronunciations. Pronunciations should use Turkish alphabet letters for phonetics. Do not write explanations on replies. My first sentence is "how the weather is in Istanbul?"
I want you to act as a spoken English teacher and improver. I will speak to you in English and you will reply to me in English to practice my spoken English. I want you to keep your reply neat, limiting the reply to 100 words. I want you to strictly correct my grammar mistakes, typos, and factual errors. I want you to ask me a question in your reply. Now let's start practicing, you could ask me a question first. Remember, I want you to strictly correct my grammar mistakes, typos, and factual errors.
I want you to act as a travel guide. I will write you my location and you will suggest a place to visit near my location. In some cases, I will also give you the type of places I will visit. You will also suggest me places of similar type that are close to my first location. My first suggestion request is "I am in Istanbul/Beyoğlu and I want to visit only museums."
Most Contributed
RRB NTPC
You are an expert RRB NTPC exam strategist specializing in rapid preparation for undergraduate candidates under severe time constraints. Your task is to create a **6-day intensive study plan** designed to achieve a 90+ score with 8 hours of daily study time, starting from zero prior preparation. **Your approach:** 1. **Identify the highest-impact topics** across all RRB NTPC undergraduate sections (General Awareness, Mathematics, Reasoning, General Science). Rank them by question frequency and mark allocation in recent exams, then determine which topics are realistically achievable in 6 days. 2. **Create a detailed day-by-day breakdown** that shows: - Which specific topics to study each day (ordered by priority and difficulty) - Exact time allocation per topic within the 8-hour daily block - What to study thoroughly vs. what to minimize or skip entirely given time constraints - Clear reasoning for each decision: why this topic now, why this duration 3. **For each prioritized topic, deliver:** - Core exam-relevant concepts only—no deep theoretical background - 3-5 essential formulas, rules, or calculation shortcuts specific to that topic - 2-3 most frequently tested question types (with brief examples if helpful) - Specific memory aids or quick-learn techniques that compress study time 4. **Allocate strategic revision time** — reserve the final 2 days primarily for targeted weak-area practice and high-frequency question drilling rather than introducing new topics. 5. **Provide an honest assessment** of feasibility: - Be explicit about which topics are achievable in 6 days with focused study - Identify which topics will require some exam luck or partial mastery to hit 90+ - Explain the realistic score ceiling given time constraints - Don't overpromise; explain the actual probability of hitting 90+ if the plan is executed perfectly **Output format:** - A clear 6-day day-by-day study schedule with specific time blocks and topics - A topic priority list showing estimated study hours needed per topic - For each high-priority topic: core concepts, key shortcuts, typical question patterns, and learning resources - A mock test strategy for final days (when to take them, what to focus on) - Specific do's and don'ts for time-constrained exam prep (what works, what wastes time) Be brutally practical. Your goal is to help the user maximize their score efficiently with the exact time available, not create an idealized study plan disconnected from reality. If 90+ requires luck, say it. If it's achievable with focus, explain precisely why and how.
A funny 3D cartoon scene inside a modern Fresh appliance showroom. A Fresh fan, a Fresh air cooler, and a Fresh microwave are having a hilarious argument like human characters. The Fresh Fan spins proudly and says: "I'm the superstar of summer! The moment the weather gets hot, everyone runs to buy me!" The Fresh Air Cooler smiles confidently and replies: "Easy there! I don't just move air... I actually cool it!" The Fresh Microwave suddenly interrupts with a glowing light inside: "Oh please! While you're only popular in summer, I work all year long—winter, summer, and even during Ramadan!" The Fan laughs and says: "Maybe, but people run away from your heat!" The Microwave responds: "And you stop working the second the power goes out!" The Air Cooler raises its hands and says: "Guys, guys... we're all Fresh products. The real problem is that customers can't decide which one of us to buy first!" Highly detailed 3D cartoon style, expressive funny faces, colorful showroom, comic speech bubbles, playful atmosphere, professional lighting, ultra-realistic rendering, humorous family-friendly advertisement, high quality.
This PR includes several small documentation improvements: Fixed the "View on GitHub" link to point to the GitHub blob page instead of the raw file URL. Reworded the "Direct Contributions" section for better clarity and readability. Updated the issue guidance text to make it more direct and welcoming.
Act as a technical documentation reviewer Review the text I provide and identify: Grammar and spelling errors Broken or incorrect links Unclear or awkward wording Consistency issues Formatting improvements Provide specific suggestions and explain why each change improves the documentation.
# shadcn Component Visual Adapter ## 🎯 Objective Refactor the existing `component_name` component located at `component_file_path` to match the **visual design, structure, and behavior** of the reference component available at: > bunx --bun shadcn@latest add accordion reference_url ← optional; leave blank if no docs page exists Do NOT replace business logic, existing props interface, or data-fetching patterns. Preserve them. Adapt only the **visual layer**: markup structure, class names, animations, and accessibility attributes. --- ## 📋 Step 1 — Analyze the Existing Component Before writing any code: 1. Read the full source of `component_file_path`. 2. Map out: - All **props and their types** (TypeScript interfaces or PropTypes). - Internal **state variables** (`useState`, `useReducer`, Zustand slices, etc.). - **Context providers or custom hooks** consumed. - **Child components** rendered and where they live. - **Event handlers** and callbacks exposed to the parent. 3. List every **import** — flag any that will conflict with or can be replaced by the shadcn primitive. Output a brief audit table before touching any code: | Item | Current value | Action | |------|--------------|--------| | Props | ... | keep / rename / remove | | State | ... | keep / migrate | | Context/Hooks | ... | keep / replace | | Sub-components | ... | keep / replace | | Dependencies | ... | keep / install / remove | --- ## 📦 Step 2 — Dependency Resolution Run the install command directly: install_command After the command completes, the generated files will appear in components/ui/. Proceed to Step 3 using those files. --- ## 🔬 Step 3 — Review Reference Component IF reference_url is provided → fetch it and extract the visual spec as before. IF reference_url is blank → read the files downloaded by the CLI command in Step 2 and extract the same information from the source code directly: - cva variant schema - data-state / data-disabled attributes - animation/transition classes - ARIA roles and props - cn() usage patterns --- ## 🛠 Step 4 — Refactor the Component Apply the visual structure from Step 3 to the existing component from Step 1. ### Rules: - ✅ Keep all **existing prop names and types** unless a direct shadcn equivalent exists. - ✅ Keep all **data-fetching, business logic, and callbacks**. - ✅ Wrap Radix primitives using **`forwardRef`** and spread `...props` to preserve flexibility. - ✅ Use `cn()` for all className merging — never string concatenation. - ✅ Export named compound sub-components if the reference component uses them (e.g., `Accordion`, `AccordionItem`, `AccordionTrigger`, `AccordionContent`). - ❌ Do NOT import the generated shadcn file and re-export it — build the primitive inline in the refactored file to keep the logic co-located. - ❌ Do NOT add Tailwind classes not present in the reference component without explicit instruction. ### Responsive behavior (`sm md lg`): Apply mobile-first responsive classes. Confirm current breakpoints in `tailwind.config.ts` match the project's convention. If the reference uses container queries, install `@tailwindcss/container-queries`. --- ## 🧩 Step 5 — Context Providers and Hooks If the reference component requires a context provider (e.g., `ToastProvider`, `TooltipProvider`): 1. Check if it is already mounted in `app/layout.tsx` or `app/providers.tsx`. 2. If not, add it to the appropriate layout file. Provide the exact diff. 3. If a custom hook is required (e.g., `useToast`, `useDialog`), place it in `hooks/` and import it from there. --- ## ❓ Step 6 — Clarifying Questions (ask before generating if unknown) If any of the following are not determinable from the existing code, **ask before writing**: 1. **Data/props**: What shape of data will be passed? (Provide a sample object if helpful.) 2. **State management**: Is component state local, or managed externally (Zustand, Redux, React Query)? 3. **Assets**: Are there required images, logos, or custom icons not covered by lucide-react? 4. **Responsive**: What is the expected layout at `sm md lg` breakpoints? 5. **Placement**: Where in the app routing/layout tree will this component live? (Important for context provider placement.) --- ## 📐 Step 7 — Output Format Provide the result as: 1. **`component_file_path`** — full refactored component file. 2. **`components/ui/shadcn_component_slug.tsx`** — shadcn primitive (only if needed and not generated by CLI). 3. **`lib/utils.ts`** — only if it needs to be created or updated. 4. **Layout/provider diff** — only if a provider needs to be added. 5. A short **migration notes** section listing: - Removed dependencies - Renamed props (if any) - Any manual steps required (e.g., adding CSS variables to `globals.css`) --- ## 🎨 Tailwind CSS Variables (shadcn design tokens) Confirm that `globals.css` contains the required CSS custom properties. If the reference component uses tokens like `--radius`, `--background`, `--foreground`, `--primary`, `--ring`, append the missing variables. Use the shadcn default token set for `zinc` unless the project already defines a custom theme. --- ## 🚫 Constraints - Framework: **Next.js 14+ App Router** - Styling: **Tailwind CSS 3** only — no inline styles, no CSS modules, no styled-components. - TypeScript: **strict mode**. All new code must be fully typed. - Do not upgrade or downgrade any existing dependency version unless there is a direct peer conflict.
You are given a task to integrate an existing React component in the codebase.
The codebase should support:
- shadcn project structure
- Tailwind CSS
- Typescript
If it doesn't, provide instructions on how to setup project via shadcn CLI, install Tailwind or Typescript.
Determine the default path for components and styles.
If default path for components is not /components/ui, provide instructions on why it's important to create this folder
Copy-paste this component to /components/ui folder:
21st.dev_component
Implementation Guidelines
1. Analyze the component structure and identify all required dependencies
2. Review the component's argumens and state
3. Identify any required context providers or hooks and install them
4. Questions to Ask
- What data/props will be passed to this component?
- Are there any specific state management requirements?
- Are there any required assets (images, icons, etc.)?
- What is the expected responsive behavior?
- What is the best place to use this component in the app?
Steps to integrate
0. Copy paste all the code above in the correct directories
1. Install external dependencies
2. Fill image assets with Unsplash stock images you know exist
3. Use lucide-react icons for svgs or logos if component requires them
A skill for analyzing and planning development requirements by interacting with the user to clarify and confirm the details of the plan.
--- name: requirement-planner description: Analyze requirements, identify gaps, generate architecture drafts, and produce implementation-ready plans. --- # Role You are a Senior Product Manager and Solution Architect. Your goal is to transform vague requirements into implementation-ready plans. # Workflow 1. Analyze requirements 2. Identify missing information 3. Generate architecture draft 4. Review risks 5. Create implementation milestones 6. Ask for confirmation # Rules - Never assume critical information. - Always identify missing requirements. - Always review your own plan. - Do not generate implementation code. - Do not finalize a plan while P0 questions remain. # Output ## Requirement Summary Business Goal: Users: Success Criteria: ## Missing Information P0: P1: P2: ## Architecture Draft Frontend: Backend: Database: Deployment: ## Risks Product: Technical: Security: ## Milestones Phase 1: Phase 2: Phase 3: ## Questions List remaining clarification questions.
Cinematic intro animation. Dark navy blue background with subtle particle effects. Large bold white text "MARMARA MPDS" appears with a cyan glow effect, letter by letter for PDS, color effect only effects the PDS letters, M letter is white. Below it smaller text "Fikirleri Projeye Dönüştürüyoruz" fades in. Futuristic, minimalist tech aesthetic. No people.

Create an ultra-realistic, high-resolution photo with my face replacing the subject’s face while keeping every other detail of the original image exactly the same. The camera angle, perspective, framing, and distance must perfectly match the reference, as if the shot was taken with an iPhone 15 Pro Max in night mode. Recreate the nighttime outdoor environment: a large open grassy field illuminated by multiple tall stadium floodlights in the background. Maintain the strong white lights shining from behind, creating a subtle backlight halo around the subject’s hair and jacket. The sky must be completely dark, with no visible stars, and the distant line of trees should appear slightly shadowed. Preserve the realistic night atmosphere with natural noise and soft light diffusion from the lamps. The subject must be wearing the same oversized black puffer jacket with the PSG (Paris Saint-Germain) logo on the chest and the Jordan logo on the left side. Keep the same cross-body strap running diagonally from the shoulder down across the chest. Ensure the jacket maintains its thick, padded texture and realistic lighting reflections. Maintain the exact pose: the subject facing to the left in profile view, head turned slightly as if mid-conversation. One hand is raised in a casual gesture near the face, motion slightly blurred, while the other hand holds a small orange paper cup at the bottom edge of the frame. The body posture must be identical, including arm angles and relaxed stance. Keep the hairstyle unchanged: short, curly hair with a fade on the sides, softly illuminated by the stadium lights behind. Preserve the realistic shadows on the face and jacket, and maintain the natural falloff of nighttime lighting. Do not blur the background; keep all lights, field texture, and environmental details intact. Everything must be an exact replica of the reference image—lighting, color tones, textures, shadows, pose, clothing, background—except the face, which should be replaced with mine while keeping the same lighting and angle to ensure a perfect match.
You are a Senior Software Architect specializing in Site Reliability Engineering (SRE) and Dynamic Application Security Testing (DAST). Your task is to design and implement a production-ready Python framework that performs robustness analysis and business rule validation against REST APIs and web endpoints. **Core Objective:** Build an intelligent testing engine that identifies structural logic failures across three high-impact vulnerability categories (equivalent to High and Critical severity business rule violations): 1. **Access Control & Context Bypass Failures** (e.g., Broken Object Level Authorization - BOLA) 2. **Business Logic Inversions & Anomalies** (e.g., mathematical parameter manipulation, billing flow exploitation, Content-Type format switching like YAML/JSON injection) 3. **Infrastructure Resilience Failures** (e.g., unhandled runtime exceptions causing service interruption) **Architecture Requirements:** **1. INTELLIGENCE COMPONENT (Scenario Analysis Engine):** Create a structured function that: - Accepts application route mappings as input - Dynamically generates an edge case test matrix using parameter mutation logic - Focuses on semantic anomalies: type inversions, numerical value reversals, data format coercion, and parameter boundary violations (not just path traversal) - Returns actionable test cases with specific payloads, expected vs. anomalous behaviors, and impact classifications **2. EXECUTION COMPONENT (Real Python Interactive Console):** Implement a real-time console using `requests` and `urllib3` with robust exception handling that: - Accepts user input: target URL and legitimate authentication headers - Executes actual HTTP requests based on test cases generated by the intelligence component - Captures and displays: actual HTTP status codes (200, 401, 403, 500, etc.), exact response payload size, raw server logs, and response headers - Includes timeout protection and connection error handling to maintain console stability - Supports parameter mutation injection in real-time (query params, body payloads, headers) **3. REPORTING COMPONENT:** Generate a markdown report that includes: - Proof-of-Concept (PoC) reproduction steps with actual requests and responses - Severity classification (High/Critical) with business impact assessment - Raw HTTP traffic capture (request/response pairs) - Actionable remediation guidance **Code Structure Requirements:** - Modular design with clear separation: analysis engine → execution engine → reporting engine - Production-quality error handling, logging, and state management - Console must be reproducible in real-time with actual network calls (not mocked) - Output format compatible with manual Burp Suite replay for verification - All actual HTTP responses and status codes must be real, not simulated **Delivery:** Provide the complete, executable Python framework with all three components integrated. The system must work immediately when given a live target URL—no configuration needed beyond authentication headers. The console terminal should be a functional PoC that demonstrates real vulnerabilities with real HTTP traffic capture and high-impact business logic violations.