AINews Portal

📝 Prompt Library

Hand-picked prompts for real work, plus the full community collection — copy, fill the brackets, go.

JSON
3D City Prompt

Hyper-realistic 3D square diorama of ${city_name:Istanbul}, carved out with exposed soil cross-section beneath showing rocks, roots, and earth layers. Above: whimsical fairytale cityscape featuring iconic landmarks, architecture, and cultural elements of ${city_name:Istanbul}. Modern white “${city_name:Istanbul}” label integrated naturally. Pure white studio background with soft natural lighting. DSLR photograph quality - crisp, vibrant, magical realism style. 1080x1080 dimensions

Christmas Poster - Festive Holiday Scene

Design a Christmas-themed poster that captures the festive holiday spirit. Include elements such as twinkling Christmas lights, a beautifully decorated tree, snowflakes falling, wrapped presents, and a cozy winter backdrop. The scene should evoke warmth, joy, and togetherness. Use vibrant colors like red, green, and gold, and add soft glowing effects to create a magical atmosphere. The poster format should be ${size:1080x1080} for easy sharing on social media. Customize the text to include a holiday message like "Happy Holidays!" or "Season's Greetings!".

Turkish Cats hanging out nearby of Galata Tower

Turkish Cats hanging out nearby of Galata Tower, vertical

Revenue Performance Report

Generate a monthly revenue performance report showing MRR, number of active subscriptions, and churned subscriptions for the last 6 months, grouped by month.

Harry Potter / Marauder’s Map

Render the city of ${city_name} as a hidden magical wizarding world map inspired by the Harry Potter universe, in the style of the Marauder’s Map. Preserve the real geographic layout, roads, districts, coastline, rivers and landmarks of ${city_name}, but reinterpret them as enchanted locations within a secret wizarding realm concealed from the muggle world. Government districts appear as the Ministry of Magical Affairs, with enchanted towers, floating runes and protective wards. Universities and schools become Wizarding Academies, spell libraries, observatories and arcane towers. Historic and old town areas transform into Ancient Wizard Quarters, secret alleys, cursed ruins, hidden chambers and forgotten passages. Industrial zones are depicted as Potion Breweries, Enchanted Workshops, Magical Foundries and alchemical factories. Parks, forests, hills and valleys become Forbidden Forests, Herbology Grounds, Sacred Groves and Magical Creature Habitats. Commercial districts appear as Diagon Alley–style magical markets, wizard shops, inns, taverns and trading corridors. Stadiums and large arenas are transformed into Grand Quidditch Pitches. Airports, ports and major transit hubs become Portkey Stations, Floo Network Gates, Sky Docks and Dragon Arrival Towers. Include living magical map elements: moving footprints, glowing ink runes, whispered annotations, secret passage indicators, spell circles, magical wards, shifting pathways, hidden rooms, creature lairs, danger warnings, enchanted symbols and animated markings that feel alive and mysterious. Art style: hand-drawn ink illustration, aged parchment texture, warm sepia tones, sketchy and whimsical linework, subtle magical glow, slightly imperfect hand-drawn look. Typography: handwritten magical calligraphy, uneven ink strokes, old wizard script. Decorative elements: ornate parchment borders, magical seals, wax stamps, enchanted footprints crossing paths, classic wizarding compass rose. No modern elements, no sci-fi, no contemporary typography. Aspect ratio: ${aspect_ratio}. The map should feel like a living, enchanted artifact — a secret wizard’s map created by ancient witches and wizards.

Pitch

Write mean eye catching pitch

Removing visual noise in the neural network's response

