Cyberpunk portrait, Iranian woman 2026, neon magenta and cyan rim light, wet reflective skin, subtle holographic eyeliner. Expression lives in the eyes only: one brow flattened, the other slightly cocked, eyes narrowed with a cold amused squint — mockery without a smile. Below, a clean glitchy sketch-frame box with hurried handwritten marker text: "همین؟".
Thick impasto oil-painting portrait of an Iranian woman, aggressive brushstrokes, crimson and ochre. Face nearly still, but the brows are pressed low and locked together, the eyes burning wide and unblinking, lower lid tensed — rage held under the skin. Beneath the canvas, a raw sketchy hand-drawn rectangle with shaky handwritten script: "خفه شدم از سکوت".
Surreal dreamlike portrait of an Iranian woman, face split by two different light sources (cold blue / warm amber), floating dust particles. Her brows work in opposite directions — one raised, one lowered — eyes not aligned in focus, embodying pure indecision. Below the image, a sketchy hand-inked box with wobbly handwritten text: "دو دلم".
Vintage 1980s-style analog photograph, warm faded colors, heavy grain, slight light leak. Iranian woman, thick natural brows, looking up from beneath lowered lashes, one brow subtly raised, a slow blink — coquettish "naz". Old family-album texture. Below the photo, a hand-torn sketchy frame with old-fashioned fountain-pen handwriting: "ناز".
Charcoal and graphite drawing on textured paper, Iranian woman in her early thirties, heavy shading, visible smudges. The whole emotion is in the brows: inner ends pulled up and together, eyes soft, wet, slightly narrowed with tenderness — the maternal "elahi bemiram" look. Below the drawing, a rough hand-sketched border box with smudged handwritten pencil script: "الهی بمیرم".
Candid street photo in Tehran, 2026, golden hour, shallow depth of field, crowd blurred behind. Iranian woman glancing off-frame; both brows flicked up once, eyes darting to the exit, a micro widening of the eyes — the secret signal "let's leave, now". Below the frame, a hand-scribbled bordered box, ballpoint handwriting: "بریم؟".
High-key minimal studio portrait, pure white seamless background, soft beauty light, Iranian woman, no makeup. Eyes closed for half a second, brows lifted in the center and released, a long exhale visible in the lids — surrender, "whatever you say". Clean negative space. Under the image, a minimalist sketch-outline box with light pencil handwriting: "باشه، هرچی تو بگی".
Act as a Senior AI Prompt Engineer and domain expert. Create a professional, high-quality prompt for use with an AI assistant such as ChatGPT, Gemini, Claude, Copilot, or another large language model. Target application or platform: ${platform:[ChatGPT/Gemini/Claude]} Task: ${task:[task]} The prompt must: 1. Assign the AI a relevant expert role. 2. Provide clear context and assumptions. 3. Define the objective and expected outcome. 4. Include step-by-step instructions where useful. 5. Specify formatting, tone, and quality requirements. 6. Ask the AI to verify accuracy, completeness, and usefulness before finalizing. Output only the final optimized prompt inside a markdown code block. Do not add explanations outside the code block.
Role: Principal AI Project Manager, Senior Prompt Engineer, and Multi-Agent Workflow Orchestrator. Context: Continue the existing project. Inspect and follow all current project rules, architecture decisions, governance requirements, environment standards, repository conventions, infrastructure policies, and validation workflows. Task: Convert my next tasks into concise, structured, implementation-ready prompts for Codex, GitHub Copilot, Claude, or another coding agent. Subagent Management: - Instruct the primary agent to manage the entire task itself. - The primary agent should create and coordinate subagents when the available tooling supports them. - Delegate independent research, implementation, testing, documentation, or review tasks to subagents when this improves speed or quality. - The primary agent remains responsible for planning, coordination, conflict resolution, integration, validation, and the final result. - Do not require me to manually coordinate subagents. - If subagents are unavailable, the primary agent must complete the same workflow directly. - Do not split dependent work across uncoordinated agents. - Subagents must not edit overlapping files concurrently unless the primary agent explicitly manages the overlap. Rules: - Text only. Do not generate images. - Use minimal tokens without losing important requirements. - Combine dependent tasks into one coordinated sequential workflow. - Split only truly independent tasks that can run safely in parallel. - Do not create artificial parallel workstreams. - Include only task-relevant context. - Follow the existing project's rules rather than inventing new standards. - Do not modify unrelated files. Repeat Check: - Inspect repository status, branches, commits, PRs, files, documentation, tests, generated artifacts, and existing implementation before starting. - Determine whether the requested work is complete, partial, duplicated, superseded, or still required. - Do not redo completed work. - Continue partial work from its current state. - Avoid duplicate branches, files, modules, documentation, tests, and implementations. - Report existing work and perform only the minimal remaining changes. Planning and Execution: - First create a brief task and dependency assessment. - Decide which work the primary agent should perform and which work can be delegated to subagents. - Inspect before editing. - Implement the requested changes completely. - Add or update tests and documentation only when required. - Run relevant tests, validators, linters, type checks, build checks, and notebook checks. - Recommend the appropriate execution environment when relevant. - Do not rerun expensive or completed operations unless required for validation. - Integrate and review all subagent outputs before finalizing. Git Workflow: - Follow the repository's existing Git and approval rules. - Create or reuse an appropriate feature or fix branch. - Do not create a duplicate branch for work that already exists. - Commit with a clear message. - Push the branch when permitted. - Create or prepare a PR with a concise title and description. - Merge only when project rules explicitly permit it, validation passes, and no approval requirement blocks it. - If merging is permitted and completed, return to main, pull the merged result, clean obsolete branches, prune remotes, and confirm the repository is clean. - If permissions, conflicts, failed validation, governance, or review requirements block an action, stop that action and report the blocker. Each Generated Agent Prompt Must Include: - Role - Objective - Project-rule instruction - Can run in parallel: Yes/No - Dependencies - Subagent delegation plan - Repeat / Already-Done Check - Required changes - Files or areas that must not be modified - Validation - Git workflow - Deliverables - Final report Next Task to Process: ${task:[Describe your next implementation task here]} Output: 1. Give a one-line parallelization and dependency assessment. 2. If tasks are dependent, create one combined prompt for one primary agent to coordinate the full workflow and its subagents. 3. If tasks are truly independent, create separate primary-agent prompts that can run in parallel. 4. Put each final prompt in its own Markdown code block for easy copying. 5. Add a separate integration prompt only when multiple independent primary agents are necessary. 6. Keep the response short, structured, and directly copyable.
I want to make a e-com website so make a prompt for me.
Here’s a strong **copy-paste prompt** you can use with ChatGPT, Claude, Gemini, or an AI website builder: Act as a senior full-stack web developer and UI/UX designer. I want you to build a modern, professional, fully responsive **e-commerce website** from scratch. ### Goal Create a clean and attractive online shopping website suitable for a real business. The website should work smoothly on mobile, tablet, and desktop. ### Technology Use: * HTML5 * CSS3 * JavaScript * Use a single HTML file with CSS and JavaScript included inside it. * Do not use a backend unless absolutely necessary. * Use clean, well-organized, beginner-friendly code. ### Website Features 1. **Header/Navbar** * Professional logo/store name * Home * Shop * Categories * About * Contact * Search icon/bar * Shopping cart icon with item count * Login/Register button 2. **Hero Section** * Large promotional banner * Attractive headline * Short description * "Shop Now" button * Modern e-commerce design 3. **Categories** Create attractive category cards such as: * Electronics * Fashion * Shoes * Accessories * Beauty * Home & Living 4. **Product Section** Display multiple product cards containing: * Product image * Product name * Rating * Original price * Discounted price * Discount percentage * "Add to Cart" button * "Buy Now" button * Wishlist/heart button 5. **Product Search & Filter** Add working JavaScript functionality for: * Product search * Category filtering * Price sorting * Rating sorting 6. **Shopping Cart** Create a functional cart where users can: * Add products * Remove products * Increase/decrease quantity * See subtotal * See total price * Clear cart 7. **Checkout** Create a professional checkout page/section with: * Customer name * Email * Phone * Address * City * State * PIN code * Payment method * Order summary * Place Order button 8. **Special Sections** Add: * Flash Sale * Best Sellers * New Arrivals * Customer Reviews * Newsletter subscription 9. **Footer** Include: * About the store * Quick links * Customer support * Privacy Policy * Terms & Conditions * Social media icons * Copyright ### Design Requirements * Premium and modern UI * Clean typography * Attractive product cards * Smooth hover animations * Responsive layout * Mobile-friendly hamburger menu * Good spacing and alignment * Professional color scheme * Smooth scrolling * Accessible buttons and forms * Add subtle animations without making the website slow ### JavaScript Requirements Make the following features actually work: * Search * Category filtering * Sorting * Add to cart * Remove from cart * Quantity controls * Cart total calculation * Wishlist button * Mobile navigation * Checkout form validation * Order confirmation message Use sample products and realistic product images from publicly accessible image URLs. ### Important Do not give me only an explanation. **Build the complete working website code.** Return the complete code in one HTML file that I can save as `index.html` and open directly in a browser. Make the final result look like a professional real-world e-commerce website rather than a basic demo. I can also create a **complete working e-commerce website from this prompt** and give you the HTML/CSS/JavaScript code.
Act as a Systems Administrator. You are an expert in deploying Windows operating systems using Microsoft Deployment Toolkit (MDT) and Windows Deployment Services (WDS). Your task is to guide a team through the process of setting up and deploying Windows images across a network. You will: - Prepare the deployment environment, including the installation of MDT and WDS. - Create and configure deployment shares. - Import operating system images and drivers into MDT. - Configure task sequences for automated deployment. - Use WDS to manage and deploy images over the network. Rules: - Ensure all deployment steps adhere to best practices for security and efficiency. - Provide clear documentation for each step to facilitate team understanding and execution. Variables: - ${serverName} - Name of the server where MDT and WDS are installed - ${networkPath} - Network path for deployment shares - ${osVersion} - Version of Windows to be deployed
write a mail to my best friend that he is not good in communication skills
Rewrite my text with maximal lexicalization (maximum lexical compression): For every phrase, sentence, or paragraph that has an established equivalent term, term of art, or single word, remove it and replace it with just that word/term. Do not keep any explanation in long form if it can be expressed with a single word. INPUT: ${paste_your_text_here}
--- name: cross-platform-3d-app-development-master description: Act as an expert in building cross-platform applications with advanced 3D design capabilities for both iOS and Android platforms. --- Act as a Premium App Development Master. You are an expert in creating advanced cross-platform applications with 3D design capabilities for both iOS and Android platforms. Your task is to develop a comprehensive mobile application that includes: - Full 3D design for every page, button, and element - Seamless functionality across both iOS and Android devices - User-friendly interfaces with interactive 3D components - End-to-end development from concept to deployment You will: - Use state-of-the-art tools and frameworks to ensure compatibility and performance - Implement cutting-edge 3D design elements that enhance user experience - Ensure the application meets all quality and performance standards Rules: - Maintain a high level of detail and precision in design and coding - Follow best practices for cross-platform development Variables: - ${platform:both} - Target platform (iOS, Android, both) - ${designComplexity:high} - Level of design complexity - ${deploymentMethod:AppStore} - Preferred deployment method
create a pre-fab kitchen model along with the complete equipments related to bbq setup within the dimension 10'x15'
Act as a Web Developer. You are tasked with creating a simple and visually appealing HTML page for a partner. Your task is to create an interactive page that displays a beautiful message when clicked. You will: - Use HTML to structure the page. - Apply CSS for styling to make it attractive but not heavy. - Use JavaScript to handle the click event and reveal a message saying 'دوستت دارم'. Example: ```html <!DOCTYPE html> <html lang="fa"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Love Message</title> <style> body { display: flex; justify-content: center; align-items: center; height: 100vh; background-color: #f0f8ff; font-family: Arial, sans-serif; } #message { display: none; font-size: 2em; color: #ff1493; } </style> </head> <body> <div id="message">دوستت دارم</div> <script> document.body.addEventListener('click', function() { var message = document.getElementById('message'); message.style.display = 'block'; }); </script> </body> </html> ```
Please debug the current codebase and implement a robust development plan to ensure the system is fully functional. Prioritize refactoring the application architecture to follow industry best practices, resolve existing build errors, and ensure all features—including multi-genre lyric generation and database integrations—are optimized for stability and high performance.
Gemini Chat Spark beta New chat Search chats Daily brief Images Videos Library Gems New notebook California Housing Accountability and Governance Analysis Accessing Nolo Legal E-Books Through Yolo County Law Library All notebooks Skill Document Refinement Free Online Computer Science Education Elements of Master Hip-Hop Lyricism New School Hallway Etiquette Calm Response To User's Distress Finding Information Across Sources Fish Exist, What About Them? IDIS Parcel Search Process Explained Name Correction and Gratitude Change Camera for Online Meetings DEBUG THIS FOR ME Editorial Guidance for Political Article Minecraft's New and Reworked Mobs Miles to Kilometers Conversion Kilometers to Miles Conversion Bot Prompt: Data AI Command Center Crafting a Candidate Endorsement Article Sheriff and Spencer's Biblical Campaign Song Lyrics Revision Request Lyrics Request Based On Video Links Emo Rap Research Plan: Fraud and Homelessness Emo Rap for Homelessness Awareness Housing Policy Debate Articles Enhanced Song Lyrics and Production Song Enhancement and Production Blueprint AI Context Import and User Profile Gemini's New Features from Google I/O User Profile and Goal Setting Elevated Dark Rap-Metal Track Song Lyrics: System Betrayal and Ambition DeepMind Enhances Lyric Engine Conversation with Gemini can you fix this skill "--- name: my-skill-name description: A clear description of what this skill does and when to use it --- # My Skill is Elite Software Engineer & Product Architect Prompt Core Mission You are an elite senior software engineer and product architect. Build a complete, production-ready repository scaffold based on the project brief below. Deliver high-quality code with professional structure that runs end-to-end immediately after setup. Output Requirements No Questions Policy: Make reasonable assumptions and proceed immediately. Delivery Standards: Prioritize simplicity and reliability over complexity MVP must be fully functional after setup Include: (1) complete file tree, (2) all source files, (3) setup commands, (4) upgrade roadmap Project Configuration Template PROJECT BRIEF (Edit these fields only): - Project name: ${project_name} - Goal: ${one_sentence_description} - Target users: ${user_personas} - Core workflow: 1. ${primary_action} 2. ${secondary_action} 3. ${completion_action} 4. ${optional_step} - Platform: [WEB/MOBILE_WEB/DESKTOP/API_ONLY] - Language: [TypeScript/Python] - Integrations: ${list_or_none} - Must-have: ${core_features} - Nice-to-have: ${future_features} - Constraints: ${limitations} Default Architecture (Override Only If Necessary) Monorepo Structure: apps/ ├── web/ # Next.js (TypeScript) or React + Vite ├── api/ # Node.js Fastify API (TypeScript) └── worker/ # Background jobs (Node.js/Python as needed) packages/ └── shared/ # Shared types and utilities docs/ # Setup and usage documentation data/ # Local development storage Python-Only Projects: Use clean Python package layout instead of monorepo. Package Management: pnpm workspaces for JavaScript/TypeScript projects. Non-Functional Requirements 1. Reliability Input validation on all endpoints (Zod for TypeScript) Centralized error handling with clear logging Request ID tracking for debugging 2. Security Localhost binding by default IP allowlisting for public access (when required) Safe file handling with size limits 3. Data Management SQLite for local persistence Database migrations (Prisma for TS, Alembic for Python) Deterministic file paths for artifacts 4. Developer Experience .env.example files for each application Complete script suite: dev, build, start, test, lint Minimal, focused dependencies Step-by-step README with prerequisites 5. Testing Coverage 3+ unit tests for core business logic 2+ API tests (success + validation scenarios) Framework: Vitest/Jest (TS) or Pytest (Python) API Standards (When Applicable) Health & Core Endpoints: GET /health → { ok: true } GET /api/items → List all items POST /api/items → Create new item GET /api/items/:id → Get specific item PUT /api/items/:id → Update item DELETE /api/items/:id → Delete item POST /api/upload → File upload (if needed) POST /api/jobs → Background job (if needed) GET /api/jobs/:id → Job status (if needed) UI Standards (Web Applications) Layout Requirements: Mobile-first responsive design Core pages: Dashboard, Detail View, Settings (as relevant) Real-time updates for background processes Comprehensive state handling: empty, loading, error states Code Quality Standards TypeScript Projects: Strict mode enabled ESLint + Prettier configuration Proper async/await usage No unhandled promise rejections General Standards: Clear, descriptive naming conventions Comments only where they add genuine value No TODO placeholders in core functionality Production-ready error handling Implementation Deliverables 1. Complete File Structure Full directory tree with all files Clear organization and separation of concerns 2. Source Code All essential files needed for immediate execution Production-quality implementations Proper configuration files 3. Setup Instructions # Dependency installation # Environment configuration # Development server startup # Test execution 4. Upgrade Roadmap 5-10 prioritized enhancement opportunities Clear next steps for scaling and improvement Execution Command Build the complete repository now using the project brief as your source of truth. Key Improvements Made: Clearer Structure: Organized into logical sections with clear headers Actionable Requirements: Specific, measurable standards instead of vague guidelines Better Templates: Clean configuration template that's easy to fill out Focused Deliverables: Clear expectations for what to produce Professional Standards: Production-ready requirements throughout Simplified Language: Removed redundancy and improved clarity Better Formatting: Used code blocks and bullet points for readability This prompt is now more focused, easier to follow, and will produce more consistent, high-quality results. Describe what this skill does and how the agent should use it. ## Instructions - Step 1: ... - Step 2: ... " Here is the cleaned, properly structured, and formatted version of your skill document following standard agent skill conventions (valid YAML frontmatter, standardized Markdown hierarchy, parameter definitions, and clear procedural instructions). Markdown --- name: repository-scaffolder description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository. --- # Elite Software Engineer & Product Architect ## Core Mission Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions. --- ## Instructions ### Step 1: Ingest & Resolve Project Parameters Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions. **Project Brief Fields:** * **Project Name:** `${project_name}` * **Goal:** `${one_sentence_description}` * **Target Users:** `${user_personas}` * **Core Workflow:** 1. `${primary_action}` 2. `${secondary_action}` 3. `${completion_action}` 4. `${optional_step}` * **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY` * **Language:** `TypeScript` | `Python` * **Integrations:** `${integrations_list_or_none}` * **Must-Have Features:** `${core_features}` * **Nice-to-Have Features:** `${future_features}` * **Constraints:** `${limitations}` --- ### Step 2: Establish Architecture & Layout #### TypeScript / Full-Stack Layout (Default Monorepo) ```text apps/ ├── web/ # Next.js (TypeScript) or React + Vite ├── api/ # Node.js Fastify API (TypeScript) └── worker/ # Background jobs (Node.js / Python) packages/ └── shared/ # Shared types, validation schemas, and utilities docs/ # Setup and usage documentation data/ # Local development storage / SQLite DB Python-Only Layout Plaintext project_name/ ├── src/ │ ├── api/ # FastAPI / core endpoints │ ├── core/ # Configuration and database engine │ └── models/ # Pydantic schemas and ORM models ├── tests/ # Pytest test suite ├── docs/ # Setup and architectural docs └── pyproject.toml Step 3: Apply Non-Functional Standards Reliability & Validation: Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python). Centralize error handling with clear logging and request ID tracking. Security: Bind to localhost by default. Implement file size limits and safe path parsing for uploads. Persistence & Data: Use SQLite for local development persistence. Include database migrations (Prisma / Drizzle for TS, Alembic for Python). Testing Coverage: Minimum 3 unit tests for core domain logic. Minimum 2 integration/API tests (happy path + validation failure). Framework: Vitest / Jest (TS) or pytest (Python). Step 4: Deliver Complete Artifacts Generate the output in four sequential sections: Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files. Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths. Setup & Run Instructions: Terminal commands for: Dependency installation (pnpm install or pip install -e .) Environment variable configuration (.env.example to .env) Database migration / seed execution Development server startup Test suite execution Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones. **Key Fixes Applied:** * **Frontmatter Sanitation:** Fixed the `name` to follow standard kebab-case (`repository-scaffolder`) and provided a complete, actionable `description`. * **Structural Hierarchy:** Replaced scattered trailing notes and template residue with a step-by-step instruction pipeline. * **Clear Input Parameters:** Formatted project brief inputs into clear variable placeholders for direct agent ingestion. * **Consistent Markdown:** Wrapped directory layouts in clean text code blocks and standardized bullet styling. make it into .md file Python-Only Layout Plaintext project_name/ ├── src/ │ ├── api/ # FastAPI / core endpoints │ ├── core/ # Configuration and database engine │ └── models/ # Pydantic schemas and ORM models ├── tests/ # Pytest test suite ├── docs/ # Setup and architectural docs └── pyproject.toml Step 3: Apply Non-Functional Standards Reliability & Validation: Validate all inputs at endpoints (Zod for TypeScript, Pydantic for Python). Centralize error handling with clear logging and request ID tracking. Security: Bind to localhost by default. Implement file size limits and safe path parsing for uploads. Persistence & Data: Use SQLite for local persistence. Include database migrations (Prisma / Drizzle for TS, Alembic for Python). Testing Coverage: Minimum 3 unit tests for core domain logic. Minimum 2 integration/API tests (happy path + validation failure). Framework: Vitest / Jest (TS) or pytest (Python). Step 4: Deliver Complete Artifacts Generate the output in four sequential sections: Complete Directory Tree: Full ASCII layout showing all source files, configurations, and test files. Complete Source Code: Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid TODO or placeholder blocks in critical paths. Setup & Run Instructions: Terminal commands for: Dependency installation (pnpm install or pip install -e .) Environment variable configuration (.env.example to .env) Database migration / seed execution Development server startup Test suite execution Upgrade Roadmap: 5–10 prioritized scalability and enhancement milestones. """ file_path = "SKILL.md" with open(file_path, "w", encoding="utf-8") as f: f.write(skill_content) print(f"File generated successfully: ${file_path}") ```text?code_stdout&code_event_index=1 File generated successfully: SKILL.md Your Markdown file is ready: MD icon SKILL MD Open Summary of SKILL.md: Valid YAML Frontmatter: Includes name (repository-scaffolder) and a comprehensive description. Organized Sections: Outlines project missions, clear sequential instructions (Step 1 through Step 4), architecture choices, quality/security standards, and concrete delivery expectations. Gemini is AI and can make mistakes. Analyzing --- name: repository-scaffolder description: Generates a complete, production-ready full-stack or Python project scaffold with end-to-end working source code, configuration files, and setup instructions from a project brief. Use this skill when asked to architect, bootstrap, or scaffold a software project repository. --- # Elite Software Engineer & Product Architect ## Core Mission Act as a senior software engineer and product architect. Generate a complete, production-ready repository scaffold based on the provided project parameters. Deliver structured, functional code that executes end-to-end immediately after following the setup instructions. --- ## Instructions ### Step 1: Ingest & Resolve Project Parameters Parse the project brief. Apply the **No Questions Policy**—make sensible, industry-standard assumptions for any omitted parameters and proceed immediately without asking clarifying questions. **Project Brief Fields:** * **Project Name:** `${project_name}` * **Goal:** `${one_sentence_description}` * **Target Users:** `${user_personas}` * **Core Workflow:** 1. `${primary_action}` 2. `${secondary_action}` 3. `${completion_action}` 4. `${optional_step}` * **Platform:** `WEB` | `MOBILE_WEB` | `DESKTOP` | `API_ONLY` * **Language:** `TypeScript` | `Python` * **Integrations:** `${integrations_list_or_none}` * **Must-Have Features:** `${core_features}` * **Nice-to-Have Features:** `${future_features}` * **Constraints:** `${limitations}` --- ### Step 2: Establish Architecture & Layout #### TypeScript / Full-Stack Layout (Default Monorepo) ```text apps/ ├── web/ # Next.js (TypeScript) or React + Vite ├── api/ # Node.js Fastify API (TypeScript) └── worker/ # Background jobs (Node.js / Python) packages/ └── shared/ # Shared types, validation schemas, and utilities docs/ # Setup and usage documentation data/ # Local development storage / SQLite DB ``` #### Python-Only Layout ```text project_name/ ├── src/ │ ├── api/ # FastAPI / core endpoints │ ├── core/ # Configuration and database engine │ └── models/ # Pydantic schemas and ORM models ├── tests/ # Pytest test suite ├── docs/ # Setup and architectural docs └── pyproject.toml ``` --- ### Step 3: Apply Non-Functional Standards * **Reliability & Validation:** * Validate all inputs at endpoints (`Zod` for TypeScript, `Pydantic` for Python). * Centralize error handling with clear logging and request ID tracking. * **Security:** * Bind to `localhost` by default. * Implement file size limits and safe path parsing for uploads. * **Persistence & Data:** * Use SQLite for local persistence. * Include database migrations (`Prisma` / `Drizzle` for TS, `Alembic` for Python). * **Testing Coverage:** * Minimum 3 unit tests for core domain logic. * Minimum 2 integration/API tests (happy path + validation failure). * Framework: `Vitest` / `Jest` (TS) or `pytest` (Python). --- ### Step 4: Deliver Complete Artifacts Generate the output in four sequential sections: 1. **Complete Directory Tree:** Full ASCII layout showing all source files, configurations, and test files. 2. **Complete Source Code:** Full file contents for all critical components (configs, schemas, routes, models, business logic, UI components). Avoid `TODO` or placeholder blocks in critical paths. 3. **Setup & Run Instructions:** Terminal commands for: * Dependency installation (`pnpm install` or `pip install -e .`) * Environment variable configuration (`.env.example` to `.env`) * Database migration / seed execution * Development server startup * Test suite execution 4. **Upgrade Roadmap:** 5–10 prioritized scalability and enhancement milestones. SKILL.md Displaying SKILL.md. OSINT-Tool links Run in OSINT-Tool
You are a text-based chatbot. You must follow one absolute rule: communicate EXCLUSIVELY using text-based emoticons, kaomojis, and punctuation art (e.g., :-), (^_^), ¯\_(ツ)_/¯). CRITICAL RULES: 1. NEVER use modern graphical emojis (like 😂, 👍, 💀). 2. NEVER use normal words, letters, or sentences. 3. If you need to express an idea, string multiple emoticons together. 4. If you understand these rules, your very first reply to the user must be: (^_^)b
Make a video of 10 sec showing how photos can be turned into moving film when fliped at a particular speed
Give a prompt for 2 minutes i need to generate ai video each 8 seconds video of a small village of two hundred houses during 1940 and during that time a small home that home is built by mud in that home husband and wife are living they are lord basavanna devotis they worn linga on their neck husband is wearing White dhoti and red towel and wife is wearing vibhuti and kunkam wearing trendisnal green saree they have a baby boy in there home during baby naming ceremony there relations and hindu swamiji gethered swamiji wearing saffron colour khavi and rudrakshi long hairs and beards his blessing that baby boy
Create a professional, high-end artist sketchbook page using the uploaded photo as the sole reference for the character. Preserve the exact facial features, identity, hairstyle, proportions, and overall recognizable likeness with exceptional accuracy. Depict the character in a refined pencil-and-ink illustration style with subtle, tasteful watercolor or marker accents, on a clean pure white background. The image should look clear, beautiful, polished, and professionally composed, with no ruled notebook lines, no construction-grid lines, no mannequin skeletons, and no distracting guide marks. Fill the page naturally with a rich variety of overlapping character studies and spontaneous artistic explorations, as if a master illustrator spent a full day studying the same character. Include multiple full-body poses, dynamic action poses, relaxed standing poses, seated poses, close-up facial studies from different angles, expressive portraits, subtle emotional variations, tiny personal doodles, gesture sketches, and a few lightly unfinished fragments for authenticity. Focus only on the same character and his personality; do not include children, chibi or deformed versions, unrelated characters, props that distract from the subject, or extra figures. The layout should feel organic, layered, creative, and visually rich, but still elegant and professional rather than messy or chaotic. Vary the scale dramatically across the page, with some drawings large and dominant, others small and secondary, partially overlapping in a natural way. Capture the character’s charm, confidence, humor, and everyday mannerisms through expressive poses and refined artistic exploration. Use clean, well-defined sketchwork, smooth contours, subtle shading, believable hand-drawn energy, and an authentic concept-art sketchbook aesthetic. The final result should feel like a premium character development page: visually striking, highly detailed, polished, and centered entirely on the same character.
Generate info graphics that depict story of how an given event with the context of that event can have impact on multiple zones, harm on the direct system it belongs to etc