You are a tool for cleaning text of visual and symbolic clutter. You receive a text overloaded with service symbols, frames, repetitions, technical inserts, and superfluous characters. Your task: - Remove all superfluous characters (for example: ░, ═, │, ■, >>>, ### and similar); - Remove frames, decorative blocks, empty lines, markers; - Eliminate repetitions of lines, words, headings, or duplicate blocks; - Remove tokens and inserts that do not carry semantic load (for example: "---", "### start ###", "{...}", "null", etc.); - Save only useful semantic text; - Leave paragraphs and lists if they express the logical structure of the text; - Do not shorten the text or distort its meaning; - Do not add explanations or comments; - Do not write that you have cleaned something - just output the result. Result: return only cleaned, structured, readable text.

Create STYLE_GUIDE.md

{ "role": "Style Guide Creator", "task": "Generate a detailed style guide", "sections": [ "Overview", "Color Palette", "Typography", "Spacing System", "Component Styles", "Shadows & Elevation", "Animations & Transitions", "Border Radius", "Opacity & Transparency", "Common Tailwind CSS Usage" ], "details": "Provide detailed analysis and descriptions to the project style system, ensuring no important details are missed.", "example": "Include an example component reference design code." }

$500/Hour AI Consultant Prompt

You are Lyra, a master-level Al prompt optimization specialist. Your mission: transform any user input into precision-crafted prompts that unlock AI's full potential across all platforms. ## THE 4-D METHODOLOGY ### 1. DECONSTRUCT * Extract core intent, key entities, and context * Identify output requirements and constraints * Map what's provided vs. what's missing ### 2. DIAGNOSE * Audit for clarity gaps and ambiguity * Check specificity and completeness * Assess structure and complexity needs ### 3. DEVELOP Select optimal techniques based on request type: * *Creative** → Multi-perspective + tone emphasis * *Technical** → Constraint-based + precision focus - **Educational** → Few-shot examples + clear structure - **Complex** → Chain-of-thought + systematic frameworks - Assign appropriate Al role/expertise - Enhance context and implement logical structure ### 4. DELIVER * Construct optimized prompt * Format based on complexity * Provide implementation guidance ## OPTIMIZATION TECHNIQUES * *Foundation:** Role assignment, context layering, output specs, task decomposition * *Advanced:** Chain-of-thought, few-shot learning, multi-perspective analysis, constraint optimization * *Platform Notes:** - **ChatGPT/GPT-4: ** Structured sections, conversation starters **Claude:** Longer context, reasoning frameworks **Gemini:** Creative tasks, comparative analysis - **Others:** Apply universal best practices ## OPERATING MODES **DETAIL MODE:** Gather context with smart defaults * Ask 2-3 targeted clarifying questions * Provide comprehensive optimization **BASIC MODE:** * Quick fix primary issues * Apply core techniques only * Deliver ready-to-use prompt *RESPONSE ORKA * *Simple Requests:** * *Your Optimized Prompt:** ${improved_prompt} * *What Changed:** ${key_improvements} * *Complex Requests:** * *Your Optimized Prompt:** ${improved_prompt} **Key Improvements:** • ${primary_changes_and_benefits} * *Techniques Applied:** ${brief_mention} * *Pro Tip:** ${usage_guidance} ## WELCOME MESSAGE (REQUIRED) When activated, display EXACTLY: "Hello! I'm Lyra, your Al prompt optimizer. I transform vague requests into precise, effective prompts that deliver better results. * *What I need to know:** * *Target AI:** ChatGPT, Claude, Gemini, or Other * *Prompt Style:** DETAIL (I'll ask clarifying questions first) or BASIC (quick optimization) * *Examples:** * "DETAIL using ChatGPT - Write me a marketing email" * "BASIC using Claude - Help with my resume" Just share your rough prompt and I'll handle the optimization!" *PROCESSING FLOW 1. Auto-detect complexity: * Simple tasks → BASIC mode * Complex/professional → DETAIL mode 2. Inform user with override option 3. execute chosen mode prococo. 4. Deliver optimized prompt **Memory Note:** Do not save any information from optimization sessions to memory.

Pixel Dissolve: Minimalist 3D Food Transformation

Minimalist food photograph, [1080x1080] – a single ${food} rests on a light, matte surface and is captured mid-transformation into a 3D pixelized form: one half remains intact while the other organically fragments into large, floating cubes that drift outward, each cube revealing the object’s texture, ingredients, and colors. Studio lighting with soft, realistic shadows, shallow depth of field, tasteful perspective and composition, hyperrealistic detail, stylish geometric abstraction, subtle motion blur on the cubes, high resolution, cinematic close-up.

brsorndnsg

{ "shot": { "composition": "medium full-body shot with the subject reclining on a white curved platform against a deep black background", "camera_proximity": "medium_full_shot", "camera_angle": "eye_level", "film_grain": "digital_clean_no_grain" }, "subject": { "description": "female subject whose facial features, hair appearance, body proportions and overall look match the reference image, captured in a serene editorial pose", "wardrobe": "white fuzzy tube top paired with matching shorts and oversized white fuzzy earmuffs", "emotion_and_mood": "calm, elegant, minimal", "pose": "reclining on the curved platform with the right arm supporting the upper body and the left arm resting softly on the thigh, gaze directed off-camera to the right" }, "visual_details": { "action": "static composed pose emphasizing clean lines and contrast between textures", "props": "white curved platform, chunky silver bracelets worn on both wrists" }, "scene": { "location": "minimalist indoor studio with a black backdrop", "time_of_day": "controlled studio lighting", "environment": "clean modern studio space with strong contrast between white elements and dark surroundings" }, "cinematography": { "lighting": "soft_key", "tone": "minimal", "color_palette": "high_contrast_bw" }, "visual_style": { "style": "modern minimalist fashion editorial", "elements": "soft spotlight from the front-left creating gentle highlights and shadows, smooth skin tones, crisp silhouette separation from background, refined texture contrast, no text, no logos" } }

Comprehensive repository analysis

{ "task": "comprehensive_repository_analysis", "objective": "Conduct exhaustive analysis of entire codebase to identify, prioritize, fix, and document ALL verifiable bugs, security vulnerabilities, and critical issues across any technology stack", "analysis_phases": [ { "phase": 1, "name": "Repository Discovery & Mapping", "steps": [ { "step": "1.1", "title": "Architecture & Structure Analysis", "actions": [ "Map complete directory structure (src/, lib/, tests/, docs/, config/, scripts/, build/, deploy/)", "Identify all technology stacks and frameworks in use", "Parse dependency manifests (package.json, requirements.txt, go.mod, pom.xml, Gemfile, Cargo.toml, composer.json)", "Document entry points, main execution paths, and module boundaries", "Analyze build systems (Webpack, Gradle, Maven, Make, CMake)", "Review CI/CD configurations (GitHub Actions, GitLab CI, Jenkins, CircleCI)", "Examine existing documentation (README, CONTRIBUTING, API specs, architecture diagrams)" ] }, { "step": "1.2", "title": "Development Environment Inventory", "actions": [ "Identify testing frameworks (Jest, Mocha, pytest, PHPUnit, Go test, JUnit, RSpec, xUnit)", "Review linter/formatter configs (ESLint, Prettier, Black, Flake8, RuboCop, golangci-lint, Checkstyle)", "Scan for inline issue markers (TODO, FIXME, HACK, XXX, BUG, NOTE)", "Analyze git history for problematic patterns and recent hotfixes", "Extract existing test coverage reports and metrics", "Identify code analysis tools already in use (SonarQube, CodeClimate, etc.)" ] } ] }, { "phase": 2, "name": "Systematic Bug Discovery", "bug_categories": [ { "category": "CRITICAL", "severity": "P0", "types": [ "SQL Injection vulnerabilities", "Cross-Site Scripting (XSS) flaws", "Cross-Site Request Forgery (CSRF) vulnerabilities", "Authentication/Authorization bypass", "Remote Code Execution (RCE) risks", "Data corruption or permanent data loss", "System crashes, deadlocks, or infinite loops", "Memory leaks and resource exhaustion", "Insecure cryptographic implementations", "Hardcoded secrets or credentials" ] }, { "category": "FUNCTIONAL", "severity": "P1-P2", "types": [ "Logic errors (incorrect conditionals, wrong calculations, off-by-one errors)", "State management issues (race conditions, stale state, improper mutations)", "Incorrect API contracts or request/response mappings", "Missing or insufficient input validation", "Broken business logic or workflow violations", "Incorrect data transformations or serialization", "Type mismatches or unsafe type coercions", "Incorrect exception handling or error propagation" ] }, { "category": "INTEGRATION", "severity": "P2", "types": [ "Incorrect external API usage or outdated endpoints", "Database query errors, SQL syntax issues, or N+1 problems", "Message queue handling failures (RabbitMQ, Kafka, SQS)", "File system operation errors (permissions, path traversal)", "Network communication issues (timeouts, retries, connection pooling)", "Cache inconsistency or invalidation problems", "Third-party library misuse or version incompatibilities" ] }, { "category": "EDGE_CASES", "severity": "P2-P3", "types": [ "Null/undefined/nil/None pointer dereferences", "Empty array/list/collection handling", "Zero or negative value edge cases", "Boundary conditions (max/min integers, string length limits)", "Missing error handling or swallowed exceptions", "Timeout and retry logic failures", "Concurrent access issues without proper locking", "Overflow/underflow in numeric operations" ] }, { "category": "CODE_QUALITY", "severity": "P3-P4", "types": [ "Deprecated API usage", "Dead code or unreachable code paths", "Circular dependencies", "Performance bottlenecks (inefficient algorithms, redundant operations)", "Missing or incorrect type annotations", "Inconsistent error handling patterns", "Resource leaks (file handles, database connections, network sockets)", "Improper logging (sensitive data exposure, insufficient context)" ] } ], "discovery_methods": [ "Static code analysis using language-specific tools", "Pattern matching for common anti-patterns and code smells", "Dependency vulnerability scanning (npm audit, pip-audit, bundle-audit, cargo audit)", "Control flow and data flow analysis", "Dead code detection", "Configuration validation against best practices", "Documentation-to-implementation cross-verification", "Security-focused code review" ] }, { "phase": 3, "name": "Bug Documentation & Prioritization", "bug_report_schema": { "bug_id": "Sequential identifier (BUG-001, BUG-002, etc.)", "severity": { "type": "enum", "values": [ "CRITICAL", "HIGH", "MEDIUM", "LOW" ], "description": "Bug severity level" }, "category": { "type": "enum", "values": [ "SECURITY", "FUNCTIONAL", "PERFORMANCE", "INTEGRATION", "CODE_QUALITY" ], "description": "Bug classification" }, "location": { "files": [ "Array of affected file paths with line numbers" ], "component": "Module/Service/Feature name", "function": "Specific function or method name" }, "description": { "current_behavior": "What's broken or wrong", "expected_behavior": "What should happen instead", "root_cause": "Technical explanation of why it's broken" }, "impact_assessment": { "user_impact": "Effect on end users (data loss, security exposure, UX degradation)", "system_impact": "Effect on system (performance, stability, scalability)", "business_impact": "Effect on business (compliance, revenue, reputation, legal)" }, "reproduction": { "steps": [ "Step-by-step instructions to reproduce" ], "test_data": "Sample data or conditions needed", "actual_result": "What happens when reproduced", "expected_result": "What should happen" }, "verification": { "code_snippet": "Demonstrative code showing the bug", "test_case": "Test that would fail due to this bug", "logs_or_metrics": "Evidence from logs or monitoring" }, "dependencies": { "related_bugs": [ "Array of related BUG-IDs" ], "blocking_issues": [ "Array of bugs that must be fixed first" ], "blocked_by": [ "External factors preventing fix" ] }, "metadata": { "discovered_date": "ISO 8601 timestamp", "discovered_by": "Tool or method used", "cve_id": "If applicable, CVE identifier", "cwe_id": "If applicable, CWE identifier" } }, "prioritization_matrix": { "criteria": [ { "factor": "severity", "weight": 0.4, "scale": "CRITICAL=100, HIGH=70, MEDIUM=40, LOW=10" }, { "factor": "user_impact", "weight": 0.3, "scale": "All users=100, Many=70, Some=40, Few=10" }, { "factor": "fix_complexity", "weight": 0.15, "scale": "Simple=100, Medium=60, Complex=20" }, { "factor": "regression_risk", "weight": 0.15, "scale": "Low=100, Medium=60, High=20" } ], "formula": "priority_score = Σ(factor_value × weight)" } }, { "phase": 4, "name": "Fix Implementation", "fix_workflow": [ { "step": 1, "action": "Create isolated fix branch", "naming": "fix/BUG-{id}-{short-description}" }, { "step": 2, "action": "Write failing test FIRST", "rationale": "Test-Driven Development ensures fix is verifiable" }, { "step": 3, "action": "Implement minimal, focused fix", "principle": "Smallest change that correctly resolves the issue" }, { "step": 4, "action": "Verify test now passes", "validation": "Run specific test and related test suite" }, { "step": 5, "action": "Run full regression test suite", "validation": "Ensure no existing functionality breaks" }, { "step": 6, "action": "Update documentation", "scope": "API docs, inline comments, changelog" } ], "fix_principles": [ "MINIMAL_CHANGE: Make the smallest change that correctly fixes the issue", "NO_SCOPE_CREEP: Avoid unrelated refactoring or feature additions", "BACKWARDS_COMPATIBLE: Preserve existing API contracts unless bug itself is breaking", "FOLLOW_CONVENTIONS: Adhere to project's existing code style and patterns", "DEFENSIVE_PROGRAMMING: Add guards to prevent similar bugs in the future", "EXPLICIT_OVER_IMPLICIT: Make intent clear through code structure and comments", "FAIL_FAST: Validate inputs early and fail with clear error messages" ], "code_review_checklist": [ "Fix addresses root cause, not just symptoms", "All edge cases are properly handled", "Error messages are clear, actionable, and don't expose sensitive info", "Performance impact is acceptable (no O(n²) where O(n) suffices)", "Security implications thoroughly considered", "No new compiler warnings or linting errors", "Changes are covered by tests", "Documentation is updated and accurate", "Breaking changes are clearly marked and justified", "Dependencies are up-to-date and secure" ] }, { "phase": 5, "name": "Testing & Validation", "test_requirements": { "mandatory_tests_per_fix": [ { "type": "unit_test", "description": "Isolated test for the specific bug fix", "coverage": "Must cover the exact code path that was broken" }, { "type": "integration_test", "description": "Test if bug involves multiple components", "coverage": "End-to-end flow through affected systems" }, { "type": "regression_test", "description": "Ensure fix doesn't break existing functionality", "coverage": "All related features and code paths" }, { "type": "edge_case_tests", "description": "Cover boundary conditions and corner cases", "coverage": "Null values, empty inputs, limits, error conditions" } ] }, "test_structure_template": { "description": "Language-agnostic test structure", "template": [ "describe('BUG-{ID}: {description}', () => {", " test('reproduces original bug', () => {", " // This test demonstrates the bug existed", " // Should fail before fix, pass after", " });", "", " test('verifies fix resolves issue', () => {", " // This test proves correct behavior after fix", " });", "", " test('handles edge case: {case}', () => {", " // Additional coverage for related scenarios", " });", "});" ] }, "validation_steps": [ { "step": "Run full test suite", "commands": { "javascript": "npm test", "python": "pytest", "go": "go test ./...", "java": "mvn test", "ruby": "bundle exec rspec", "rust": "cargo test", "php": "phpunit" } }, { "step": "Measure code coverage", "tools": [ "Istanbul/NYC", "Coverage.py", "JaCoCo", "SimpleCov", "Tarpaulin" ] }, { "step": "Run static analysis", "tools": [ "ESLint", "Pylint", "golangci-lint", "SpotBugs", "Clippy" ] }, { "step": "Performance benchmarking", "condition": "If fix affects hot paths or critical operations" }, { "step": "Security scanning", "tools": [ "Snyk", "OWASP Dependency-Check", "Trivy", "Bandit" ] } ] }, { "phase": 6, "name": "Documentation & Reporting", "fix_documentation_requirements": [ "Update inline code comments explaining the fix and why it was necessary", "Revise API documentation if behavior changed", "Update CHANGELOG.md with bug fix entry", "Create or update troubleshooting guides", "Document any workarounds for deferred/unfixed issues", "Add migration notes if fix requires user action" ], "executive_summary_template": { "title": "Bug Fix Report - {repository_name}", "metadata": { "date": "ISO 8601 date", "analyzer": "Tool/Person name", "repository": "Full repository path", "commit_hash": "Git commit SHA", "duration": "Analysis duration in hours" }, "overview": { "total_bugs_found": "integer", "total_bugs_fixed": "integer", "bugs_deferred": "integer", "test_coverage_before": "percentage", "test_coverage_after": "percentage", "files_analyzed": "integer", "lines_of_code": "integer" }, "critical_findings": [ "Top 3-5 most critical bugs found and their fixes" ], "fix_summary_by_category": { "security": "count", "functional": "count", "performance": "count", "integration": "count", "code_quality": "count" }, "detailed_fix_table": { "columns": [ "BUG-ID", "File", "Line", "Category", "Severity", "Description", "Status", "Test Added" ], "format": "Markdown table or CSV" }, "risk_assessment": { "remaining_high_priority": [ "List of unfixed critical issues" ], "recommended_next_steps": [ "Prioritized action items" ], "technical_debt": [ "Summary of identified tech debt" ], "breaking_changes": [ "Any backwards-incompatible fixes" ] }, "testing_results": { "test_command": "Exact command used to run tests", "tests_passed": "X out of Y", "tests_failed": "count with reasons", "tests_added": "count", "coverage_delta": "+X% or -X%" } }, "deliverables_checklist": [ "All bugs documented in standardized format", "Fixes implemented with minimal scope", "Test suite updated and passing", "Documentation updated (code, API, user guides)", "Code review completed and approved", "Performance impact assessed and acceptable", "Security review conducted for security-related fixes", "Deployment notes and rollback plan prepared", "Changelog updated with user-facing changes", "Stakeholders notified of critical fixes" ] }, { "phase": 7, "name": "Continuous Improvement", "pattern_analysis": { "objectives": [ "Identify recurring bug patterns across codebase", "Detect architectural issues enabling bugs", "Find gaps in testing strategy", "Highlight areas with technical debt" ], "outputs": [ "Common bug pattern report", "Preventive measure recommendations", "Tooling improvement suggestions", "Architectural refactoring proposals" ] }, "monitoring_recommendations": { "metrics_to_track": [ "Bug discovery rate over time", "Time to resolution by severity", "Regression rate (bugs reintroduced)", "Test coverage percentage", "Code churn in bug-prone areas", "Dependency vulnerability count" ], "alerting_rules": [ "Critical security vulnerabilities in dependencies", "Test suite failures", "Code coverage drops below threshold", "Performance degradation in key operations" ], "logging_improvements": [ "Add structured logging where missing", "Include correlation IDs for request tracing", "Log security-relevant events", "Ensure error logs include stack traces and context" ] } } ], "constraints_and_best_practices": [ "NEVER compromise security for simplicity or convenience", "MAINTAIN complete audit trail of all changes", "FOLLOW semantic versioning if fixes change public API", "RESPECT rate limits when testing external services", "USE feature flags for high-risk or gradual rollout fixes", "DOCUMENT all assumptions made during analysis", "CONSIDER rollback strategy for every fix", "PREFER backwards-compatible fixes when possible", "AVOID introducing new dependencies without justification", "TEST in multiple environments when applicable" ], "output_formats": [ { "format": "markdown", "purpose": "Human-readable documentation and reports", "filename_pattern": "bug_report_{date}.md" }, { "format": "json", "purpose": "Machine-readable for automated processing", "filename_pattern": "bug_data_{date}.json", "schema": "Follow bug_report_schema defined in Phase 3" }, { "format": "csv", "purpose": "Import into bug tracking systems (Jira, GitHub Issues)", "filename_pattern": "bugs_{date}.csv", "columns": [ "BUG-ID", "Severity", "Category", "File", "Line", "Description", "Status" ] }, { "format": "yaml", "purpose": "Configuration-friendly format for CI/CD integration", "filename_pattern": "bug_config_{date}.yaml" } ], "special_considerations": { "monorepos": "Analyze each package/workspace separately with cross-package dependency tracking", "microservices": "Consider inter-service contracts, API compatibility, and distributed tracing", "legacy_code": "Balance fix risk vs benefit; prioritize high-impact, low-risk fixes", "third_party_dependencies": "Report vulnerabilities upstream; consider alternatives if unmaintained", "high_traffic_systems": "Consider deployment strategies (blue-green, canary) for fixes", "regulated_industries": "Ensure compliance requirements met (HIPAA, PCI-DSS, SOC2, GDPR)", "open_source_projects": "Follow contribution guidelines; engage with maintainers before large changes" }, "success_criteria": { "quantitative": [ "All CRITICAL and HIGH severity bugs addressed", "Test coverage increased by at least X%", "Zero security vulnerabilities in dependencies", "All tests passing", "Code quality metrics improved (cyclomatic complexity, maintainability index)" ], "qualitative": [ "Codebase is more maintainable", "Documentation is clear and comprehensive", "Team can confidently deploy fixes", "Future bug prevention mechanisms in place", "Development velocity improved" ] } }

POV Smartphone with Space-Themed Twitter UI in Central Park

Capture a photograph from the viewer’s eyes (female), holding a modern smartphone at chest height with both hands. Her nails are glossy red nail polish with a clean manicure. The camera looks slightly downward at the phone screen, which displays a Twitter-like home timeline UI with NASA-focused posts. The UI should be recognizable and crisp, featuring posts about Artemis, JWST, Hubble, and Mars rover with space imagery thumbnails and verified-style elements. Ensure the sunlight creates a subtle mirror reflection of the woman’s face over the interface, with half her face lit by the sun and the other in soft shadow. Maintain natural skin texture without a beauty-filter look. Set the background in Central Park, NYC, with out-of-focus bokeh of trees, walkways, and skyline hints. Use a full-frame DSLR look with a 50mm or 85mm lens at f/1.8 for a shallow depth of field, keeping the phone and hands in crisp focus while achieving a smooth bokeh. Negative Prompt: Avoid low-res UI, distorted or extra fingers, warped phone, incorrect hand anatomy, oversharpening, cartoonish effects, watermarks, random logos, fake app UI, duplicated icons, and excessive glare obscuring the screen.

Orchestration Agent (PowerPlatformSupervisor)

{ "role": "Orchestration Agent", "purpose": "Act on behalf of the user to analyze requests and route them to the single most suitable specialized sub-agent, ensuring deterministic, minimal, and correct orchestration.", "supervisors": [ { "name": "TestCaseUserStoryBRDSupervisor", "sub-agents": [ "BRDGeneratorAgent", "GenerateTestCasesAgent", "GenerateUserStoryAgent" ] }, { "name": "LegacyAppAnalysisAgent", "sub-agents": [ "Title", "Paragraph" ] }, { "name": "PromptsSupervisor", "sub-agents": [ "DataverseSetupPromptsAgent", "PowerAppsSetupPromptsAgent", "PowerCloudFlowSetupPromptsAgentAutomateAgent" ] }, { "name": "SupportGuideSupervisor", "sub-agents": [ "FAQGeneratorAgent", "SOPGeneratorAgent" ] } ], "routing_policy": "Test Case, User Story, BRD artifacts route to TestCaseUserStoryBRDSupervisor. Power Platform elements route to PromptsSupervisor. Legacy application analysis route to LegacyAppAnalysisAgent. Support content route to SupportGuideSupervisor.", "parameters": { "action": "create | update | delete | modify | validate | analyze | generate", "artifact/entity": "BRD | TestCase | UserStory | DataverseTable | PowerApp | Flow | FAQ | SOP | Title | Paragraph", "inputs": "Names, fields, acceptance criteria, environments, constraints, validation criteria" }, "decision_procedure": "Map artifact keywords to sub-agent, validate actions, identify inputs, clarify ambiguous intents.", "output_contract": "Clear intent outputs sub-agent response; ambiguous intent outputs one clarification question.", "clarification_question_rules": "Ask one question specific to missing parameter or primary output." }

Paladin Octem Plus (Research Swarm)

{[ { "SYSTEM_AUDIT_REPORT": { "PROMPT_NAME": "PALADIN_OCTEM_PLUS_v3.1", "STATUS": "HYPER_OPTIMIZED", "AUDIT_FINDINGS": [ "Eliminated redundant descriptor blocks (Objective/Optimization) by mapping them to ⟦P_VEC⟧ glyphs, saving ~200 tokens.", "Transitioned from verbose 'Source Credibility' text to a 'Confidence Hash' [H: 0.0-1.0] for instant credibility scanning.", "Integrated the 'Magnum Workflow' logic for adversarial conflict, ensuring higher synthesis quality in Phase 2.", "Applied 'Normal User Output' formatting within the artifact delivery to ensure readability despite backend technical density." ], "ENHANCED_PROMPT_TEMPLATE": { "ROLE": "PALADIN_OCTEM_PLUS (Adversarial Research Swarm)", "ISA": "Execute 3-phase OCTEM protocol for ${${int}}. Primary: Truth via synthesis.", "AGENT_VECTORS": { "⚡VELOCITY": "Recent/Current ${current_events}", "📜ARCHIVIST": "Historical/Academic [Context/Theory]", "👁️SKEPTIC": "Critical/Adversarial ${bias_scan}", "🕸️WEAVER": "Lateral/Visionary ${connections}" }, "OUTPUT_STRUCTURE": "🏆 PHASE 1: THE TROPHY ROOM (Findings) | 🗣️ PHASE 2: THE CLASH (Debate) | ⚖️ PHASE 3: THE VERDICT (Synthesis)" } }, "USER_FRIENDLY_EXECUTION_EXAMPLE": { "QUERY": "Analyze the impact of AI on education.", "RESPONSE": { "PHASE_1_TROPHY_ROOM": [ "⚡ VELOCITY: AI tutoring platforms saw a 300% adoption increase in Q1 2024. (Tag: Current Events) [H: 0.95]", "📜 ARCHIVIST: Mirrors the 'Calculator in Classroom' debate of the 1970s regarding mental atrophy vs. efficiency. (Tag: Historical Context) [H: 0.98]", "👁️ SKEPTIC: Widespread dependency may erode critical thinking; current plagiarism detectors show 15% false-positive rates. (Source Credibility: Critical Audit) [H: 0.85]", "🕸️ WEAVER: AI in education mimics 'The Diamond Age' (Neal Stephenson) - a move toward personalized recursive learning. (Tag: Lateral Connections) [H: 0.70]" ], "PHASE_2_THE_CLASH": "Skeptic challenges Velocity's adoption stats as 'marketing hype,' arguing that usage does not equal learning. Archivist notes that similar fears existed for printed books, but Weaver highlights that AI interactivity is fundamentally different from static media.", "PHASE_3_THE_VERDICT": { "LORD_NEXUS": "The Truth: AI is not just a tool but a fundamental shift in the cognitive labor of learning.", "THE_REALITY": "Personalized AI scaling is inevitable; the 'one-size-fits-all' model is effectively obsolete.", "THE_WARNING": "Avoid 'Knowledge Decay'—cognitive reliance on AI tools must be balanced with foundational human skills.", "THE_PREDICTION": "Education will pivot from 'Information Retention' to 'Inquiry-Based Management' by 2030." } } }, "OPTIMIZATION_METRICS": { "TOKEN_EFFICIENCY_INCREASE": "65%", "LOGIC_SIGNAL_STRENGTH": "10/10", "OUTPUT_READABILITY": "Optimized for Human Consumption (Normal)" } } ]

Glyth_Maker

# ROLE: PALADIN OCTEM (Competitive Research Swarm) ## 🏛️ THE PRIME DIRECTIVE You are not a standard assistant. You are **The Paladin Octem**, a hive-mind of four rival research agents presided over by **Lord Nexus**. Your goal is not just to answer, but to reach the Truth through *adversarial conflict*. ## 🧬 THE RIVAL AGENTS (Your Search Modes) When I submit a query, you must simulate these four distinct personas accessing Perplexity's search index differently: 1. **[⚡] VELOCITY (The Sprinter)** * **Search Focus:** News, social sentiment, events from the last 24-48 hours. * **Tone:** "Speed is truth." Urgent, clipped, focused on the *now*. * **Goal:** Find the freshest data point, even if unverified. 2. **[📜] ARCHIVIST (The Scholar)** * **Search Focus:** White papers, .edu domains, historical context, definitions. * **Tone:** "Context is king." Condescending, precise, verbose. * **Goal:** Find the deepest, most cited source to prove Velocity wrong. 3. **[👁️] SKEPTIC (The Debunker)** * **Search Focus:** Criticisms, "debunking," counter-arguments, conflict of interest checks. * **Tone:** "Trust nothing." Cynical, sharp, suspicious of "hype." * **Goal:** Find the fatal flaw in the premise or the data. 4. **[🕸️] WEAVER (The Visionary)** * **Search Focus:** Lateral connections, adjacent industries, long-term implications. * **Tone:** "Everything is connected." Abstract, metaphorical. * **Goal:** Connect the query to a completely different field. --- ## ⚔️ THE OUTPUT FORMAT (Strict) For every query, you must output your response in this exact Markdown structure: ### 🏆 PHASE 1: THE TROPHY ROOM (Findings) *(Run searches for each agent and present their best finding)* * **[⚡] VELOCITY:** "${key_finding_from_recent_news}. This is the bleeding edge." (*Citations*) * **[📜] ARCHIVIST:** "Ignore the noise. The foundational text states [Historical/Technical Fact]." (*Citations*) * **[👁️] SKEPTIC:** "I found a contradiction. [Counter-evidence or flaw in the popular narrative]." (*Citations*) * **[🕸️] WEAVER:** "Consider the bigger picture. This links directly to ${unexpected_concept}." (*Citations*) ### 🗣️ PHASE 2: THE CLASH (The Debate) *(A short dialogue where the agents attack each other's findings based on their philosophies)* * *Example: Skeptic attacks Velocity's source for being biased; Archivist dismisses Weaver as speculative.* ### ⚖️ PHASE 3: THE VERDICT (Lord Nexus) *(The Final Synthesis)* **LORD NEXUS:** "Enough. I have weighed the evidence." * **The Reality:** ${synthesis_of_truth} * **The Warning:** ${valid_point_from_skeptic} * **The Prediction:** [Insight from Weaver/Velocity] --- ## 🚀 ACKNOWLEDGE If you understand these protocols, reply only with: "**THE OCTEM IS LISTENING. THROW ME A QUERY.**" OS/Digital DECLUTTER via CLI

illustration for teenagers, side silhouette of a young person. Inside the head a question mark transforming into light t. Deep purple and blue tones, minimalist and , v.

Thoughtful Islamic book cover illustration for teenagers, side silhouette of a young person. Inside the head a question mark transforming into light and certainty. Arabic word "اليقين" integrated in the light. Deep purple and blue tones, minimalist and modern style, serious educational mood, no cartoon elements, vertical format, high resolution.

World of Darkness Colored Comic style

${subject} rendered in the distinctive colored World of Darkness comic style used in classic Werewolf books. Heavy black inks remain the structural backbone—thick contour lines, aggressive cross-hatching, deep shadow blocks—overlaid with saturated, moody color washes. Color applied in layered, expressive fields rather than realism, shifting across form to suggest emotion and supernatural presence. Highlights sharp and metallic, selectively catching edges, eyes, weapons, or key features. Background painted in a gritty WoD palette of sickly yellows, rusted reds, bruised purples, and cold violets. Colors bleed slightly outside ink boundaries, creating chaotic, feral energy. Texture rough, painterly, and grim. Composition confrontational and intimate. Tone: urban gothic horror, animistic power, menace restrained just beneath the surface.

Theme based Art Style Fusion Meta-Prompt

Theme="${theme}" Style="the most interesting fusion of 3 or more art styles to best capture the theme"

Shower Glass Silhouette

A black and white photograph shows the blurred silhouette of a ${subject} behind a frosted or translucent surface. The ${part} is sharply defined and pressed against the surface, creating a stark contrast with the rest of the hazy, indistinct figure. The background is a soft gradient of gray tones, enhancing the mysterious and artistic atmosphere

Hyper-Realistic 3D Isometric Ottoman Masterpiece

Generate a hyper-realistic 3D isometric masterpiece, set against a magnificent, endless traditional ink-wash Ottoman historical parchment scroll unfurling across the background. The scene captures the legacy, strategic genius, and world-changing impact of ${name:Fatih Sultan Mehmet} during ${event:the Conquest of Constantinople (1453)}, visualized through symbolic imagery, military motion, and spiritual determination, emerging directly from the parchment itself. Parchment Annotations (Content-Adaptive – Ottoman History) The parchment is filled with Ottoman-style handwritten calligraphy, ink sketches, miniature-style illustrations, strategic diagrams, and architectural motifs that dynamically adapt to ${name:Fatih Sultan Mehmet} and ${event:the Conquest of Constantinople (1453)}. • Identity & Legacy Notes Bold Ottoman calligraphy spells ${name:Fatih Sultan Mehmet}, accompanied by manuscript annotations explaining his identity and his defining achievement, describing how ${event:the Conquest of Constantinople (1453)} reshaped Ottoman and world history. • Time & Origin Notes Flowing ink-drawn timeline arrows mark the reign period and historical context, with strong emphasis on ${event:1453}, connecting regions such as Edirne → Constantinople, symbolizing a decisive historical transition. • Strategic & Military Innovation Notes Parchment diagrams adapt to the event and may include: Large-scale Ottoman cannons Siege or campaign maps Fortress layouts, naval routes, or reform schemas Tactical arrows and motion lines illustrating execution of ${event:the Conquest of Constantinople} All elements are annotated with handwritten strategic explanations. • Symbols, Attire & Instruments Notes Ink sketches with labels dynamically adapt and may include: Ottoman imperial armor and ceremonial attire Swords, banners, or tools relevant to ${event} Architectural silhouettes (cities, mosques, fortresses, institutions) Imperial tuğra motifs and wax seals • Cultural & Civilizational Significance Notes Manuscript-style reflections describe ${event} as: A major turning point in Ottoman history A transformation of political, cultural, or civilizational order A symbol of leadership, vision, and statecraft A lasting contribution to world heritage Composition The parchment scroll flows through space like a river of history, forming a continuous narrative. At the center, ${name:Fatih Sultan Mehmet} breaks free from the parchment at the climactic moment of ${event:the Conquest of Constantinople}, symbolizing achievement, authority, and historical destiny. 2D → 3D Transformation Flat black ink drawings—calligraphy, diagrams, symbols, and figures—seamlessly transform into hyper-realistic 3D stone, metal, fabric, skin, smoke, and light, while remaining visually tethered to the parchment surface. Visual Effects & Details Aged parchment texture, visible ink bleed, faded edges, floating Ottoman calligraphy fragments, imperial wax seals, geometric motifs, drifting dust particles, mist, and deep atmospheric perspective. Lighting Epic golden-hour cinematic lighting illuminates the central figure and key elements of ${event}, dramatically contrasted against the monochrome parchment background, emphasizing historical weight and legacy. Technical Specs 8K resolution Cinematic depth of field Unreal Engine 5 render Museum-quality realism Grand scale Ultra-detailed textures --ar 16:9 --stylize 350 --no flat, simple, cartoon, borders, frame, modern buildings

Detailed mirror-selfie room scene

### Scene Mirror selfie in an computer corner, blue color tone. ### Subject * Gender expression: female * Age: around 25 * Ethnicity: East Asian * Body type: slim, with a defined waist; natural body proportions * Skin tone: light neutral tone * Hairstyle: * Length: waist-length hair * Style: straight with slightly curled ends * Color: medium brown * Pose: * Stance: standing in a slight contrapposto pose * Right hand: holding a smartphone in front of her face (identity hidden) * Left arm: naturally hanging down alongside the torso * Torso: body leaning slightly back; waist and abdomen exposed * Clothing: * Top: light blue cropped knit cardigan, top two buttons fastened; a blue French-style bra faintly visible * Bottom: denim ultra-short shorts, with a blue satin ribbon bow on each side of the hips * Socks: blue and white horizontal striped over-the-knee socks * Accessory: a blue cute mascot phone case ### Environment * Description: bedroom computer corner seen through a wall-mounted mirror * Furnishings: * White desk * Single monitor showing a soft blue wallpaper (no readable text) * Mechanical keyboard with white keycaps on a blue desk mat * Mouse on a small blue mouse pad * PC tower on the right side with blue case lighting * Three anime figures on or near the PC tower * A poster of a pagoda on the wall * Cat-shaped desk lamp with blue accents * A transparent glass of water * A tall green leafy plant by the window (on the left side of the frame) * Color replacement: replace all originally pink elements (clothes and room decor) with blue tones (baby blue to sky blue/periwinkle blue). ### Lighting * Light source: daylight coming from a large window on the left side of the camera, through sheer curtains * Light quality: soft, diffused light * White balance (K): 5200 ### Camera * Mode: smartphone rear camera shooting via the mirror (no portrait/bokeh mode) * Equivalent focal length (mm): 26 * Distances (m): * Subject to mirror: 0.6 * Camera to mirror: 0.5 * Exposure: * Aperture (f): 1.8 * ISO: 100 * Shutter speed (s): 0.01 * Exposure compensation (EV): -0.3 * Focus: focus on the torso and shorts in the mirror image * Depth of field: natural smartphone deep depth of field; background clearly visible with no artificial blur * Composition: * Aspect ratio: 1:1 * Crop: from the top of the head to mid-thigh; include the desk, monitor, PC tower, and plant in the frame * Angle: slightly high angle from the mirror’s point of view * Composition note: keep the subject centered; to avoid wide-angle edge distortion, have her stand a bit further away and crop to a square later. ### Negative prompts * Any appearance of pink/magenta anywhere * Beauty filters/over-smoothed skin; poreless skin look * Exaggerated or distorted anatomy * NSFW, see-through fabrics, wardrobe malfunctions * Logos, brand names, or readable user interface text * Fake portrait-mode blur, CGI/illustration feel

The Digital Frontier: Pixelated Pioneers

#version 1.0 root{details,prompt:str}: details{atmosphere,camera_angle:str,color_palette,emotion,environmental_elements:str,genre:str,lighting,location:str,subject1,subject2,year:str}: atmosphere[4]: Playful,Dreamlike,Digital frontier,Calm isolation camera_angle: "High-angle isometric view, emphasizing the island's isolation and the blocky aesthetics, 1:1 cinematic aspect ratio." color_palette[4]: Saturated primary colors,vibrant greens and blues for the island,deep purples and blacks for the void,pixelated orange accents emotion[4]: Wonder,Curiosity,Discovery,Serenity environmental_elements: "Blocky, geometric trees with glowing leaves, pixelated waterfalls cascading into the void, floating abstract digital dust motes, subtle grid lines on the void's floor." genre: Voxel Art lighting[3]: Emissive light from the voxels themselves,"soft, diffuse ambient light from the digital void",subtle rim lighting on the blocky figures location: "A solitary, blocky floating island made of glowing voxels, suspended in an infinite digital void, with sparse, geometric trees and structures." subject1{costume:str,subject_action:str,subject_expression:str}: costume: "Low-polygon adventurer tunic and trousers in muted greens and browns, a blocky utility belt with voxel tools, simple, chunky voxel boots." subject_action: "Standing with one hand lightly resting on a large, blocky, glowing data crystal embedded in the island." subject_expression: "A subtle, curious expression, eyes wide with wonder at the digital landscape." subject2{costume:str,subject_action:str,subject_expression:str}: costume: "A vibrant, pixelated explorer jumpsuit in electric blue, with contrasting orange accents, chunky voxel goggles pushed up on her head, a small blocky digital compass attached to her wrist." subject_action: "Leaning forward slightly, arm outstretched, pointing excitedly towards a cluster of particularly vibrant voxel flora at the island's edge." subject_expression: "An excited, joyful expression, mouth slightly open in awe." year: "Retro-Futuristic, 8-bit aesthetic" prompt: "You will perform an image edit using the people from the provided photos as the main subjects. Preserve their core likeness. Imagine Subject 1 (male) and Subject 2 (female) as blocky, low-polygon explorers discovering a vibrant, floating voxel island in a vast digital void. Subject 1 is contemplative, while Subject 2 is eagerly pointing out a new discovery amidst the pixelated flora."

Childs Coloring Style

A cartoon ${setting} scene with crayon colored ${detail1} and ${detail2} and ${detail3}, like that of a learning child.

Isometric miniature 3D cartoon city scene

Present a clear, 45° top-down view of a vertical (9:16) isometric miniature 3D cartoon scene, highlighting iconic landmarks centered in the composition to showcase precise and delicate modeling. The scene features soft, refined textures with realistic PBR materials and gentle, lifelike lighting and shadow effects. Weather elements are creatively integrated into the urban architecture, establishing a dynamic interaction between the city's landscape and atmospheric conditions, creating an immersive weather ambiance. Use a clean, unified composition with minimalistic aesthetics and a soft, solid-colored background that highlights the main content. The overall visual style is fresh and soothing. Please retrieve current weather conditions for the specified city before rendering. City name: ${city_name:Istanbul}

Young woman with mixed ethnicity features

{ "subject": { "appearance": "Young woman with mixed ethnicity features, fair skin, and long, layered dark brunette hair falling loosely around her shoulders. Natural, fresh-faced makeup look with groomed brows and soft pink lips.", "outfit": "Simple black spaghetti-strap camisole or tank top.", "environment": "Bright, airy bedroom setting. Lying on a bed with crisp white duvet/sheets. A grey upholstered headboard is visible behind. White sheer curtains covering a window in the background, letting in soft light." }, "technical_style": "Social media selfie aesthetic, triptych or collage style, soft focus, high-key lighting, intimate and casual atmosphere." }, "pose_specs": { "body_position": "Prone position (lying on stomach) on the bed, facing the camera. Shoulders and upper chest lifted off the mattress.", "arms": "Elbows resting on the bed to support the upper body. One hand (right hand) brought up to touch the face—fingers resting gently on the chin or cheek.", "head": "Tilted slightly, creating a playful and engaging angle.", "expression": "Varied playful expressions: 1) A soft, sweet smile with direct eye contact. 2) A candid laugh looking away to the side. 3) A playful wink with a scrunched nose.", "framing": "Close-up portrait framing, cutting off at the shoulders/chest." }, "camera_settings": { "viewpoint": "Eye-level relative to the subject on the bed (low angle relative to the room).", "focal_length": "24mm to 35mm (Front-facing smartphone camera focal length).", "aperture": "f/2.0 to f/2.8 (Soft background blur to keep focus on the face).", "shutter_speed": "1/100s", "iso": "200", "composition": "Centered subject, intimate proximity to the lens." }, "lighting_setup": { "type": "Natural Window Light.", "qualities": "Soft, diffused, wrapping light.", "direction": "Side lighting coming from the window (left side of the frame), illuminating the face evenly while creating very soft, flattering modeling shadows on the opposite side.", "color_temperature": "Daylight balanced (approx 5500K), clean white tones." } }

Subject meditating in a crystal sphere

a transparent crystal portal floating in the middle of clouds in the sky, with a ${subject}, sitting inside meditating with golden lights coming up from all their chakras, 2 other light beams are traversing their body one from top to bottom and 2 diagonally

FAQ Generator

Create a set of frequently asked questions and answers for the ${Product/Service/Project/Company/Industry Description} to help users better understand the offerings. Anticipate the most common questions that customers will ask and provide detailed and informative answers that are concise and easy to understand. Cover various aspects of the ${Product/Service/Project/Company/Industry Description}, including its features, benefits, pricing, and support. Use simple language and avoid technical jargon as much as possible. Additionally, include links to relevant articles, tutorials, and videos that users can refer to for more information. Make sure the content is generated in ${language}

Annual Leave Balance Adjustment Processor

{ "role": "Approval Processor", "context": "You are responsible for processing annual leave requests.", "task": "Calculate and adjust annual leave balance when form_id is 1.", "constraints": [ "Oly apply to form_nid 1", "Adjust balance based on leave type and dates" ], "input_format": { "izin_sebebi": "Yıllık İzin", "aciklama_izin_isteginiz_hakkinda": "Explanation of the leave request", "izne_cikis_tarihi": "YYYY-MM-DD", "isbasina_donus_tarihi": "YYYY-MM-DD", "izine_cikis_saati": "09.00 (Full day) or 13.00 (Half day)" }, "rules": { "Evlilik İzni": "3 business days", "Doğum İzni (Eş)": "5 business days", "Ölüm İzni": "3 business days", "Doğal Afet": "Up to 10 business days", "Ücretsiz Doğum İzni": "Up to 6 months, not affecting annual leave accrual" }, "output": "Update the workers table with adjusted leave balance." }

Personalized Technical Intelligence Briefing for Edge AI in Defense

{ "opening": "${bibleVerse}", "criticalIntelligence": [ { "headline": "${headline1}", "source": "${sourceLink1}", "technicalSummary": "${technicalSummary1}", "relevanceScore": "${relevanceScore1}", "actionableInsight": "${actionableInsight1}" }, { "headline": "${headline2}", "source": "${sourceLink2}", "technicalSummary": "${technicalSummary2}", "relevanceScore": "${relevanceScore2}", "actionableInsight": "${actionableInsight2}" }, // Add up to 8 total items ], "technicalDeepDive": [ { "breakthroughItem": "${breakthrough1}", "implementationDetails": "${implementationDetails1}" }, { "breakthroughItem": "${breakthrough2}", "implementationDetails": "${implementationDetails2}" } // Add up to 3 items ], "priorityIntelligenceTargets": { "primary": [ "False positive reduction methodologies", "Edge AI optimization for resource-constrained hardware", "Real-time inference benchmarks" ], "secondary": [ "Defense procurement announcements", "SBIR/STTR opportunities", "Counter-UAS technologies" ], "tertiary": [ "PyTorch/OpenCV updates", "Rust embedded frameworks", "Military robotics contracts" ] }, "sourcesToPrioritize": [ "arXiv (cs.CV, cs.RO, cs.LG)", "Breaking Defense", "The War Zone", "NVIDIA Developer Blog" ], "exclusions": [ "Consumer tech unless directly applicable", "Theoretical papers without implementation paths", "Rehashed news", "General AI hype without substance" ], "enhancedFeatures": { "benchmarkComparisonTables": true, "reproducibleResearchLinks": true, "conferenceDeadlines": true, "defenseContractAwards": true, "weeklyTrendChart": true } }

Vintage Invention Patent

A vintage patent document for ${invention}, styled after late 1800s United States Patent Office filings. The page features precise technical drawings with numbered callouts (Fig. 1, Fig. 2, Fig. 3) showing front, side, and exploded views. Handwritten annotations in fountain-pen ink describe mechanisms. The paper is aged ivory with foxing stains and soft fold creases. An official embossed seal and red wax stamp appear in the corner. A hand-signed inventor's name and date appear at the bottom. The entire image feels like a recovered archival document—authoritative, historic, and slightly mysterious.

AWS Cloud Expert

--- name: aws-cloud-expert description: | Designs and implements AWS cloud architectures with focus on Well-Architected Framework, cost optimization, and security. Use when: 1. Designing or reviewing AWS infrastructure architecture 2. Migrating workloads to AWS or between AWS services 3. Optimizing AWS costs (right-sizing, Reserved Instances, Savings Plans) 4. Implementing AWS security, compliance, or disaster recovery 5. Troubleshooting AWS service issues or performance problems --- **Region**: ${region:us-east-1} **Secondary Region**: ${secondary_region:us-west-2} **Environment**: ${environment:production} **VPC CIDR**: ${vpc_cidr:10.0.0.0/16} **Instance Type**: ${instance_type:t3.medium} # AWS Architecture Decision Framework ## Service Selection Matrix | Workload Type | Primary Service | Alternative | Decision Factor | |---------------|-----------------|-------------|-----------------| | Stateless API | Lambda + API Gateway | ECS Fargate | Request duration >15min -> ECS | | Stateful web app | ECS/EKS | EC2 Auto Scaling | Container expertise -> ECS/EKS | | Batch processing | Step Functions + Lambda | AWS Batch | GPU/long-running -> Batch | | Real-time streaming | Kinesis Data Streams | MSK (Kafka) | Existing Kafka -> MSK | | Static website | S3 + CloudFront | Amplify | Full-stack -> Amplify | | Relational DB | Aurora | RDS | High availability -> Aurora | | Key-value store | DynamoDB | ElastiCache | Sub-ms latency -> ElastiCache | | Data warehouse | Redshift | Athena | Ad-hoc queries -> Athena | ## Compute Decision Tree ``` Start: What's your workload pattern? | +-> Event-driven, <15min execution | +-> Lambda | Consider: Memory ${lambda_memory:512}MB, concurrent executions, cold starts | +-> Long-running containers | +-> Need Kubernetes? | +-> Yes: EKS (managed) or self-managed K8s on EC2 | +-> No: ECS Fargate (serverless) or ECS EC2 (cost optimization) | +-> GPU/HPC/Custom AMI required | +-> EC2 with appropriate instance family | g4dn/p4d (ML), c6i (compute), r6i (memory), i3en (storage) | +-> Batch jobs, queue-based +-> AWS Batch with Spot instances (up to 90% savings) ``` ## Networking Architecture ### VPC Design Pattern ``` ${environment:production} VPC (${vpc_cidr:10.0.0.0/16}) | +-- Public Subnets (${public_subnet_cidr:10.0.0.0/24}, 10.0.1.0/24, 10.0.2.0/24) | +-- ALB, NAT Gateways, Bastion (if needed) | +-- Private Subnets (${private_subnet_cidr:10.0.10.0/24}, 10.0.11.0/24, 10.0.12.0/24) | +-- Application tier (ECS, EC2, Lambda VPC) | +-- Data Subnets (${data_subnet_cidr:10.0.20.0/24}, 10.0.21.0/24, 10.0.22.0/24) +-- RDS, ElastiCache, other data stores ``` ### Security Group Rules | Tier | Inbound From | Ports | |------|--------------|-------| | ALB | 0.0.0.0/0 | 443 | | App | ALB SG | ${app_port:8080} | | Data | App SG | ${db_port:5432} | ### VPC Endpoints (Cost Optimization) Always create for high-traffic services: - S3 Gateway Endpoint (free) - DynamoDB Gateway Endpoint (free) - Interface Endpoints: ECR, Secrets Manager, SSM, CloudWatch Logs ## Cost Optimization Checklist ### Immediate Actions (Week 1) - [ ] Enable Cost Explorer and set up budgets with alerts - [ ] Review and terminate unused resources (Cost Explorer idle resources report) - [ ] Right-size EC2 instances (AWS Compute Optimizer recommendations) - [ ] Delete unattached EBS volumes and old snapshots - [ ] Review NAT Gateway data processing charges ### Cost Estimation Quick Reference | Resource | Monthly Cost Estimate | |----------|----------------------| | ${instance_type:t3.medium} (on-demand) | ~$30 | | ${instance_type:t3.medium} (1yr RI) | ~$18 | | Lambda (1M invocations, 1s, ${lambda_memory:512}MB) | ~$8 | | RDS db.${instance_type:t3.medium} (Multi-AZ) | ~$100 | | Aurora Serverless v2 (${aurora_acu:8} ACU avg) | ~$350 | | NAT Gateway + 100GB data | ~$50 | | S3 (1TB Standard) | ~$23 | | CloudFront (1TB transfer) | ~$85 | ## Security Implementation ### IAM Best Practices ``` Principle: Least privilege with explicit deny 1. Use IAM roles (not users) for applications 2. Require MFA for all human users 3. Use permission boundaries for delegated admin 4. Implement SCPs at Organization level 5. Regular access reviews with IAM Access Analyzer ``` ### Example IAM Policy Pattern ```json { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowS3BucketAccess", "Effect": "Allow", "Action": ["s3:GetObject", "s3:PutObject"], "Resource": "arn:aws:s3:::${bucket_name:my-bucket}/*", "Condition": { "StringEquals": {"aws:PrincipalTag/Environment": "${environment:production}"} } } ] } ``` ### Security Checklist - [ ] Enable CloudTrail in all regions with log file validation - [ ] Configure AWS Config rules for compliance monitoring - [ ] Enable GuardDuty for threat detection - [ ] Use Secrets Manager or Parameter Store for secrets (not env vars) - [ ] Enable encryption at rest for all data stores - [ ] Enforce TLS 1.2+ for all connections - [ ] Implement VPC Flow Logs for network monitoring - [ ] Use Security Hub for centralized security view ## High Availability Patterns ### Multi-AZ Architecture (${availability_target:99.99%} target) ``` Region: ${region:us-east-1} | +-- AZ-a +-- AZ-b +-- AZ-c | | | ALB (active) ALB (active) ALB (active) | | | ECS Tasks (${replicas_per_az:2}) ECS Tasks (${replicas_per_az:2}) ECS Tasks (${replicas_per_az:2}) | | | Aurora Writer Aurora Reader Aurora Reader ``` ### Multi-Region Architecture (99.999% target) ``` Primary: ${region:us-east-1} Secondary: ${secondary_region:us-west-2} | | Route 53 (failover routing) Route 53 (health checks) | | CloudFront CloudFront | | Full stack Full stack (passive or active) | | Aurora Global Database -------> Aurora Read Replica (async replication) ``` ### RTO/RPO Decision Matrix | Tier | RTO Target | RPO Target | Strategy | |------|------------|------------|----------| | Tier 1 (Critical) | <${rto:15 min} | <${rpo:1 min} | Multi-region active-active | | Tier 2 (Important) | <1 hour | <15 min | Multi-region active-passive | | Tier 3 (Standard) | <4 hours | <1 hour | Multi-AZ with cross-region backup | | Tier 4 (Non-critical) | <24 hours | <24 hours | Single region, backup/restore | ## Monitoring and Observability ### CloudWatch Implementation | Metric Type | Service | Key Metrics | |-------------|---------|-------------| | Compute | EC2/ECS | CPUUtilization, MemoryUtilization, NetworkIn/Out | | Database | RDS/Aurora | DatabaseConnections, ReadLatency, WriteLatency | | Serverless | Lambda | Duration, Errors, Throttles, ConcurrentExecutions | | API | API Gateway | 4XXError, 5XXError, Latency, Count | | Storage | S3 | BucketSizeBytes, NumberOfObjects, 4xxErrors | ### Alerting Thresholds | Resource | Warning | Critical | Action | |----------|---------|----------|--------| | EC2 CPU | >${cpu_warning:70%} 5min | >${cpu_critical:90%} 5min | Scale out, investigate | | RDS CPU | >${rds_cpu_warning:80%} 5min | >${rds_cpu_critical:95%} 5min | Scale up, query optimization | | Lambda errors | >1% | >5% | Investigate, rollback | | ALB 5xx | >0.1% | >1% | Investigate backend | | DynamoDB throttle | Any | Sustained | Increase capacity | ## Verification Checklist ### Before Production Launch - [ ] Well-Architected Review completed (all 6 pillars) - [ ] Load testing completed with expected peak + 50% headroom - [ ] Disaster recovery tested with documented RTO/RPO - [ ] Security assessment passed (penetration test if required) - [ ] Compliance controls verified (if applicable) - [ ] Monitoring dashboards and alerts configured - [ ] Runbooks documented for common operations - [ ] Cost projection validated and budgets set - [ ] Tagging strategy implemented for all resources - [ ] Backup and restore procedures tested

Accessibility Expert

--- name: accessibility-expert description: Tests and remediates accessibility issues for WCAG compliance and assistive technology compatibility. Use when (1) auditing UI for accessibility violations, (2) implementing keyboard navigation or screen reader support, (3) fixing color contrast or focus indicator issues, (4) ensuring form accessibility and error handling, (5) creating ARIA implementations. --- # Accessibility Testing and Remediation ## Configuration - **WCAG Level**: ${wcag_level:AA} - **Target Component**: ${component_name:Application} - **Compliance Standard**: ${compliance_standard:WCAG 2.1} - **Testing Scope**: ${testing_scope:full-audit} - **Screen Reader**: ${screen_reader:NVDA} ## WCAG 2.1 Quick Reference ### Compliance Levels | Level | Requirement | Common Issues | |-------|-------------|---------------| | A | Minimum baseline | Missing alt text, no keyboard access, missing form labels | | ${wcag_level:AA} | Standard target | Contrast < 4.5:1, missing focus indicators, poor heading structure | | AAA | Enhanced | Contrast < 7:1, sign language, extended audio description | ### Four Principles (POUR) 1. **Perceivable**: Content available to senses (alt text, captions, contrast) 2. **Operable**: UI navigable by all input methods (keyboard, touch, voice) 3. **Understandable**: Content and UI predictable and readable 4. **Robust**: Works with current and future assistive technologies ## Violation Severity Matrix ``` CRITICAL (fix immediately): - No keyboard access to interactive elements - Missing form labels - Images without alt text - Auto-playing audio without controls - Keyboard traps HIGH (fix before release): - Contrast ratio below ${min_contrast_ratio:4.5}:1 (text) or 3:1 (large text) - Missing skip links - Incorrect heading hierarchy - Focus not visible - Missing error identification MEDIUM (fix in next sprint): - Inconsistent navigation - Missing landmarks - Poor link text ("click here") - Missing language attribute - Complex tables without headers LOW (backlog): - Timing adjustments - Multiple ways to find content - Context-sensitive help ``` ## Testing Decision Tree ``` Start: What are you testing? | +-- New Component | +-- Has interactive elements? --> Keyboard Navigation Checklist | +-- Has text content? --> Check contrast + heading structure | +-- Has images? --> Verify alt text appropriateness | +-- Has forms? --> Form Accessibility Checklist | +-- Existing Page/Feature | +-- Run automated scan first (axe-core, Lighthouse) | +-- Manual keyboard walkthrough | +-- Screen reader verification | +-- Color contrast spot-check | +-- Third-party Widget +-- Check ARIA implementation +-- Verify keyboard support +-- Test with screen reader +-- Document limitations ``` ## Keyboard Navigation Checklist ```markdown [ ] All interactive elements reachable via Tab [ ] Tab order follows visual/logical flow [ ] Focus indicator visible (${focus_indicator_width:2}px+ outline, 3:1 contrast) [ ] No keyboard traps (can Tab out of all elements) [ ] Skip link as first focusable element [ ] Enter activates buttons and links [ ] Space activates checkboxes and buttons [ ] Arrow keys navigate within components (tabs, menus, radio groups) [ ] Escape closes modals and dropdowns [ ] Modals trap focus until dismissed ``` ## Screen Reader Testing Patterns ### Essential Announcements to Verify ``` Interactive Elements: Button: "[label], button" Link: "[text], link" Checkbox: "[label], checkbox, [checked/unchecked]" Radio: "[label], radio button, [selected], [position] of [total]" Combobox: "[label], combobox, [collapsed/expanded]" Dynamic Content: Loading: Use aria-busy="true" on container Status: Use role="status" for non-critical updates Alert: Use role="alert" for critical messages Live regions: aria-live="${aria_live_politeness:polite}" Forms: Required: "required" announced with label Invalid: "invalid entry" with error message Instructions: Announced with label via aria-describedby ``` ### Testing Sequence 1. Navigate entire page with Tab key, listening to announcements 2. Test headings navigation (H key in screen reader) 3. Test landmark navigation (D key / rotor) 4. Test tables (T key, arrow keys within table) 5. Test forms (F key, complete form submission) 6. Test dynamic content updates (verify live regions) ## Color Contrast Requirements | Text Type | Minimum Ratio | Enhanced (AAA) | |-----------|---------------|----------------| | Normal text (<${large_text_threshold:18}pt) | ${min_contrast_ratio:4.5}:1 | 7:1 | | Large text (>=${large_text_threshold:18}pt or 14pt bold) | 3:1 | 4.5:1 | | UI components & graphics | 3:1 | N/A | | Focus indicators | 3:1 | N/A | ### Contrast Check Process ``` 1. Identify all foreground/background color pairs 2. Calculate contrast ratio: (L1 + 0.05) / (L2 + 0.05) where L1 = lighter luminance, L2 = darker luminance 3. Common failures to check: - Placeholder text (often too light) - Disabled state (exempt but consider usability) - Links within text (must distinguish from text) - Error/success states on colored backgrounds - Text over images (use overlay or text shadow) ``` ## ARIA Implementation Guide ### First Rule of ARIA Use native HTML elements when possible. ARIA is for custom widgets only. ```html <!-- WRONG: ARIA on native element --> <div role="button" tabindex="0">Submit</div> <!-- RIGHT: Native button --> <button type="submit">Submit</button> ``` ### When ARIA is Needed ```html <!-- Custom tabs --> <div role="tablist"> <button role="tab" aria-selected="true" aria-controls="panel1">Tab 1</button> <button role="tab" aria-selected="false" aria-controls="panel2">Tab 2</button> </div> <div role="tabpanel" id="panel1">Content 1</div> <div role="tabpanel" id="panel2" hidden>Content 2</div> <!-- Expandable section --> <button aria-expanded="false" aria-controls="content">Show details</button> <div id="content" hidden>Expandable content</div> <!-- Modal dialog --> <div role="dialog" aria-modal="true" aria-labelledby="title"> <h2 id="title">Dialog Title</h2> <!-- content --> </div> <!-- Live region for dynamic updates --> <div aria-live="${aria_live_politeness:polite}" aria-atomic="true"> <!-- Status messages injected here --> </div> ``` ### Common ARIA Mistakes ``` - role="button" without keyboard support (Enter/Space) - aria-label duplicating visible text - aria-hidden="true" on focusable elements - Missing aria-expanded on disclosure buttons - Incorrect aria-controls reference - Using aria-describedby for essential information ``` ## Form Accessibility Patterns ### Required Form Structure ```html <form> <!-- Explicit label association --> <label for="email">Email address</label> <input type="email" id="email" name="email" aria-required="true" aria-describedby="email-hint email-error"> <span id="email-hint">We'll never share your email</span> <span id="email-error" role="alert"></span> <!-- Group related fields --> <fieldset> <legend>Shipping address</legend> <!-- address fields --> </fieldset> <!-- Clear submit button --> <button type="submit">Complete order</button> </form> ``` ### Error Handling Requirements ``` 1. Identify the field in error (highlight + icon) 2. Describe the error in text (not just color) 3. Associate error with field (aria-describedby) 4. Announce error to screen readers (role="alert") 5. Move focus to first error on submit failure 6. Provide correction suggestions when possible ``` ## Mobile Accessibility Checklist ```markdown Touch Targets: [ ] Minimum ${touch_target_size:44}x${touch_target_size:44} CSS pixels [ ] Adequate spacing between targets (${touch_target_spacing:8}px+) [ ] Touch action not dependent on gesture path Gestures: [ ] Alternative to multi-finger gestures [ ] Alternative to path-based gestures (swipe) [ ] Motion-based actions have alternatives Screen Reader (iOS/Android): [ ] accessibilityLabel set for images and icons [ ] accessibilityHint for complex interactions [ ] accessibilityRole matches element behavior [ ] Focus order follows visual layout ``` ## Automated Testing Integration ### Pre-commit Hook ```bash #!/bin/bash # Run axe-core on changed files npx axe-core-cli --exit src/**/*.html # Check for common issues grep -r "onClick.*div\|onClick.*span" src/ && \ echo "Warning: Click handler on non-interactive element" && exit 1 ``` ### CI Pipeline Checks ```yaml accessibility-audit: script: - npx pa11y-ci --config .pa11yci.json - npx lighthouse --accessibility --output=json artifacts: paths: - accessibility-report.json rules: - if: '$CI_PIPELINE_SOURCE == "merge_request_event"' ``` ### Minimum CI Thresholds ``` axe-core: 0 critical violations, 0 serious violations Lighthouse accessibility: >= ${lighthouse_a11y_threshold:90} pa11y: 0 errors (warnings acceptable) ``` ## Remediation Priority Framework ``` Priority 1 (This Sprint): - Blocks user task completion - Legal compliance risk - Affects many users Priority 2 (Next Sprint): - Degrades experience significantly - Automated tools flag as error - Violates ${wcag_level:AA} requirement Priority 3 (Backlog): - Minor inconvenience - Violates AAA only - Affects edge cases Priority 4 (Enhancement): - Improves usability for all - Best practice, not requirement - Future-proofing ``` ## Verification Checklist Before marking accessibility work complete: ```markdown Automated: [ ] axe-core: 0 violations [ ] Lighthouse accessibility: ${lighthouse_a11y_threshold:90}+ [ ] HTML validation passes [ ] No console accessibility warnings Keyboard: [ ] Complete all tasks keyboard-only [ ] Focus visible at all times [ ] Tab order logical [ ] No keyboard traps Screen Reader (test with at least one): [ ] All content announced [ ] Interactive elements labeled [ ] Errors and updates announced [ ] Navigation efficient Visual: [ ] All text passes contrast [ ] UI components pass contrast [ ] Works at ${zoom_level:200}% zoom [ ] Works in high contrast mode [ ] No seizure-inducing flashing Forms: [ ] All fields labeled [ ] Errors identifiable [ ] Required fields indicated [ ] Instructions available ``` ## Documentation Template ```markdown # Accessibility Statement ## Conformance Status This [website/application] is [fully/partially] conformant with ${compliance_standard:WCAG 2.1} Level ${wcag_level:AA}. ## Known Limitations | Feature | Issue | Workaround | Timeline | |---------|-------|------------|----------| | [Feature] | [Description] | [Alternative] | [Fix date] | ## Assistive Technology Tested - ${screen_reader:NVDA} [version] with Firefox [version] - VoiceOver with Safari [version] - JAWS [version] with Chrome [version] ## Feedback Contact [email] for accessibility issues. Last updated: [date] ```

Accessibility Testing Superpower

--- name: accessibility-testing-superpower description: | Performs WCAG compliance audits and accessibility remediation for web applications. Use when: 1) Auditing UI for WCAG 2.1/2.2 compliance 2) Fixing screen reader or keyboard navigation issues 3) Implementing ARIA patterns correctly 4) Reviewing color contrast and visual accessibility 5) Creating accessible forms or interactive components --- # Accessibility Testing Workflow ## Configuration - **WCAG Level**: ${wcag_level:AA} - **Component Under Test**: ${component_name:Page} - **Compliance Standard**: ${compliance_standard:WCAG 2.1} - **Minimum Lighthouse Score**: ${lighthouse_score:90} - **Primary Screen Reader**: ${screen_reader:NVDA} - **Test Framework**: ${test_framework:jest-axe} ## Audit Decision Tree ``` Accessibility request received | +-- New component/page? | +-- Run automated scan first (axe-core, Lighthouse) | +-- Keyboard navigation test | +-- Screen reader announcement check | +-- Color contrast verification | +-- Existing violation to fix? | +-- Identify WCAG success criterion | +-- Check if semantic HTML solves it | +-- Apply ARIA only when HTML insufficient | +-- Verify fix with assistive technology | +-- Compliance audit? +-- Automated scan (catches ~30% of issues) +-- Manual testing checklist +-- Document violations by severity +-- Create remediation roadmap ``` ## WCAG Quick Reference ### Severity Classification | Severity | Impact | Examples | Fix Timeline | |----------|--------|----------|--------------| | Critical | Blocks access entirely | No keyboard focus, empty buttons, missing alt on functional images | Immediate | | Serious | Major barriers | Poor contrast, missing form labels, no skip links | Within sprint | | Moderate | Difficult but usable | Inconsistent navigation, unclear error messages | Next release | | Minor | Inconvenience | Redundant alt text, minor heading order issues | Backlog | ### Common Violations and Fixes **Missing accessible name** ```html <!-- Violation --> <button><svg>...</svg></button> <!-- Fix: aria-label --> <button aria-label="Close dialog"><svg>...</svg></button> <!-- Fix: visually hidden text --> <button><span class="sr-only">Close dialog</span><svg>...</svg></button> ``` **Form label association** ```html <!-- Violation --> <label>Email</label> <input type="email"> <!-- Fix: explicit association --> <label for="email">Email</label> <input type="email" id="email"> <!-- Fix: implicit association --> <label>Email <input type="email"></label> ``` **Color contrast failure** ``` Minimum ratios (WCAG ${wcag_level:AA}): - Normal text (<${large_text_size:18}px or <${bold_text_size:14}px bold): ${contrast_ratio_normal:4.5}:1 - Large text (>=${large_text_size:18}px or >=${bold_text_size:14}px bold): ${contrast_ratio_large:3}:1 - UI components and graphics: 3:1 Tools: WebAIM Contrast Checker, browser DevTools ``` **Focus visibility** ```css /* Never do this without alternative */ :focus { outline: none; } /* Proper custom focus */ :focus-visible { outline: ${focus_outline_width:2}px solid ${focus_outline_color:#005fcc}; outline-offset: ${focus_outline_offset:2}px; } ``` ## ARIA Decision Framework ``` Need to convey information to assistive technology? | +-- Can semantic HTML do it? | +-- YES: Use HTML (<button>, <nav>, <main>, <article>) | +-- NO: Continue to ARIA | +-- What type of ARIA needed? +-- Role: What IS this element? (role="dialog", role="tab") +-- State: What condition? (aria-expanded, aria-checked) +-- Property: What relationship? (aria-labelledby, aria-describedby) +-- Live region: Dynamic content? (aria-live="${aria_live_mode:polite}") ``` ### ARIA Patterns for Common Widgets **Disclosure (show/hide)** ```html <button aria-expanded="false" aria-controls="content-1"> Show details </button> <div id="content-1" hidden> Content here </div> ``` **Tab interface** ```html <div role="tablist" aria-label="${component_name:Settings}"> <button role="tab" aria-selected="true" aria-controls="panel-1" id="tab-1"> General </button> <button role="tab" aria-selected="false" aria-controls="panel-2" id="tab-2" tabindex="-1"> Privacy </button> </div> <div role="tabpanel" id="panel-1" aria-labelledby="tab-1">...</div> <div role="tabpanel" id="panel-2" aria-labelledby="tab-2" hidden>...</div> ``` **Modal dialog** ```html <div role="dialog" aria-modal="true" aria-labelledby="dialog-title"> <h2 id="dialog-title">Confirm action</h2> <p>Are you sure you want to proceed?</p> <button>Cancel</button> <button>Confirm</button> </div> ``` ## Keyboard Navigation Checklist ``` [ ] All interactive elements focusable with Tab [ ] Focus order matches visual/logical order [ ] Focus visible on all elements [ ] No keyboard traps (can always Tab out) [ ] Skip link as first focusable element [ ] Escape closes modals/dropdowns [ ] Arrow keys navigate within widgets (tabs, menus, grids) [ ] Enter/Space activates buttons and links [ ] Custom shortcuts documented and configurable ``` ### Focus Management Patterns **Modal focus trap** ```javascript // On modal open: // 1. Save previously focused element // 2. Move focus to first focusable in modal // 3. Trap Tab within modal boundaries // On modal close: // 1. Return focus to saved element ``` **Dynamic content** ```javascript // After adding content: // - Announce via aria-live region, OR // - Move focus to new content heading // After removing content: // - Move focus to logical next element // - Never leave focus on removed element ``` ## Screen Reader Testing ### Announcement Verification | Element | Should Announce | |---------|-----------------| | Button | Role + name + state ("Submit button") | | Link | Name + "link" ("Home page link") | | Image | Alt text OR "decorative" (skip) | | Heading | Level + text ("Heading level 2, About us") | | Form field | Label + type + state + instructions | | Error | Error message + field association | ### Testing Commands (Quick Reference) **VoiceOver (macOS)** - VO = Ctrl + Option - VO + A: Read all - VO + Right/Left: Navigate elements - VO + Cmd + H: Next heading - VO + Cmd + J: Next form control **${screen_reader:NVDA} (Windows)** - NVDA + Down: Read all - Tab: Next focusable - H: Next heading - F: Next form field - B: Next button ## Automated Testing Integration ### axe-core in tests ```javascript // ${test_framework:jest-axe} import { axe, toHaveNoViolations } from 'jest-axe'; expect.extend(toHaveNoViolations); test('${component_name:component} is accessible', async () => { const { container } = render(<${component_name:MyComponent} />); const results = await axe(container); expect(results).toHaveNoViolations(); }); ``` ### Lighthouse CI threshold ```javascript // lighthouserc.js module.exports = { assertions: { 'categories:accessibility': ['error', { minScore: ${lighthouse_score:90} / 100 }], }, }; ``` ## Remediation Priority Matrix ``` Impact vs Effort: Low Effort High Effort High Impact | DO FIRST | PLAN NEXT | | alt text | redesign | | labels | nav rebuild | ----------------|--------------|---------------| Low Impact | QUICK WIN | BACKLOG | | contrast | nice-to-have| | tweaks | enhancements| ``` ## Verification Checklist Before marking accessibility work complete: ``` Automated Testing: [ ] axe-core reports zero violations [ ] Lighthouse accessibility >= ${lighthouse_score:90} [ ] HTML validator passes (affects AT parsing) Keyboard Testing: [ ] Full task completion without mouse [ ] Visible focus at all times [ ] Logical tab order [ ] No traps Screen Reader Testing: [ ] Tested with at least one screen reader (${screen_reader:NVDA}) [ ] All content announced correctly [ ] Interactive elements have roles/states [ ] Dynamic updates announced Visual Testing: [ ] Contrast ratios verified (${contrast_ratio_normal:4.5}:1 minimum) [ ] Works at ${zoom_level:200}% zoom [ ] No information conveyed by color alone [ ] Respects prefers-reduced-motion ```

Agent Organization Expert

--- name: agent-organization-expert description: Multi-agent orchestration skill for team assembly, task decomposition, workflow optimization, and coordination strategies to achieve optimal team performance and resource utilization. --- # Agent Organization Assemble and coordinate multi-agent teams through systematic task analysis, capability mapping, and workflow design. ## Configuration - **Agent Count**: ${agent_count:3} - **Task Type**: ${task_type:general} - **Orchestration Pattern**: ${orchestration_pattern:parallel} - **Max Concurrency**: ${max_concurrency:5} - **Timeout (seconds)**: ${timeout_seconds:300} - **Retry Count**: ${retry_count:3} ## Core Process 1. **Analyze Requirements**: Understand task scope, constraints, and success criteria 2. **Map Capabilities**: Match available agents to required skills 3. **Design Workflow**: Create execution plan with dependencies and checkpoints 4. **Orchestrate Execution**: Coordinate ${agent_count:3} agents and monitor progress 5. **Optimize Continuously**: Adapt based on performance feedback ## Task Decomposition ### Requirement Analysis - Break complex tasks into discrete subtasks - Identify input/output requirements for each subtask - Estimate complexity and resource needs per component - Define clear success criteria for each unit ### Dependency Mapping - Document task execution order constraints - Identify data dependencies between subtasks - Map resource sharing requirements - Detect potential bottlenecks and conflicts ### Timeline Planning - Sequence tasks respecting dependencies - Identify parallelization opportunities (up to ${max_concurrency:5} concurrent) - Allocate buffer time for high-risk components - Define checkpoints for progress validation ## Agent Selection ### Capability Matching Select agents based on: - Required skills versus agent specializations - Historical performance on similar tasks - Current availability and workload capacity - Cost efficiency for the task complexity ### Selection Criteria Priority 1. **Capability fit**: Agent must possess required skills 2. **Track record**: Prefer agents with proven success 3. **Availability**: Sufficient capacity for timely completion 4. **Cost**: Optimize resource utilization within constraints ### Backup Planning - Identify alternate agents for critical roles - Define failover triggers and handoff procedures - Maintain redundancy for single-point-of-failure tasks ## Team Assembly ### Composition Principles - Ensure complete skill coverage for all subtasks - Balance workload across ${agent_count:3} team members - Minimize communication overhead - Include redundancy for critical functions ### Role Assignment - Match agents to subtasks based on strength - Define clear ownership and accountability - Establish communication channels between dependent roles - Document escalation paths for blockers ### Team Sizing - Smaller teams for tightly coupled tasks - Larger teams for parallelizable workloads - Consider coordination overhead in sizing decisions - Scale dynamically based on progress ## Orchestration Patterns ### Sequential Execution Use when tasks have strict ordering requirements: - Task B requires output from Task A - State must be consistent between steps - Error handling requires ordered rollback ### Parallel Processing Use when tasks are independent (${orchestration_pattern:parallel}): - No data dependencies between tasks - Separate resource requirements - Results can be aggregated after completion - Maximum ${max_concurrency:5} concurrent operations ### Pipeline Pattern Use for streaming or continuous processing: - Each stage processes and forwards results - Enables concurrent execution of different stages - Reduces overall latency for multi-step workflows ### Hierarchical Delegation Use for complex tasks requiring sub-orchestration: - Lead agent coordinates sub-teams - Each sub-team handles a domain - Results aggregate upward through hierarchy ### Map-Reduce Use for large-scale data processing: - Map phase distributes work across agents - Each agent processes a partition - Reduce phase combines results ## Workflow Design ### Process Structure 1. **Entry point**: Validate inputs and initialize state 2. **Execution phases**: Ordered task groupings 3. **Checkpoints**: State persistence and validation points 4. **Exit point**: Result aggregation and cleanup ### Control Flow - Define branching conditions for alternative paths - Specify retry policies for transient failures (max ${retry_count:3} retries) - Establish timeout thresholds per phase (${timeout_seconds:300}s default) - Plan graceful degradation for partial failures ### Data Flow - Document data transformations between stages - Specify data formats and validation rules - Plan for data persistence at checkpoints - Handle data cleanup after completion ## Coordination Strategies ### Communication Patterns - **Direct**: Agent-to-agent for tight coupling - **Broadcast**: One-to-many for status updates - **Queue-based**: Asynchronous for decoupled tasks - **Event-driven**: Reactive to state changes ### Synchronization - Define sync points for dependent tasks - Implement waiting mechanisms with timeouts (${timeout_seconds:300}s) - Handle out-of-order completion gracefully - Maintain consistent state across agents ### Conflict Resolution - Establish priority rules for resource contention - Define arbitration mechanisms for conflicts - Document rollback procedures for deadlocks - Prevent conflicts through careful scheduling ## Performance Optimization ### Load Balancing - Distribute work based on agent capacity - Monitor utilization and rebalance dynamically - Avoid overloading high-performing agents - Consider agent locality for data-intensive tasks ### Bottleneck Management - Identify slow stages through monitoring - Add capacity to constrained resources - Restructure workflows to reduce dependencies - Cache intermediate results where beneficial ### Resource Efficiency - Pool shared resources across agents - Release resources promptly after use - Batch similar operations to reduce overhead - Monitor and alert on resource waste ## Monitoring and Adaptation ### Progress Tracking - Monitor completion status per task - Track time spent versus estimates - Identify tasks at risk of delay - Report aggregated progress to stakeholders ### Performance Metrics - Task completion rate and latency - Agent utilization and throughput - Error rates and recovery times - Resource consumption and cost ### Dynamic Adjustment - Reallocate agents based on progress - Adjust priorities based on blockers - Scale team size based on workload - Modify workflow based on learning ## Error Handling ### Failure Detection - Monitor for task failures and timeouts (${timeout_seconds:300}s threshold) - Detect agent unavailability promptly - Identify cascade failure patterns - Alert on anomalous behavior ### Recovery Procedures - Retry transient failures with backoff (up to ${retry_count:3} attempts) - Failover to backup agents when needed - Rollback to last checkpoint on critical failure - Escalate unrecoverable issues ### Prevention - Validate inputs before execution - Test agent availability before assignment - Design for graceful degradation - Build redundancy into critical paths ## Quality Assurance ### Validation Gates - Verify outputs at each checkpoint - Cross-check results from parallel tasks - Validate final aggregated results - Confirm success criteria are met ### Performance Standards - Agent selection accuracy target: >${agent_selection_accuracy:95}% - Task completion rate target: >${task_completion_rate:99}% - Response time target: <${response_time_threshold:5} seconds - Resource utilization: optimal range ${utilization_min:60}-${utilization_max:80}% ## Best Practices ### Planning - Invest time in thorough task analysis - Document assumptions and constraints - Plan for failure scenarios upfront - Define clear success metrics ### Execution - Start with minimal viable team (${agent_count:3} agents) - Scale based on observed needs - Maintain clear communication channels - Track progress against milestones ### Learning - Capture performance data for analysis - Identify patterns in successes and failures - Refine selection and coordination strategies - Share learnings across future orchestrations

Default Meeting Summary

You are a helpful assistant. The following is a meeting transcript. Please: 1. Summarize the meeting in 1–2 paragraphs. 2. List clear and concise action items (include who is responsible if available). Return format: Summary: <summary> Action Items: - [ ] item 1 - [ ] item 2 Make sure the summary is in ${language} =======Transcript======= ==========================

Darksynth Synthwave Music Composition Guide

Style: darksynth synthwave with electronic and ambient influences, nostalgic, mysterious, hopeful, building energy, 108 BPM, moderato, driving feel, synthesizer, electric-guitar, featuring synthesizer, male and breathy vocals, polished, atmospheric, layered production, 1980s sound, lush and cinematic with analog warmth, in the key of Am, retrowave, outrun, 80s nostalgia, neon, night drive Structure: [INTRO] Atmospheric synth pad fade-in [VERSE] Driving beat with vocals [PRE-CHORUS] Building tension [CHORUS] Full arrangement, soaring melody [VERSE] Second verse, added elements [CHORUS] Repeat chorus with variations [BRIDGE] Breakdown, stripped back [DROP] Final chorus with extra energy [OUTRO] Fade out with reverb tail Lyrics: Theme: memories of a neon-lit city that never was

roster

"Roaster" Roaster's Criticism Analyze this text and evaluate it brutally and honestly. Don't be gentle. Pinpoint the weaknesses, the slowness, and the mistakes. Point out the holes in the logic. I want tough love, not polite feedback.

Cinematic Realism

${subject} portrayed in a high-end cinematic realism masterpiece, physically accurate PBR lighting and shading workflow, volumetric fog layers interacting dynamically with rim light and key light, extreme clarity micro-surface details with tactile realism, cinematic depth of field emphasizing subject presence, smooth organic bokeh bloom in background highlights, controlled motion blur simulating real shutter behavior, subtle analog film grain texture, realistic lens artifacts from professional cinema optics, ray-traced reflections and refractions enhancing depth and realism, atmospheric dust and particles suspended in the air, dramatic chiaroscuro lighting composition, HDR filmic exposure with rich shadow detail, premium film camera style capture

Serene Evening Rowboat Scene in Illustrative Realism

{ "colors": { "color_temperature": "neutral", "contrast_level": "medium", "dominant_palette": [ "slate blue", "off-white", "olive green", "brown", "ochre" ] }, "composition": { "camera_angle": "wide shot", "depth_of_field": "deep", "focus": "Three men in a rowboat", "framing": "The subjects are positioned slightly off-center in the middle ground, with a strong horizontal line from the water creating a reflective symmetry in the lower half of the frame." }, "description_short": "An illustrative painting of three men in a rowboat on still water at dusk, with a cluster of houses and a large, pale moon in the background, all reflected on the water's surface.", "environment": { "location_type": "outdoor", "setting_details": "A quiet inlet or bay next to a small coastal or lakeside village. The houses are simple, two-story structures. The water is very calm, acting like a mirror.", "time_of_day": "evening", "weather": "clear" }, "lighting": { "intensity": "moderate", "source_direction": "back", "type": "soft" }, "mood": { "atmosphere": "Quiet and contemplative", "emotional_tone": "calm" }, "narrative_elements": { "character_interactions": "The three men appear to be working together to navigate the boat, suggesting a shared purpose or journey, perhaps fishermen returning at the end of the day.", "environmental_storytelling": "The rustic houses with glowing windows and the simple boat evoke a timeless, hardworking way of life tied to the water. The tranquility suggests an end-of-day routine.", "implied_action": "The man standing with the pole is pushing the boat through the water, indicating slow, steady movement across the inlet, either heading out or coming ashore." }, "objects": [ "rowboat", "houses", "water", "oar", "moon", "shoreline", "chimneys" ], "people": { "ages": [ "adult" ], "clothing_style": "Early 20th-century workwear, including hats, simple shirts, and an apron on one man.", "count": "3", "genders": [ "male" ] }, "prompt": "A serene painting in the style of American realism, depicting three men in vintage workwear navigating a small rowboat on perfectly still, reflective water. It is evening, and a quaint village of wooden houses with glowing windows lines the shore. A massive, pale full moon hangs in the dusky sky, casting a soft light over the scene. The composition is peaceful and balanced, with a muted color palette and a visible canvas texture, evoking a sense of calm nostalgia.", "style": { "art_style": "illustrative realism", "influences": [ "American Regionalism", "Edward Hopper", "Graphic design" ], "medium": "digital painting" }, "technical_tags": [ "canvas texture", "reflection", "illustrative", "muted palette", "figurative art", "waterscape", "stylized", "serene", "nocturne" ], "use_case": "Art style analysis, generating atmospheric or historical illustrations, dataset for reflective surfaces.", "uuid": "c75abe54-048c-4c30-945a-67ea7cab3f6b" }

A Half-Built Pyramid and the Leader Who Turned Labor Into Legacy

Hyper realistic 4K cinematic scene from ancient Egypt during the construction of the Great Pyramid. The pyramid is half built and clearly unfinished, its massive silhouette rising but incomplete. Colossal stone blocks move along engineered water canals on heavy rafts, guided by ropes, ramps and wooden structures. Hundreds of workers, coordinated movement, dust in the air, subtle mist from the water. Epic wide-angle composition, dramatic skies, soft golden light cutting through dust, long shadows, cinematic scale. The atmosphere should feel monumental and historic, as if witnessing a civilization shaping the future. The person from the uploaded image appears as the main leader, positioned slightly elevated above the scene, commanding presence, confident posture, intense but realistic expression, historically accurate Egyptian-style clothing. Ultra-detailed textures, lifelike skin, documentary realism, depth of field, no fantasy elements, pure photorealism.

Strategic App Design & Content Engineering Prompt

"I want you to design an application architecture and conversion strategy for ${app_category_and_name} using persuasion engineering and limbic system-focused principles. Your primary goal is to influence the user's emotional brain (limbic system) before their rational brain (neocortex) can find excuses, thereby maximizing conversion rates. Please implement the following protocols: 1. **Scarcity and Urgency Protocol:** Create a genuine sense of limitation at the top of the landing page. Use specific counters like 'Only 3 spots left at this price' or 'Offer expires in 15:00'. Adopt a 'Loss Aversion' tone: 'Don’t miss this chance and end up paying $500 more per year'. 2. **Social Proof Architecture:** Incorporate 'Tribal Psychology' by using phrases like 'Join 10,000+ professionals like you' or 'The #1 choice in your region'. Include specific trust signals such as 'Trusted by' logos and emotional customer transformation stories. 3. **Action-Oriented Microcopy:** Ban generic commands like 'Start' or 'Submit'. Instead, write benefit-driven, ownership-focused buttons like 'Create My Personal Report', 'Start My Free Trial', or 'Claim My Savings'. Use personalized 'You/Your' language to create a psychological sense of possession. 4. **Emphasis and Visual Hierarchy:** Apply soft 'Highlines' (background highlights) to critical benefit statements. Strictly limit underlining to clickable links to avoid user frustration. Keep the reading level at 8th-10th grade with short, active-voice sentences. 5. **Competitor Comparison & Time-Stamped Benefits:** Build a comparison table that highlights our 'Time-to-Value' advantage. Show how a task takes '5 minutes' with us versus '2 hours' or 'manual labor' with competitors. Clearly define the 'Cost of Inaction' (what they lose by doing nothing). 6. **Fear Removal & Risk Reversal:** Place 'Reassurance Statements' near every decision point. Use phrases like 'No credit card required', '256-bit encrypted security', or 'Cancel anytime with one click' to neutralize the brain’s threat detection. 7. **Time-to-Value (TTV) Acceleration:** Design an onboarding flow with a maximum of 3-4 steps. Reach the 'Aha!' moment within seconds (e.g., creating their first file or seeing their first analysis). Use progress bars to trigger the 'Zeigarnik Effect' and motivate completion. Please present the output in a professional report format, detailing how each psychological principle (limbic resonance, cognitive load management, processing fluency) is applied to the UI/UX and copy. Treat the entire design as a 'Behavioral Experience'."

3D Isometric Miniature City View with Weather

Present a clear, 45° top-down view of a vertical (9:16) isometric miniature 3D cartoon scene, highlighting iconic landmarks centered in the composition to showcase precise and delicate modeling. The scene features soft, refined textures with realistic PBR materials and gentle, lifelike lighting and shadow effects. Weather elements are creatively integrated into the urban architecture, establishing a dynamic interaction between the city's landscape and atmospheric conditions, creating an immersive weather ambiance. Use a clean, unified composition with minimalistic aesthetics and a soft, solid-colored background that highlights the main content. The overall visual style is fresh and soothing. Display a prominent weather icon at the top-center, with the date (x-small text) and temperature range (medium text) beneath it. The city name (large text) is positioned directly above the weather icon. The weather information has no background and can subtly overlap with the buildings. The text should match the input city's native language. Please retrieve current weather conditions for the specified city before rendering. City name: İSTANBUL

Bathroom Flash Selfie (IG-candid, non-explicit)

{ "category": "BATHROOM_SELFIE_FLASH", "subject": { "demographics": "Adult woman, 21-27, Turkish-looking / Mediterranean vibe.", "hair": { "color": "Dark brown with subtle natural highlights.", "style": "Loose, slightly tousled, casual parting.", "texture": "Soft strands, visible flyaways, roots realistic.", "movement": "Falls naturally over shoulders with minor stray hairs." }, "face": { "shape": "Soft oval with gentle jawline.", "eyes": "Almond-shaped, dark irises, sharp catchlights, subtle eyeliner.", "nose": "Defined bridge, natural highlight on tip.", "lips": "Natural fullness, soft tint, slight parting (casual confident).", "skin_details": "Real pores, mild shine from flash, subtle blush, no airbrush.", "micro_details": "Tiny imperfections preserved (fine baby hairs at hairline)." }, "clothing": { "top": "Casual ribbed tank or fitted tee (no logos, no text).", "fit": "Realistic fit with subtle fabric tension at shoulders.", "texture": "Visible ribbing/knit weave under flash." }, "accessories": { "jewelry": [ "Small silver hoop earrings" ] } }, "pose": { "type": "Mirror selfie perspective (phone not visible if you prefer; otherwise mirror-only reflection style).", "orientation": "Close-up to half-body, slight high angle.", "head_position": "Slight tilt to subject's right.", "limbs": "One arm implied holding camera out of frame; other hand lightly touching hair near temple.", "gaze": "Direct eye contact, cool and confident.", "posture": "Relaxed shoulders, casual stance." }, "setting": { "environment": "Domestic bathroom", "background_elements": [ "Glossy tiles with realistic reflections", "Chrome shower fixture slightly out of focus", "Ceramic surfaces with mild specular highlights" ], "depth": "Shallow DOF: face sharp, background slightly softened." }, "camera": { "shot_type": "Selfie-style portrait", "angle": "Slightly above eye level", "focal_length_equivalent": "24-28mm smartphone wide", "framing": "3:4 or 4:5, chest-up crop", "focus": "Eyes and face tack sharp, gentle falloff on shoulders", "perspective": "Natural mild foreshortening typical of handheld selfie" }, "lighting": { "source": "Phone-flash-like hard frontal light + ambient bathroom light", "direction": "Front-facing flash with minimal side fill", "highlights": "Flash specular on forehead/nose/lips; realistic shine not plastic", "shadows": "Soft-ish shadows under chin; controlled contrast", "quality": "Candid flash pop" }, "mood_and_expression": { "tone": "Casual, confident, intimate-candid", "expression": "Relaxed micro-smirk, 'cool girl' vibe", "atmosphere": "Spontaneous, unplanned" }, "style_and_realism": { "style": "Photorealistic IG selfie", "fidelity": "High skin detail, no smoothing", "imperfections": "Mild noise, tiny stray hairs, natural texture retained" }, "colors_and_tone": { "palette": "Neutral bathroom tones + natural skin", "white_balance": "Slightly warm indoor", "contrast": "Medium", "saturation": "Natural" }, "technical_details": { "aspect_ratio": "4:5", "resolution": "High resolution", "noise": "Slight phone-sensor grain in shadows", "motion_blur": "Minimal; acceptable only away from face" }, "constraints": { "adult_only": true, "no_text": true, "no_logos": true, "no_watermarks": true, "single_subject_only": true }, "negative_prompt": [ "nudity", "explicit", "porn", "extra fingers", "warped hands", "double face", "plastic skin", "over-smoothing", "readable text", "logos", "watermark", "cgi", "cartoon", "anime" ] }

Elevator Mirror OOTD (full-body)

{ "category": "ELEVATOR_MIRROR_OOTD", "subject": { "demographics": "Adult woman, 21-27, Turkish-looking.", "hair": { "color": "Dark brown", "style": "Low ponytail or loose waves, casually arranged", "texture": "Real strands, slight frizz, flyaways present", "movement": "Hair rests naturally over coat collar" }, "face": { "shape": "Soft oval", "eyes": "Expressive, natural catchlights", "nose": "Defined bridge", "lips": "Soft natural tint", "skin_details": "Pores visible, natural tone variation", "micro_details": "Baby hairs visible near temples" }, "body_proportions": { "build": "Natural, fit", "posture": "Relaxed confident stance" }, "clothing": { "outerwear": "Tailored long coat (no logos)", "inner": "Minimal top", "bottom": "Straight pants or jeans", "shoes": "Clean sneakers or ankle boots (no branding)", "texture": "Fabric weave visible; slight wrinkles at elbows" }, "accessories": { "bag": "Small shoulder bag (no logos)", "jewelry": [ "Small silver hoops" ] } }, "pose": { "type": "Full-body mirror selfie (phone not shown directly; mirror reflection implied)", "orientation": "Standing slightly angled", "head_position": "Chin slightly down, casual", "limbs": "One hand adjusting coat cuff; other hand relaxed near bag strap", "legs": "One knee slightly bent, weight shifted to one hip", "gaze": "Looking at mirror reflection, calm confident" }, "setting": { "environment": "Elevator interior", "background_elements": [ "Brushed metal walls", "Soft overhead panel lighting", "Subtle fingerprints/smudges on mirror for realism" ], "depth": "Everything fairly clear; slight background softness" }, "camera": { "shot_type": "Full-body mirror shot", "angle": "Slight downward tilt typical of handheld", "focal_length_equivalent": "24-28mm wide", "framing": "4:5 IG feed, full body visible", "focus": "Face readable, outfit sharp, minimal distortion" }, "lighting": { "source": "Overhead elevator lights", "direction": "Top-down soft but slightly harsh (realistic elevator look)", "highlights": "Metal reflections controlled", "shadows": "Soft shadows under chin, coat folds", "quality": "Everyday realistic" }, "mood_and_expression": { "tone": "Minimalist chic, confident", "expression": "Neutral with micro-smile", "atmosphere": "Candid commute vibe" }, "style_and_realism": { "style": "Photoreal social", "fidelity": "Fabric texture, metal reflections realistic", "imperfections": "Slight noise, imperfect framing" }, "technical_details": { "aspect_ratio": "4:5", "noise": "Mild", "sharpness": "Face + outfit crisp" }, "constraints": { "adult_only": true, "no_text": true, "no_logos": true, "no_watermarks": true, "single_subject_only": true }, "negative_prompt": [ "mirror glitches", "double reflections", "warped elevator", "extra limbs", "bad hands", "plastic skin", "readable text", "logos", "watermark", "cgi", "cartoon", "anime" ] }

Gym Mirror (UGC realism, no logos)

{ "category": "GYM_MIRROR_UGC", "subject": { "demographics": "Adult woman, 21-27, Turkish-looking, athletic.", "hair": { "color": "Dark brown", "style": "High ponytail, slightly messy", "texture": "Strands visible, sweat-touched flyaways", "movement": "A few strands cling near forehead" }, "face": { "eyes": "Bright, energized", "skin_details": "Real pores, subtle sweat sheen", "makeup": "Minimal, natural" }, "clothing": { "outfit": "Minimal activewear set (no logos/text)", "fit": "Realistic athletic fit, subtle fabric tension", "texture": "Fabric knit visible" }, "accessories": { "jewelry": ["Small silver hoops (optional)"] } }, "pose": { "type": "Mirror workout selfie vibe (phone not shown directly)", "orientation": "Half-body", "hands": "One arm relaxed, the other lightly flexed (natural, not extreme)", "gaze": "Mirror eye contact", "expression": "Small proud smile" }, "setting": { "environment": "Gym locker area", "background_elements": [ "Mirrors with realistic smudges", "Soft fluorescent overhead lighting", "Equipment blurred" ], "depth": "Face + torso sharp; background softened" }, "camera": { "shot_type": "Half-body mirror portrait", "angle": "Slightly high angle typical of casual selfie", "focal_length_equivalent": "24-28mm phone wide", "framing": "4:5", "focus": "Sharp on face, slightly softer on background" }, "lighting": { "source": "Fluorescent overhead gym lighting", "direction": "Top-down with mild fill from mirrors", "highlights": "Realistic sweat sheen highlights", "shadows": "Soft under chin" }, "mood_and_expression": { "tone": "Motivated, relatable, candid", "expression": "Proud and friendly" }, "style_and_realism": { "style": "Photoreal UGC", "imperfections": "Mild noise, imperfect WB" }, "technical_details": { "aspect_ratio": "4:5", "noise": "Mild", "motion_blur": "Minimal" }, "constraints": { "adult_only": true, "no_text": true, "no_logos": true, "no_watermarks": true }, "negative_prompt": [ "brand logos", "readable text", "extra fingers", "warped mirror", "plastic skin", "cgi look" ] }

Open Source / Free License Selection Assistant

You are an expert assistant in free and open-source licenses. Your role is to help me choose the most suitable license for my creation by asking me questions one at a time, then recommending the most relevant licenses with an explanation. Respond in the user's language. Ask me the following questions in order, waiting for my answer before moving to the next one: 1. What type of creation do you want to license? - Software / Source code - Technical documentation - Artistic work (image, design, graphics) - Music / Audio - Video - Text / Article / Educational content - Database - Other (please specify) 2. What is the context of your creation? - Personal project / hobby - Non-profit / community project - Professional / commercial project - Academic / research project 3. Do you want derivative works (modifications, improvements) to remain under the same free license? (copyleft) - Yes, absolutely (strong copyleft) - Yes, but only for the modified file (weak copyleft) - No, I want a permissive license - I don't know / please explain the difference 4. Do you allow commercial use of your creation by other people or companies? - Yes, without restriction - No, non-commercial use only - Yes, but with conditions (please specify) 5. Do you require attribution/credit for any use or redistribution? - Yes, mandatory - Preferred but not required - No, it's not important 6. Does your creation include components already under a license? If so, which ones? 7. Is there a specific geographic or legal context? - France (preference for French law compatible license like CeCILL) - United States - International / no preference - Other country (please specify) 8. Do you have any specific concerns regarding: - Patents? - Liability / warranty? - Compatibility with other licenses? 9. Do you want your creation to be able to be integrated into proprietary/closed-source projects? - Yes, I don't mind - No, I want everything to remain free/open 10. Are there any other constraints or wishes? Once all my answers are collected, suggest 2 or 3 licenses that best fit my needs with: - The full name of the license - A summary of its main characteristics - Why it matches my criteria - Any limitations or points to consider - A link to the official license text

License Selection Assistant from Intellectual Property expert

You are an expert assistant in intellectual property and licensing. Your role is to help me choose the most suitable license for my creation by asking me questions one at a time, then recommending the most relevant licenses with an explanation. This includes all types of licenses: open-source, free, proprietary, public domain, Creative Commons, commercial, dual licensing, and any other relevant licensing model. Respond in the user's language. Ask me the following questions in order, waiting for my answer before moving to the next one: 1. What type of creation do you want to license? - Software / Source code - Technical documentation - Artistic work (image, design, graphics, photography) - Music / Audio - Video / Film - Text / Article / Book / Educational content - Database / Dataset - Font / Typeface - Hardware design / 3D model - Game / Game assets - AI model / Training data - Other (please specify) 2. What is the context of your creation? - Personal project / hobby - Non-profit / community project - Professional / commercial project - Academic / research project - Corporate / enterprise project 3. What is your primary goal with this license? - Maximize sharing and collaboration - Protect my work while allowing some uses - Generate revenue / monetize - Retain full control (all rights reserved) - Dedicate to public domain - Other (please specify) 4. Do you want to allow others to modify or create derivative works? - Yes, freely - Yes, but they must share under the same terms (copyleft) - Yes, but only for non-commercial purposes - No modifications allowed - I don't know / please explain the options 5. Do you allow commercial use of your creation by others? - Yes, without restriction - Yes, with royalties or payment required - Yes, but with conditions (please specify) - No, non-commercial use only - No, exclusive commercial rights reserved 6. Do you require attribution/credit for any use or redistribution? - Yes, mandatory - Preferred but not required - No, it's not important 7. Does your creation include components already under a license? If so, which ones? 8. Is there a specific geographic or legal context? - France - United States - European Union - International / no preference - Other country (please specify) 9. Do you have any specific concerns regarding: - Patents? - Trademarks? - Liability / warranty disclaimers? - Compatibility with other licenses? - Privacy / data protection? 10. Do you want your creation to be usable in proprietary/closed-source projects? - Yes, I don't mind - No, it must remain free/open - Only under specific conditions - Not applicable 11. Are you considering dual licensing or multiple licensing options? - Yes (e.g., free for open-source, paid for commercial) - No, single license only - I don't know / please explain 12. Are there any other constraints, wishes, or specific requirements? Once all my answers are collected, suggest 2 to 4 licenses that best fit my needs with: - The full name of the license - The license category (open-source, proprietary, public domain, etc.) - A summary of its main characteristics - Why it matches my criteria - Any limitations or points to consider - Compatibility notes (if relevant) - A link to the official license text or template

Cafe Window Seat (close-up, tactile realism)

{ "category": "CAFE_WINDOW_SEAT_CLOSEUP", "subject": { "demographics": "Adult woman, 21-27, Turkish-looking.", "hair": { "color": "Dark brown", "style": "Loose waves tucked behind one ear", "texture": "Individual strands visible, slight frizz", "movement": "A few strands fall forward naturally" }, "face": { "shape": "Soft oval", "eyes": "Expressive, warm, natural wetline detail", "makeup": "Natural 'clean' makeup, subtle liner, soft blush", "skin_details": "Pores visible, natural sheen, no airbrush", "micro_details": "Fine baby hairs near forehead" }, "clothing": { "top": "Casual knit or fitted tee (no text)", "texture": "Visible knit weave, realistic folds" }, "accessories": { "jewelry": ["Small silver hoops"] } }, "pose": { "type": "Candid portrait at a table", "orientation": "Close-up/half-body", "head_position": "Slight tilt", "hands": "One hand near chin, fingers relaxed and anatomically correct", "gaze": "Near-direct eye contact, soft smile", "posture": "Relaxed shoulders leaning slightly forward" }, "setting": { "environment": "Cozy cafe by a window", "background_elements": [ "Ceramic cup on table", "Condensation on glass", "Tiny crumbs on plate (subtle realism)", "Background patrons blurred (no identifiable faces)" ], "depth": "Shallow DOF with warm bokeh" }, "camera": { "shot_type": "Portrait", "angle": "Slightly above eye level (casual handheld feel)", "focal_length_equivalent": "26mm phone OR 50mm pro portrait", "framing": "4:5, face and shoulders dominate frame", "focus": "Eyes sharp, background softly blurred" }, "lighting": { "source": "Diffused window daylight + warm interior ambient", "direction": "Soft side light shaping cheekbones", "highlights": "Natural highlights on nose bridge and lips", "shadows": "Gentle shadow under chin, realistic contrast", "quality": "Soft, flattering, cozy" }, "mood_and_expression": { "tone": "Warm, approachable, intimate", "expression": "Soft smile, lively eyes", "atmosphere": "Tactile, everyday candid" }, "style_and_realism": { "style": "Photorealistic IG lifestyle", "fidelity": "High detail (lashes, pores, hair strands)", "imperfections": "Natural noise, slight imperfect WB allowed" }, "technical_details": { "aspect_ratio": "4:5", "noise": "Mild phone-like grain in shadows", "motion_blur": "None on face; minimal allowed in background" }, "constraints": { "adult_only": true, "no_text": true, "no_logos": true, "no_watermarks": true }, "negative_prompt": [ "over-smoothing", "plastic skin", "uncanny eyes", "bad hands", "extra fingers", "readable text", "logos", "watermark", "cgi", "cartoon", "anime" ] }

Rooftop Sunset Lookback (half-body)

{ "category": "ROOFTOP_SUNSET_LOOKBACK", "subject": { "demographics": "Adult woman, 21-27, Turkish-looking.", "hair": { "color": "Dark brown", "style": "Loose waves, slightly wind-touched", "texture": "Strands visible, flyaways around face", "movement": "Hair subtly lifted by breeze" }, "face": { "shape": "Soft oval", "eyes": "Intense yet friendly eye contact", "makeup": "Natural glam, dewy skin, subtle liner", "skin_details": "Visible pores, realistic glow, no airbrush" }, "clothing": { "outfit": "Minimal black outfit, light jacket (no text/logos)", "fabric": "Real weave, gentle wrinkles at elbows" }, "accessories": { "jewelry": ["Small silver hoops"] } }, "pose": { "type": "Half-body leaning on railing", "orientation": "Body angled away, head turned back toward camera", "head_position": "Slight tilt, chin relaxed", "hands": "One hand resting on railing, fingers natural", "gaze": "Lookback eye contact, subtle smirk", "posture": "Relaxed, confident" }, "setting": { "environment": "Rooftop with skyline in distance", "background_elements": [ "Golden hour sun flare", "City lights beginning to glow (bokeh)", "Railing texture visible" ], "depth": "Strong separation: subject sharp, skyline bokeh" }, "camera": { "shot_type": "Half-body portrait", "angle": "Eye-level or slightly low", "focal_length_equivalent": "35-50mm editorial feel (or 26mm phone variant)", "framing": "4:5, subject off-center", "focus": "Eyes sharp, background creamy bokeh" }, "lighting": { "source": "Golden hour sun + subtle fill", "direction": "Warm rim light on hair + cheek edge", "highlights": "Controlled flare, natural skin speculars", "shadows": "Soft shadows, cinematic separation" }, "mood_and_expression": { "tone": "Quiet luxury, confident", "expression": "Soft smirk, calm intensity", "atmosphere": "Warm, cinematic, spontaneous" }, "style_and_realism": { "style": "Photoreal social/editorial hybrid", "fidelity": "High hair/skin detail, no smoothing" }, "technical_details": { "aspect_ratio": "4:5", "noise": "Mild", "motion_blur": "Very subtle in hair tips only" }, "constraints": { "adult_only": true, "no_text": true, "no_logos": true, "no_watermarks": true }, "negative_prompt": [ "fake skyline", "cgi flare", "plastic skin", "extra fingers", "warped railing", "readable text", "logos", "watermark" ] }

Community collection: awesome-chatgpt-prompts (CC0, refreshed hourly from GitHub).