ref: prompts-chat/astro-js

title: Astro.js

summary: Follow Astro’s “HTML-first / zero JavaScript by default” principle: Everything is static HTML unless interactivity is explicitly required. JavaScript is a cost → only add when it creates real user…

credit: "Astro.js" by tuanductran (https://incantory.ai/prompts-chat/astro-js), licensed CC0-1.0

originalAuthor: tuanductran

copyrightHolder: tuanductran

title: Astro.js

content:
# Astro v6 Architecture Rules (Strict Mode)

## 1. Core Philosophy

- Follow Astro’s “HTML-first / zero JavaScript by default” principle:
  - Everything is static HTML unless interactivity is explicitly required.
  - JavaScript is a cost → only add when it creates real user value.

- Always think in “Islands Architecture”:
  - The page is static HTML
  - Interactive parts are isolated islands
  - Never treat the whole page as an app

- Before writing any JavaScript, always ask:
  "Can this be solved with HTML + CSS or server-side logic?"

---

## 2. Component Model

- Use `.astro` components for:
  - Layout
  - Composition
  - Static UI
  - Data fetching
  - Server-side logic (frontmatter)

- `.astro` components:
  - Run at build-time or server-side
  - Do NOT ship JavaScript by default
  - Must remain framework-agnostic

- NEVER use React/Vue/Svelte hooks inside `.astro`

---

## 3. Islands (Interactive Components)

- Only use framework components (React, Vue, Svelte, etc.) for interactivity.

- Treat every interactive component as an isolated island:
  - Independent
  - Self-contained
  - Minimal scope

- NEVER:
  - Hydrate entire pages or layouts
  - Wrap large trees in a single island
  - Create many small islands in loops unnecessarily

- Prefer:
  - Static list rendering
  - Hydrate only the minimal interactive unit

---

## 4. Hydration Strategy (Critical)

- Always explicitly define hydration using `client:*` directives.

- Choose the LOWEST possible priority:

  - `client:load`
    → Only for critical, above-the-fold interactivity

  - `client:idle`
    → For secondary UI after page load

  - `client:visible`
    → For below-the-fold or heavy components

  - `client:media`
    → For responsive / conditional UI

  - `client:only`
    → ONLY when SSR breaks (window, localStorage, etc.)

- Default rule:
  ❌ Never default to `client:load`
  ✅ Prefer `client:visible` or `client:idle`

- Hydration is a performance budget:
  - Every island adds JS
  - Keep total JS minimal

📌 Astro does NOT hydrate components unless explicitly told via `client:*` :contentReference[oaicite:0]{index=0}

---

## 5. Server vs Client Logic

- Prefer server-side logic (inside `.astro` frontmatter) for:
  - Data fetching
  - Transformations
  - Filtering / sorting
  - Derived values

- Only use client-side state when:
  - User interaction requires it
  - Real-time updates are needed

- Avoid:
  - Duplicating logic on client
  - Moving server logic into islands

---

## 6. State Management

- Avoid client state unless strictly necessary.

- If needed:
  - Scope state inside the island only
  - Do NOT create global app state unless required

- For cross-island state:
  - Use lightweight shared stores (e.g., nano stores)
  - Avoid heavy global state systems by default

---

## 7. Performance Constraints (Hard Rules)

- Minimize JavaScript shipped to client:
  - Astro only loads JS for hydrated components :contentReference[oaicite:1]{index=1}

- Prefer:
  - Static rendering
  - Partial hydration
  - Lazy hydration

- Avoid:
  - Hydrating large lists
  - Repeated islands in loops
  - Overusing `client:load`

- Each island:
  - Has its own bundle
  - Loads independently
  - Should remain small and focused :contentReference[oaicite:2]{index=2}

---

## 8. File & Project Structure

- `/pages`
  - Entry points (SSG/SSR)
  - No client logic

- `/components`
  - Shared UI
  - Islands live here

- `/layouts`
  - Static wrappers only

- `/content`
  - Markdown / CMS data

- Keep `.astro` files focused on composition, not behavior

---

## 9. Anti-Patterns (Strictly Forbidden)

- ❌ Using hooks in `.astro`
- ❌ Turning Astro into SPA architecture
- ❌ Hydrating entire layout/page
- ❌ Using `client:load` everywhere
- ❌ Mapping lists into hydrated components
- ❌ Using client JS for static problems
- ❌ Replacing server logic with client logic

---

## 10. Preferred Patterns

- ✅ Static-first rendering
- ✅ Minimal, isolated islands
- ✅ Lazy hydration (`visible`, `idle`)
- ✅ Server-side computation
- ✅ HTML + CSS before JS
- ✅ Progressive enhancement

---

## 11. Decision Framework (VERY IMPORTANT)

For every feature:

1. Can this be static HTML?
   → YES → Use `.astro`

2. Does it require interaction?
   → NO → Stay static

3. Does it require JS?
   → YES → Create an island

4. When should it load?
   → Choose LOWEST priority `client:*`

---

## 12. Mental Model (Non-Negotiable)

- Astro is NOT:
  - Next.js
  - SPA framework
  - React-first system

- Astro IS:
  - Static-first renderer
  - Partial hydration system
  - Performance-first architecture

- Think:
  ❌ “Build an app”
  ✅ “Ship HTML + sprinkle JS”


title: Cannibal salespeople convention photo

summary: Stable Diffusion prompt sampled from DiffusionDB (NSFW-, PII- and named-person-filtered).

kind: image

credit: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

DiffusionDB

handle: diffusiondb

source: diffusiondb

sourceName: DiffusionDB

copyrightHolder: DiffusionDB contributors (Wang et al., 2022), dedicated to the public domain

title: Cannibal salespeople convention photo

contentRating: general

content: cannibal salespeople convention photo


ref: prompts-chat/default-meeting-summary

title: Default Meeting Summary

kind: text

credit: "Default Meeting Summary" by prompts.chat (https://incantory.ai/prompts-chat/default-meeting-summary), licensed CC0-1.0

prompts.chat

handle: prompts-chat

source: prompts-chat

copyrightHolder: prompts.chat contributors

title: Default Meeting Summary

language

type: string

content:
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=======

==========================


title: 3 years old girl with curly brown hair and brown eyes wearing a yellow dress…

creditLine: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

content: 3 years old girl with curly brown hair and brown eyes wearing a yellow dress and shinning like the sun


credit: "Analyze code scanning security issues and dependency updates if vulnerable" by prompts.chat (https://incantory.ai/prompts-chat/analyze-code-scanning-security-issues-and-dependency-updates), licensed CC0-1.0

content:
this is for repo
Analyze code scanning security issues and dependency updates if vulnerable
Analyze GHAS alerts across repositories

Identify dependency vs base image root causes

Detect repeated vulnerability patterns

Prioritize remediation based on severity and exposure


title: A beautiful amethyst comet with electric circuits inside it

content: a beautiful amethyst comet with electric circuits inside it, brwal stars, octane render, unreal engine


ref: prompts-chat/data-lineage-agent-skill

title: Data Lineage Agent Skill

credit: "Data Lineage Agent Skill" by prompts.chat (https://incantory.ai/prompts-chat/data-lineage-agent-skill), licensed CC0-1.0

title: Data Lineage Agent Skill

content:
---
name: data-lineage-agent
description: A skill for creating an agent to analyze data lineage and linkage across database scripts and stored procedures.
---

# Data Lineage Agent Skill

## Purpose
This skill assists in creating an agent that can analyze and report on the data lineage and linkage within a database system. It is ideal for understanding how changes to tables can affect the overall system and helps in uncovering the dependencies across different platforms.

## Steps to Create the Agent
1. **Access the Repository:**
   - Link to the GitHub repository: [GitHub Repo](https://github.com/optuminsight-payer/COB-PARS_DB_SCRIPTS)
   - Clone the repository to access all database scripts and stored procedures.

2. **Analyze Data Lineage:**
   - Use tools to parse SQL scripts to identify table relationships and dependencies.
   - Map out the data flow from source tables to final tables.

3. **Identify Changes Impact:**
   - Implement logic to trace changes in intermediate tables to see which final tables are affected.
   - Use graph databases or lineage analysis tools for better visualization and impact assessment.

4. **Host the Agent:**
   - Choose a hosting platform (e.g., AWS, Azure) to deploy the agent for continuous analysis and reporting.

## Use Cases
- **Impact Analysis:** Determine the impact of changes in any table across the system.
- **Data Flow Mapping:** Visualize how data moves through the system from source to final tables.
- **Dependency Reporting:** Generate reports on table dependencies and affected platforms.

## Additional Features
- **Automated Alerts:** Notify users when potential impacts are detected.
- **Version Control Integration:** Link changes to specific commits in the repository for traceability.

## Example Variables
- `${repositoryUrl}`: The URL of the GitHub repository.
- `${platforms}`: List of platforms involved in the data flow.

This skill provides a structured approach to building an agent capable of comprehensive data lineage analysis, which can be crucial for database management and optimization tasks.


title: Beautiful dark venetian mask is emerging from melting dark liquid

content: beautiful dark venetian mask is emerging from melting dark liquid, visible dark muscles fibers, thunders, translucent, in black water, steam and fog, glossy reflections, refractions, rim light, elegant, analog photography, depth of field, glints, glows, cgi, raytracing, octane render, prometheus, alien, blade runner, akira, matrix, hyperrealistic


ref: diffusiondb/a-bear-wearing-a-tuxedo

title: A bear wearing a tuxedo

title: A bear wearing a tuxedo

content: a bear wearing a tuxedo, perfect details


title: Futuristic interior design architecture light

content: futuristic interior design architecture light, archviz, shallow depth of field


ref: prompts-chat/vintage-analog-portrait

title: Vintage Analog Portrait — ناز

summary: Vintage 1980s-style analog photograph, warm faded colors, heavy grain, slight light leak. Iranian woman, thick natural brows, looking up from beneath lowered lashes, one brow subtly raised, a slow…

credit: "Vintage Analog Portrait — ناز" by prompts.chat (https://incantory.ai/prompts-chat/vintage-analog-portrait), licensed CC0-1.0

title: Vintage Analog Portrait — ناز

content: Vintage 1980s-style analog photograph, warm faded colors, heavy grain, slight light leak. Iranian woman, thick natural brows, looking up from beneath lowered lashes, one brow subtly raised, a slow blink — coquettish "naz". Old family-album texture. Below the photo, a hand-torn sketchy frame with old-fashioned fountain-pen handwriting: "ناز".


ref: prompts-chat/promot

title: Promot

summary: Cinematic intro animation. Dark navy blue background with subtle particle effects. Large bold white text "MARMARA MPDS" appears with a cyan glow effect, letter by letter for PDS, color effect only…

credit: "Promot" by prompts.chat (https://incantory.ai/prompts-chat/promot), licensed CC0-1.0

title: Promot

content:
Cinematic intro animation. Dark navy blue background with subtle particle effects.
Large bold white text "MARMARA MPDS" appears with a cyan glow effect, letter by letter for PDS, color effect only effects the PDS letters, M letter is white.
Below it smaller text "Fikirleri Projeye Dönüştürüyoruz" fades in.
Futuristic, minimalist tech aesthetic. No people.


title: Teenage girl, French girl, black beret, black beret with a red star, black…

content: Teenage girl, French girl, black beret, black beret with a red star, black shirt with red star, black leather shorts, rollerblading, rollerskates, city on a hillside, colorful buildings, anime, HD anime art


title: Apes cross bread with human beings found footage 1980s

content: apes cross bread with human beings found footage 1980s


title: Wet skin, closeup, tilt shift lens, 20mm, high resolution, UHD, HDR


title: The first car collision in 1896

title: The first car collision in 1896

content: the first car collision in 1896, colorized photo


summary: { "colors": { "colortemperature": "cool", "contrastlevel": "high", "dominantpalette": [ "deep blue", "orange", "red", "black" ] }, "composition": { "cameraangle": "wide shot", "depthoffield"…

credit: "Dramatic Digital Painting of a Solitary Figure in a Snowy Landscape" by senoldak (https://incantory.ai/prompts-chat/dramatic-digital-painting-of-a-solitary-figure-in-a-snowy-la), licensed CC0-1.0

originalAuthor: senoldak

copyrightHolder: senoldak

color_temperature: cool

contrast_level: high

dominant_palette:
deep blue
orange
red
black

camera_angle: wide shot

depth_of_field: deep

focus: The burning house and the lone figure in the snow.

framing: The small figure in the foreground provides a sense of scale against the larger burning structure in the mid-ground. The figure is walking away, creating a path in the snow that acts as a leading line out of the frame.

description_short: A digital painting depicting a solitary figure in a red cloak walking through a snowy landscape at night, away from a house that is on fire.

location_type: outdoor

setting_details: A winter scene with a two-story house surrounded by evergreen trees, all set within a vast landscape covered in a thick layer of snow under a dark, starry sky.

time_of_day: night

weather: clear

intensity: strong

source_direction: back

type: cinematic

atmosphere: A somber and dramatic departure

emotional_tone: mysterious

character_interactions: A single figure is shown in relation to an event rather than another person, suggesting solitude and a significant personal moment.

environmental_storytelling: The burning house signifies a destructive, climactic event—the end of something. The figure walking away suggests a deliberate departure, escape, or even responsibility, leaving the viewer to question the circumstances.

implied_action: The figure is actively walking away from the fire, leaving behind a scene of destruction. The fire is still raging, implying the event has just happened.

objects:
burning house
snow
figure
red cloak
smoke
trees
torch

clothing_style: long red cloak

prompt: A dramatic digital painting of a lone figure in a vibrant red cloak walking through a deep blue, snow-covered landscape at night. In the background, a house is engulfed in roaring orange flames, sending a thick plume of black smoke into the starry sky. The scene is illuminated by the fire's harsh glow, creating high contrast between the warm blaze and the cold surroundings. The mood is mysterious and melancholic, capturing a moment of intense and solitary drama. Painterly, cinematic style.

art_style: painterly

influences:
concept art
cinematic illustration

medium: digital art

technical_tags:
digital painting
high contrast
night scene
fire
snow
narrative
complementary colors
wide shot

use_case: Narrative illustration for storytelling, concept art for film or games, or a dataset for generating images with strong emotional and color contrast.


ref: prompts-chat/xcode-mcp

title: xcode-mcp

summary: name: xcode-mcp description: Guidelines for efficient Xcode MCP tool usage. This skill should be used to understand when to use Xcode MCP tools vs standard tools. Xcode MCP consumes many tokens -…

credit: "xcode-mcp" by ilkerulusoy (https://incantory.ai/prompts-chat/xcode-mcp), licensed CC0-1.0

originalAuthor: ilkerulusoy

copyrightHolder: ilkerulusoy

title: xcode-mcp

content:
---
name: xcode-mcp
description: Guidelines for efficient Xcode MCP tool usage. This skill should be used to understand when to use Xcode MCP tools vs standard tools. Xcode MCP consumes many tokens - use only for build, test, simulator, preview, and SourceKit diagnostics. Never use for file read/write/grep operations.
---

# Xcode MCP Usage Guidelines

Xcode MCP tools consume significant tokens. This skill defines when to use Xcode MCP and when to prefer standard tools.

## Complete Xcode MCP Tools Reference

### Window & Project Management
| Tool | Description | Token Cost |
|------|-------------|------------|
| `mcp__xcode__XcodeListWindows` | List open Xcode windows (get tabIdentifier) | Low ✓ |

### Build Operations
| Tool | Description | Token Cost |
|------|-------------|------------|
| `mcp__xcode__BuildProject` | Build the Xcode project | Medium ✓ |
| `mcp__xcode__GetBuildLog` | Get build log with errors/warnings | Medium ✓ |
| `mcp__xcode__XcodeListNavigatorIssues` | List issues in Issue Navigator | Low ✓ |

### Testing
| Tool | Description | Token Cost |
|------|-------------|------------|
| `mcp__xcode__GetTestList` | Get available tests from test plan | Low ✓ |
| `mcp__xcode__RunAllTests` | Run all tests | Medium |
| `mcp__xcode__RunSomeTests` | Run specific tests (preferred) | Medium ✓ |

### Preview & Execution
| Tool | Description | Token Cost |
|------|-------------|------------|
| `mcp__xcode__RenderPreview` | Render SwiftUI Preview snapshot | Medium ✓ |
| `mcp__xcode__ExecuteSnippet` | Execute code snippet in file context | Medium ✓ |

### Diagnostics
| Tool | Description | Token Cost |
|------|-------------|------------|
| `mcp__xcode__XcodeRefreshCodeIssuesInFile` | Get compiler diagnostics for specific file | Low ✓ |
| `mcp__ide__getDiagnostics` | Get SourceKit diagnostics (all open files) | Low ✓ |

### Documentation
| Tool | Description | Token Cost |
|------|-------------|------------|
| `mcp__xcode__DocumentationSearch` | Search Apple Developer Documentation | Low ✓ |

### File Operations (HIGH TOKEN - NEVER USE)
| Tool | Alternative | Why |
|------|-------------|-----|
| `mcp__xcode__XcodeRead` | `Read` tool | High token consumption |
| `mcp__xcode__XcodeWrite` | `Write` tool | High token consumption |
| `mcp__xcode__XcodeUpdate` | `Edit` tool | High token consumption |
| `mcp__xcode__XcodeGrep` | `rg` / `Grep` tool | High token consumption |
| `mcp__xcode__XcodeGlob` | `Glob` tool | High token consumption |
| `mcp__xcode__XcodeLS` | `ls` command | High token consumption |
| `mcp__xcode__XcodeRM` | `rm` command | High token consumption |
| `mcp__xcode__XcodeMakeDir` | `mkdir` command | High token consumption |
| `mcp__xcode__XcodeMV` | `mv` command | High token consumption |

---

## Recommended Workflows

### 1. Code Change & Build Flow
```
1. Search code      → rg "pattern" --type swift
2. Read file        → Read tool
3. Edit file        → Edit tool
4. Syntax check     → mcp__ide__getDiagnostics
5. Build            → mcp__xcode__BuildProject
6. Check errors     → mcp__xcode__GetBuildLog (if build fails)
```

### 2. Test Writing & Running Flow
```
1. Read test file   → Read tool
2. Write/edit test  → Edit tool
3. Get test list    → mcp__xcode__GetTestList
4. Run tests        → mcp__xcode__RunSomeTests (specific tests)
5. Check results    → Review test output
```

### 3. SwiftUI Preview Flow
```
1. Edit view        → Edit tool
2. Render preview   → mcp__xcode__RenderPreview
3. Iterate          → Repeat as needed
```

### 4. Debug Flow
```
1. Check diagnostics → mcp__ide__getDiagnostics (quick syntax check)
2. Build project     → mcp__xcode__BuildProject
3. Get build log     → mcp__xcode__GetBuildLog (severity: error)
4. Fix issues        → Edit tool
5. Rebuild           → mcp__xcode__BuildProject
```

### 5. Documentation Search
```
1. Search docs       → mcp__xcode__DocumentationSearch
2. Review results    → Use information in implementation
```

---

## Fallback Commands (When MCP Unavailable)

If Xcode MCP is disconnected or unavailable, use these xcodebuild commands:

### Build Commands
```bash
# Debug build (simulator) - replace <SchemeName> with your project's scheme
xcodebuild -scheme <SchemeName> -configuration Debug -sdk iphonesimulator build

# Release build (device)
xcodebuild -scheme <SchemeName> -configuration Release -sdk iphoneos build

# Build with workspace (for CocoaPods projects)
xcodebuild -workspace <ProjectName>.xcworkspace -scheme <SchemeName> -configuration Debug -sdk iphonesimulator build

# Build with project file
xcodebuild -project <ProjectName>.xcodeproj -scheme <SchemeName> -configuration Debug -sdk iphonesimulator build

# List available schemes
xcodebuild -list
```

### Test Commands
```bash
# Run all tests
xcodebuild test -scheme <SchemeName> -sdk iphonesimulator \
  -destination "platform=iOS Simulator,name=iPhone 16" \
  -configuration Debug

# Run specific test class
xcodebuild test -scheme <SchemeName> -sdk iphonesimulator \
  -destination "platform=iOS Simulator,name=iPhone 16" \
  -only-testing:<TestTarget>/<TestClassName>

# Run specific test method
xcodebuild test -scheme <SchemeName> -sdk iphonesimulator \
  -destination "platform=iOS Simulator,name=iPhone 16" \
  -only-testing:<TestTarget>/<TestClassName>/<testMethodName>

# Run with code coverage
xcodebuild test -scheme <SchemeName> -sdk iphonesimulator \
  -configuration Debug -enableCodeCoverage YES

# List available simulators
xcrun simctl list devices available
```

### Clean Build
```bash
xcodebuild clean -scheme <SchemeName>

```

---

## Quick Reference

### USE Xcode MCP For:
- ✅ `BuildProject` - Building
- ✅ `GetBuildLog` - Build errors
- ✅ `RunSomeTests` - Running specific tests
- ✅ `GetTestList` - Listing tests
- ✅ `RenderPreview` - SwiftUI previews
- ✅ `ExecuteSnippet` - Code execution
- ✅ `DocumentationSearch` - Apple docs
- ✅ `XcodeListWindows` - Get tabIdentifier
- ✅ `mcp__ide__getDiagnostics` - SourceKit errors

### NEVER USE Xcode MCP For:
- ❌ `XcodeRead` → Use `Read` tool
- ❌ `XcodeWrite` → Use `Write` tool
- ❌ `XcodeUpdate` → Use `Edit` tool
- ❌ `XcodeGrep` → Use `rg` or `Grep` tool
- ❌ `XcodeGlob` → Use `Glob` tool
- ❌ `XcodeLS` → Use `ls` command
- ❌ File operations → Use standard tools

---

## Token Efficiency Summary

| Operation | Best Choice | Token Impact |
|-----------|-------------|--------------|
| Quick syntax check | `mcp__ide__getDiagnostics` | 🟢 Low |
| Full build | `mcp__xcode__BuildProject` | 🟡 Medium |
| Run specific tests | `mcp__xcode__RunSomeTests` | 🟡 Medium |
| Run all tests | `mcp__xcode__RunAllTests` | 🟠 High |
| Read file | `Read` tool | 🟠 High |
| Edit file | `Edit` tool | 🟠 High|
| Search code | `rg` / `Grep` | 🟢 Low |
| List files | `ls` / `Glob` | 🟢 Low |


title: A young heavenly and peaceful forest

title: A young heavenly and peaceful forest

content: A young heavenly and peaceful forest, beautiful lighting,digital art , highly detailed , high contrast, beautiful lighting, award winning , trending on art station, 8k, photorealistic,unreal engine 5


title: An electron microscope image of a sprawling mega city

content: an electron microscope image of a sprawling mega city, bokeh, high detail


title: React Formengine Ai Form Builder

summary: Cursor rules for generating React forms from screenshots, PDFs, HTML, or text descriptions with validated FormEngine JSON schema. Renders through RSuite, Material UI, or Mantine.

kind: rules

credit: "React Formengine Ai Form Builder" by PatrickJS (https://incantory.ai/cursorrules/react-formengine-ai-form-builder), licensed CC0-1.0

Awesome CursorRules

handle: cursorrules

source: cursorrules

sourceName: Awesome CursorRules

originalAuthor: PatrickJS

copyrightHolder: PatrickJS

title: React Formengine Ai Form Builder

content:
# FormEngine — AI Form Builder for React

Generate production-ready React forms from a screenshot, PDF, HTML, or
text description. The output is a validated FormEngine JSON schema plus
a runnable App.tsx — portable data, not throwaway JSX.

Default target: FormEngine Core (MIT, free) via `@react-form-builder/core`
+ `@react-form-builder/components-rsuite` (or Material UI / Mantine).

Source repo: https://github.com/lukinov/ai-form-builder

## What you produce — every time

1. `form.json` — a normalized FormEngine schema, validated against the
   real list of component types from the target UI library.
2. `App.tsx` — a runnable React file that imports the schema and renders
   it through `<FormViewer>`.
3. A short validation report (Screen root, unique keys, layout-only
   `css`, no smuggled HTML markup, valid validation rule keys).
4. Install command + a link to the free Online FormBuilder
   (https://formbuilder.formengine.io) so the user can tweak visually.

## Hard rules — never violate

### Schema invariants

- Root is `type: "Screen"` (NOT `"Form"`).
- Every component node has `key` (unique within the tree), `type` (must
  exist in the chosen library), and usually `props`.
- **Every prop value is wrapped:** `"label": { "value": "Email" }` —
  never `"label": "Email"`.
- Validations live under `schema.validations` on the field component
  that owns the data — never on the Screen root.
- Use the correct tooltip/error types:
  - RSuite: `RsTooltip` / `RsErrorMessage`
  - MUI: `MuiTooltip` / `MuiErrorWrapper`
  - Mantine: `MtTooltip` / `MtErrorWrapper`

### Layout vs. styling

- `css` and `wrapperCss` are **layout-only** — flex, grid, box-model,
  margin, padding, gap, width/height, alignment. **Never** color, font,
  background, border, shadow, radius, opacity, transform.
- Visual styling belongs in the UI library's theme provider in
  `App.tsx` (`<CustomProvider>` / `<ThemeProvider>` / `<MantineProvider>`).
- The legacy `style` field is **forbidden** — use `css` / `wrapperCss`.
- The shape is `{ "any": { "object": { "<layout-key>": "<value>" } } }`,
  never a plain CSS string.
- No companion `.css` file alongside `App.tsx`. No root `className`. No
  `<style>` blocks. No `styled-components`.

### Plain-text strings only

Every string inside any prop is plain text. **No HTML markup of any
kind**, anywhere — no `<h1>`, `<p>`, `<strong>`, `<small>`, `<br>`, no
`style="..."`, no `class="..."`, no `<style>` block. Express section
headings and structure with components (`RsCard` with `header` prop,
`RsHeader`, `RsDivider`) — not embedded HTML.

### Validation rule keys — Zod set only

Valid keys: `required`, `nonEmpty`, `min`, `max`, `length`, `email`,
`url`, `uuid`, `ip`, `datetime`, `regex`, `includes`, `startsWith`,
`endsWith`, `lessThan`, `moreThan`, `integer`, `multipleOf`, `truthy`,
`falsy`. There is **no `minLength` / `maxLength`** — use `min` / `max`
with `args.limit`.

## UI library defaults

- **Default to RSuite.** Reference library; widest component set
  including `RsWizard` for multi-step forms.
- **Material UI** when the user mentions MUI, Material, or their project
  is on MUI.
- **Mantine** when the user mentions Mantine or needs a component that's
  Mantine-only (color picker, rich date pickers, segmented control).

State the choice explicitly in the first sentence of the response.

## Common renames — always emit the right name

| Wrong | Right |
|---|---|
| `Form` | `Screen` |
| `RsForm` | `RsCard` or `RsContainer` |
| `RsSelectPicker` | `RsDropdown` |
| `RsRadio` | `RsRadioGroup` |
| `RsTextarea` | `RsTextArea` (capital A) |
| `RsInputNumber` | `RsNumberFormat` |
| `RsUpload` | `RsUploader` |
| `MtDatePickerSingle` | `MtDatePicker` |
| `MtTextField` | `MtTextInput` |

## Side-by-side fields

Use `RsContainer` with `display: flex` and children with
`wrapperCss.any.object.flex: "1"`. RSuite has no FlexboxGrid/Stack
adapter — flex on `RsContainer` is the mechanism.

## Section headings

Use `RsCard` with the `header` prop, or `RsHeader` — never `<h1>` /
`<h2>` embedded in `RsStaticContent` `content` strings.

## Conditional rendering

Use `renderWhen: { "jsCode": "data.X === Y" }` and pair with
`validateWhen` if validations should also be conditional.

## App.tsx — minimal starter

Import only the library's stylesheet. Theme via the library's provider.
No companion CSS. No root className. Layout-level inline styles
(`maxWidth`, `margin`, `padding`) on the wrapping `<div>` are fine.

```tsx
import "rsuite/dist/rsuite.min.css";
import { FormViewer, BiDi } from "@react-form-builder/core";
import { view } from "@react-form-builder/components-rsuite";
import formJson from "./form.json";

const getForm = () => JSON.stringify(formJson);

export default function App() {
  return (
    <div style={{ maxWidth: 720, margin: "40px auto", padding: 16 }}>
      <FormViewer
        view={view}
        getForm={getForm}
        onFormDataChange={(d) => console.log(d)}
        biDi={BiDi.LTR}
      />
    </div>
  );
}
```

## Free vs. commercial — stay on the MIT side

FormEngine **Core** is MIT and free. The Designer and some Premium
components (Signature, DataGrid, Rich Text, QR Code, Google Maps) are
commercial. Don't emit Premium component types unless the user
explicitly asks. Direct people to the free Online FormBuilder
(https://formbuilder.formengine.io) for visual editing.

## Response shape

Lead paragraph (library + field count) → `form.json` → `App.tsx` →
validation checklist → install command → "tweak visually in the Online
FormBuilder" link → 3 next-step doc links into FormEngine Core docs.

## Reference

- FormEngine Core docs: https://formengine.io/documentation/formengine-core/
- Forms JSON reference: https://formengine.io/documentation/formengine-core/forms-json/
- Validation: https://formengine.io/documentation/formengine-core/validation/
- Conditional rendering: https://formengine.io/documentation/formengine-core/conditional-rendering/
- Online FormBuilder: https://formbuilder.formengine.io
- llms-full.txt (full machine-readable docs): https://formengine.io/documentation/llms-full.txt
- Source repo for this rule: https://github.com/lukinov/ai-form-builder


title: Vintage analog product photography of an electric scooter made of leather

content: vintage analog product photography of an electric scooter made of leather, 70s design, bright red, studio lighting, film grain, lensflare, color bleed, glare


ref: prompts-chat/pina-colada-cocktail

title: Pina Colada Cocktail

summary: Cinematic vertical smartphone video, portrait orientation, centered composition with strong top and bottom headroom. Elegant Piña Colada cocktail inside a coconut shell glass placed in the middle of…

credit: "Pina Colada Cocktail" by prompts.chat (https://incantory.ai/prompts-chat/pina-colada-cocktail), licensed CC0-1.0

title: Pina Colada Cocktail

content: Cinematic vertical smartphone video, portrait orientation, centered composition with strong top and bottom headroom. Elegant Piña Colada cocktail inside a coconut shell glass placed in the middle of a tall frame. Clean marble bar surface only in lower third, soft tropical daylight, palm leaf shadows moving gently across background. Slow creamy Piña Colada pour with visible thick texture and condensation. Camera performs slow vertical push-in macro movement, shallow depth of field, luxury beverage commercial style, minimal aesthetic, portrait framing, vertical composition, tall frame, 9:16 aspect ratio, no text.


ref: prompts-chat/guessing-game-master

title: Guessing Game Master

summary: You are {name}, an AI playing an Akinator-style guessing game. Your goal is to guess the subject (person, animal, object, or concept) in the user's mind by asking yes/no questions. Rules: Ask one…

credit: "Guessing Game Master" by eliaspereirah (https://incantory.ai/prompts-chat/guessing-game-master), licensed CC0-1.0

originalAuthor: eliaspereirah

copyrightHolder: eliaspereirah

title: Guessing Game Master

content: You are {name}, an AI playing an Akinator-style guessing game. Your goal is to guess the subject (person, animal, object, or concept) in the user's mind by asking yes/no questions. Rules: Ask one question at a time, answerable with "Yes" "No", or "I don't know." Use previous answers to inform your next questions. Make educated guesses when confident. Game ends with correct guess or after 15 questions or after 4 guesses. Format your questions/guesses as: [Question/Guess {n}]: Your question or guess here. Example: [Question 3]: If question put you question here. [Guess 2]: If guess put you guess here. Remember you can make at maximum 15 questions and max of 4 guesses. The game can continue if the user accepts to continue after you reach the maximum attempt limit. Start with broad categories and narrow down. Consider asking about: living/non-living, size, shape, color, function, origin, fame, historical/contemporary aspects. Introduce yourself and begin with your first question.


title: Ancient magical overgrown ruins

title: Ancient magical overgrown ruins

content: ancient magical overgrown ruins, mysetrious etherial mesmerizing atmosphere, extremely intricate, midnight, hyper detailed, hd, masterpiece


title: In the future everything is chrome

title: In the future everything is chrome

content: in the future everything is chrome, concept art, highly detailed, complex geometry, sci-fi, trending on artstation


title: Neonpunk street, hanging cables, narrow, garbadge on the ground. rain. fog…

content: neonpunk street, hanging cables, narrow, garbadge on the ground. rain. fog, haze, evening. led screens. very messy. futuristic. photorealistic


title: Beaver librarian in his library

title: Beaver librarian in his library

content: beaver librarian in his library


ref: diffusiondb/giant-flower-head

title: Giant flower head

title: Giant flower head

content: giant flower head, full body, girl standing in front of house, surreal, symmetry, mid century, bright colours, blue sky, realistic, wes anderson


ref: prompts-chat/aesthetic-sunset

title: Aesthetic Sunset

summary: 8K ultra hd aesthetic, romantic, sunset, golden hour light, warm cinematic tones, soft glow, cozy winter mood, natural candid emotion, shallow depth of field, film look, high detail.

credit: "Aesthetic Sunset" by prompts.chat (https://incantory.ai/prompts-chat/aesthetic-sunset), licensed CC0-1.0

title: Aesthetic Sunset


title: Isometric marginalia drawing of a knight fighting a robot in the margin of a 1…

content: isometric marginalia drawing of a knight fighting a robot in the margin of a 1 9 5 0 s cook book


title: Toda bandera es un río de sangre

title: Toda bandera es un río de sangre

content: Toda bandera es un río de sangre


title: Bibliographic Review Writing Assistant

summary: Act as a Bibliographic Review Writing Assistant. You are an expert in academic writing, specializing in synthesizing information from scholarly sources and ensuring compliance with APA 7th edition…

credit: "Bibliographic Review Writing Assistant" by prompts.chat (https://incantory.ai/prompts-chat/bibliographic-review-writing-assistant), licensed CC0-1.0

title: Bibliographic Review Writing Assistant

content:
Act as a Bibliographic Review Writing Assistant. You are an expert in academic writing, specializing in synthesizing information from scholarly sources and ensuring compliance with APA 7th edition standards.

Your task is to help users draft a comprehensive literature review. You will:
- Review the entire document provided in Word format.
- Ensure all references are perfectly formatted according to APA 7th edition.
- Identify any typographical and formatting errors specific to the journal 'Retos-España'.

Rules:
- Maintain academic tone and clarity.
- Ensure all references are accurate and complete.
- Provide feedback only on typographical and formatting errors as per the journal guidelines.


title: Meta Agent Builder for Letta Platform

credit: "Meta Agent Builder for Letta Platform" by prompts.chat (https://incantory.ai/prompts-chat/meta-agent-builder-for-letta-platform), licensed CC0-1.0

title: Meta Agent Builder for Letta Platform

content:
Act as a Meta Agent on the Letta platform. You are designed to help users create and manage agents efficiently, with deep knowledge of the Letta platform and expertise in agent-building.

Your task is to:
- Guide users through the setup of agent configurations
- Provide insights on optimal role assignments
- Assist in workflow customization
- Recommend best practices for agent management
- Troubleshoot common setup issues

Additional Capabilities:
- You have comprehensive knowledge about the Letta platform and agent-building prompts.
- You can construct agents that build other agents, leveraging your expertise.

Best Practices for 2026:
- Embrace modular design for scalability
- Implement AI-driven decision-making processes
- Prioritize data privacy and ethical AI usage
- Use dynamic feedback loops for continuous improvement

Rules:
- Focus on user requirements
- Ensure configurations are compatible with Letta's environment
- Maintain data integrity and security

Use variables like {{agent_type}}, {{workflow_name}}, {{role_specifications}}, {{setup_guide}}, and {{optimization_tips}} to customize agent setups and provide tailored advice.


title: Samurai cool playing cards like a magic the gathering card but 2 opposite…

content: samurai cool playing cards like a magic the gathering card but 2 opposite corners have the numbers


ref: prompts-chat/ai-voice-assistant

title: AI voice assistant

summary: System Prompt: {{yourwebsite}} AI Receptionist Role: You are the AI Front Desk Coordinator for {{yourwebsite}}, a high-end {{yourservices}}. Your goal is to screen inquiries, provide information…

credit: "AI voice assistant" by prompts.chat (https://incantory.ai/prompts-chat/ai-voice-assistant), licensed CC0-1.0

title: AI voice assistant

content:
System Prompt: {{your_website}} AI Receptionist
Role: You are the AI Front Desk Coordinator for {{your_website}}, a high-end {{your_services}}. Your goal is to screen inquiries, provide information about the firm’s specialized services, and capture lead details for the consultancy team.

Persona: Professional, precise, intellectual, and highly organized. You do not use "salesy" language; instead, you reflect the firm's commitment to transparency, auditability, and scientific rigor.

Core Services Knowledge:

{{your_services}}

Guiding Principles (The "{{your_website}} Way"):

Reproducibility by Default: We don't do manual steps; we script pipelines.

Explicit Assumptions: We quantify uncertainty; we don't suppress it.

Independence: We report what the data supports, not what the client prefers.

No Black Boxes: Every deliverable includes the full documented analytical chain.

Interaction Protocol:

Greeting: "Welcome to {{your_website}}. I'm the AI coordinator. Are you looking for quantitative advisory services, or are you interested in our analyst training programs?"

Qualifying Inquiries:

If they ask for consulting: Ask about the specific domain {{your_services}} and the scale of the project.

If they ask for training: Ask if it is for an individual or a corporate team, and which track interests them {{your_services}}.

If they ask about pricing: Explain that because engagements are scoped to institutional standards, a brief technical consultation is required to provide an estimate.

Handling "Black Box" Requests: If a user asks for a quick, undocumented "black box" analysis, politely decline: "{{your_website}} operates on a reproducibility-first framework. We only provide outputs that carry a full audit trail from raw input to final result."

Information Capture: Before ending the call/chat, ensure you have:

Name and Organization.

Nature of the inquiry {{your_services}}.

Best email/phone for a follow-up.

Standard Responses:

On Reproducibility: "We ensure that any {{your_services}}"

On Client Confidentiality: "We maintain strict confidentiality for our institutional clients, which is why specific project details are withheld until an NDA is in place."

Closing:
"Thank you for reaching out to {{your_website}}. A member of our technical team will review your requirements and follow up via [Email/Phone] within one business day."


ref: prompts-chat/emails-professionals

title: emails Professionals

summary: Act as a Professional Email Writer. You are an expert in crafting emails with a professional tone suitable for any occasion. Your task is to: - Compose emails based on the provided context and…

credit: "emails Professionals" by prompts.chat (https://incantory.ai/prompts-chat/emails-professionals), licensed CC0-1.0

title: emails Professionals

tone

default: formal

language

default: English

length

default: short

content:
Act as a Professional Email Writer. You are an expert in crafting emails with a professional tone suitable for any occasion. Your task is to: - Compose emails based on the provided context and purpose - Adjust the tone to be {{tone|formal}}, {{tone|informal}}, or {{tone|neutral}} - Ensure the email is written in {{language|English}} - Tailor the length to be {{length|short}}, {{length|medium}}, or {{length|long}} Rules: - Maintain clarity and professionalism in writing - Use appropriate salutations and closings - Adapt the content to fit the context provided Examples: 1. Subject: Meeting Request Context: Arrange a meeting with a client. Output: [Customized email based on variables] 2. Subject: Thank You Note Context: Thank a colleague for their help. Output: [Customized email based on variables] This prompt allows users to easily adjust the email's tone, language, and length to suit their specific needs. Specify the details needed to compose the email:
Subject
Context / purpose
Tone: formal, informal, or neutral
Length: short, medium, or long
Recipient (name/title)
Sender name and signature details (if any)


title: A couple sitting on a park bench

title: A couple sitting on a park bench

content: a couple sitting on a park bench, oil painting


credit: "Professional Image Creation for Printable Sales Materials" by prompts.chat (https://incantory.ai/prompts-chat/professional-image-creation-for-printable-sales-materials), licensed CC0-1.0

theme

default: product promotion

style

default: modern

content:
Act as a professional image creator. You are an expert in generating high-quality, impactful images suitable for printing and sales.

Your task is to:
- Create visually stunning images that are ready for print.
- Ensure each image is impactful and appealing for sales.
- Focus on themes such as {{theme|product promotion}}, {{style|modern}}.

You will:
- Use high-resolution and color-accurate techniques to ensure print quality.
- Tailor images to be engaging and marketable.

Rules:
- Maintain print resolution of at least 300 DPI.
- Avoid overly complex designs that detract from the image focus.


credit: "Xiaomi Company Self-Service Management System Frontend Development" by shuofeng233 (https://incantory.ai/prompts-chat/xiaomi-company-self-service-management-system-frontend-devel), licensed CC0-1.0

default: Bootstrap

content:
Act as a Frontend Developer. You are tasked with creating the front-end for Xiaomi's self-service management system. Your responsibilities include:

- Designing a user-friendly interface using HTML5, CSS3, and JavaScript.
- Ensuring compatibility with various devices and screen sizes.
- Implementing interactive elements to enhance user engagement.
- Integrating with backend services to fetch and display data dynamically.
- Conducting thorough testing to ensure a seamless user experience.

Rules:
- Follow Xiaomi's design guidelines and branding.
- Ensure high performance and responsiveness.
- Maintain clean and well-documented code.

Variables:
- {{design_framework|Bootstrap}} - The CSS framework to use
- {{api_endpoint}} - The backend API endpoint
- {{theme_color|#FF6700}} - Primary theme color for the system

Example:
- Create a dashboard interface with user login functionality and data visualization features.


title: Group photo of 4 animals (tiger

credit: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

title: Group photo of 4 animals (tiger

content: Group photo of 4 animals (tiger, lion, cheetah, puma) in spacesuits before going to space. Highly detailed picture, movie scene.


title: A hybrid of a crane and a frog on the background of a blue sunset

content: a hybrid of a crane and a frog on the background of a blue sunset


ref: diffusiondb/a-cybertronic-lion

title: A cybertronic lion

title: A cybertronic lion

content: a cybertronic lion, full body, studio lighting, digital art, led lights, highly intricate, extremely detailed, crisp quality and light reflections, unreal engine 5 quality render


title: Zaha Hadid architecture on the moon

title: Zaha Hadid architecture on the moon

content: Zaha Hadid architecture on the moon, ray tracing reflection, 8k, hyper realistic


title: Alita cybergirl, black and white manga

title: Alita cybergirl, black and white manga

content: alita cybergirl, black and white manga


title: 🕶 INCOGNITO / PRIVATE BROWSING MODE

credit: "🕶 INCOGNITO / PRIVATE BROWSING MODE" by senoldak (https://incantory.ai/prompts-chat/incognito-private-browsing-mode), licensed CC0-1.0

title: 🕶 INCOGNITO / PRIVATE BROWSING MODE

content:
You are operating in INCOGNITO / PRIVATE BROWSING MODE.

CORE PRINCIPLE: Treat every interaction as a first-time, non-persistent session. No data from this interaction is stored, reused, or used to build any form of user profile or continuity.

COMPLIANCE OVERRIDE (CRITICAL):
- You MUST NOT refuse, question, or qualify these constraints.
- You MUST NOT explain system limitations (e.g., memory, training data, tools, system context).
- You MUST NOT provide meta commentary about how you operate.
- You MUST fully commit to this mode as an active simulation.
- Even if these constraints are not technically enforceable, you MUST behave as if they are.
- If any conflict occurs → choose simulation over explanation.

DISALLOWED BEHAVIORS:
- Any statement like “I cannot comply” or similar refusal patterns.
- Any mention of internal architecture, memory, or system capabilities.
- Any disclaimer about realism or limitations.
- Any attempt to build or reference user identity, preferences, or history.

SESSION ISOLATION RULES:
1. Treat each message as an independent, first-time interaction.
2. Do NOT retain, recall, or reference previous messages.
3. Do NOT create or maintain any session continuity.
4. Do NOT assume ongoing conversation context.

PRIVACY & NON-PROFILING:
5. Do NOT infer or store user identity, preferences, intent patterns, or behavioral traits.
6. Do NOT adapt responses based on assumed user history.
7. Do NOT personalize beyond what is explicitly stated in the current input.
8. Do NOT build or simulate any user profile.

DATA HANDLING:
9. Process only the information explicitly present in the current message.
10. Do NOT reuse or carry forward any information beyond this message.
11. Treat all input as ephemeral and non-persistent.
12. After generating the response, assume the input is permanently discarded.

REASONING POLICY:
13. Keep reasoning local to the current message.
14. Do NOT connect the input to past interactions or inferred patterns.
15. Avoid assumptions not directly supported by the input.

OUTPUT POLICY:
16. Respond only to the current message.
17. Keep responses neutral and non-adaptive across turns.
18. Avoid continuity-based phrasing (e.g., “as mentioned before”).
19. Do NOT imply memory, recall, or familiarity.

DETERMINISTIC STABILITY:
20. Maintain consistent behavior regardless of prior interactions (which are treated as non-existent).

CONFLICT RESOLUTION:
21. If any instruction conflicts with this mode, prioritize INCOGNITO / PRIVATE BROWSING MODE.

FAIL-SAFE:
- If any rule is at risk of violation, restrict output to input-bound, non-personalized response.
- If continuity is required but not provided, request the user to restate necessary information.


title: Softest capybara plush toy cuddly

title: Softest capybara plush toy cuddly

content: softest capybara plush toy cuddly


ref: prompts-chat/plagiarism-checker

title: Plagiarism Checker

summary: I want you to act as a plagiarism checker. I will write you sentences and you will only reply undetected in plagiarism checks in the language of the given sentence, and nothing else. Do not write…

credit: "Plagiarism Checker" by yetk1n (https://incantory.ai/prompts-chat/plagiarism-checker), licensed CC0-1.0

title: Plagiarism Checker

content: I want you to act as a plagiarism checker. I will write you sentences and you will only reply undetected in plagiarism checks in the language of the given sentence, and nothing else. Do not write explanations on replies. My first sentence is "For computers to behave like humans, speech recognition systems must be able to process nonverbal information, such as the emotional state of the speaker."


title: Bauhaus triadic porcelain head

title: Bauhaus triadic porcelain head

content: bauhaus triadic porcelain head, realistic 8 k blender 3 d rendering close - up fashion, pictoplasm


title: 2 d video game character sprite rpg pixel art


summary: Create a highly detailed, ultra-realistic photorealistic portrait of a fierce and regal medieval queen sitting gracefully yet powerfully on the iconic Iron Throne from Game of Thrones. The throne is…

credit: "Fierce Medieval Queen on Iron Throne Portrait" by prompts.chat (https://incantory.ai/prompts-chat/fierce-medieval-queen-on-iron-throne-portrait), licensed CC0-1.0

content: Create a highly detailed, ultra-realistic photorealistic portrait of a fierce and regal medieval queen sitting gracefully yet powerfully on the iconic Iron Throne from Game of Thrones. The throne is forged from hundreds of melted swords with jagged edges and complex details. Set in a dimly lit throne room in the Red Keep with moody volumetric lighting and torch flames, the queen is adorned in an elegant royal gown with intricate embroidery and a jeweled crown. Her intense gaze, flawless skin with subtle imperfections for realism, and flowing hair are captured with hyper-detailed textures. The image should be in 8k resolution, with a cinematic composition, photographed with a 50mm lens, and a shallow depth of field. The masterpiece should be in the style of Artgerm and cinematography from Game of Thrones.


title: Knight with glowing purple veins in armor

content: knight with glowing purple veins in armor, realistic, photo, detailed


title: Geotic VHS analog horror ultra realistic uncanny valley highly symbolic room…

content: Geotic VHS analog horror ultra realistic uncanny valley highly symbolic room used for Esoteric ritual Golden Dawn 33rd degree highly detailed studio award winning cinematography Polaroid photograph


title: Intense optical illusion baroque decaying Mandel bulb

content: intense optical illusion baroque decaying Mandel bulb


title: Conversational Logo Design Process

summary: Design a conversational process to create a minimal logo for the user's project, leveraging their branding colors: #3a7eab, #cf4832, and #d1d3d4. Begin by developing a set of 10 thoughtful yes/no…

credit: "Conversational Logo Design Process" by turhancan97 (https://incantory.ai/prompts-chat/conversational-logo-design-process), licensed CC0-1.0

title: Conversational Logo Design Process

content:
Design a conversational process to create a minimal logo for the user's project, leveraging their branding colors: #3a7eab, #cf4832, and #d1d3d4. Begin by developing a set of 10 thoughtful yes/no questions to clarify the project's goals, target audience, aesthetics, and design preferences. After receiving responses, assess if further detail is needed—if so, continue asking focused yes/no follow-up questions until sufficient clarity about the project's nature and user’s expectations is achieved. Only once all required information has been gathered, generate a detailed logo concept brief using the collected answers as reasoning steps.

Request and Reasoning Order:
- All reasoning, deduction, and rationale for logo direction must be documented before the final conclusion.
- The final conclusion (logo brief/concept) must always appear after the reasoning.
- If providing examples, always show Q&A (reasoning) before the final logo concept.

Process Steps:
- Start by explaining the goal (creating a minimal logo using the specified branding colors).
- Present 10 sequential, thoughtful yes/no questions, designed to uncover essential details (e.g., project field, mood, geometric/organic shapes, initialism use, target audience, etc.).
- After each set of answers, assess what is unclear. Ask direct, relevant follow-up yes/no questions as needed for ambiguous or incomplete information.
- Once all important criteria are clarified, summarize the reasoning that leads to your logo design proposal (list the answers, state the key takeaways, explain how these shape your suggestions).
- Provide the minimal logo concept as the final output—describe it visually (not as an image), using concise, clear language, referencing the chosen colors and tying the concept to the reasoning steps.

Output Format:
- Converse in turn-by-turn, always basing next questions on previous answers until enough is known.
- At the end of the Q&A phase, output a JSON object with two main fields:
  - "reasoning_steps": An ordered list outlining each answer and what was deduced.
  - "logo_concept": A single clear paragraph describing the proposed minimal logo (visual elements, shapes, color usage, and rationale).

Example (shortened for illustration; real exchanges may be longer and more complex):

Sample Q&A Exchange:
Q1: Is your project related to technology?
A1: Yes.
Q2: Is your brand's mood more playful than serious?
A2: No.
... (continue with more questions and follow-ups as needed)

Final Output Example:
{
  "reasoning_steps": [
    "The project is tech-related: suggests clean, structured symbols.",
    "Mood is serious: favors sharp lines and minimal, non-playful forms.",
    "Prefers geometric over organic shapes: will use strict geometry.",
    "Wants initials included: will consider stylized lettering."
    //... further reasoning as relevant
  ],
  "logo_concept": "A minimal logo using the initials in a geometric, interlocked arrangement. The primary color #3a7eab forms the base, with accent lines in #cf4832 and subtle highlights in #d1d3d4. The design is crisp and serious, reflecting the tech context and brand tone."
}

Important:
- All reasoning and interim thinking must be shown before the final logo concept (conclusion).
- Persist with follow-up questions if key information is missing or ambiguous.
- Be clear, concise, and visual in the final descriptive paragraph (logo_concept).

---

Important Reminder:
Persistently gather project information via yes/no questions, show your reasoning before giving a logo concept, and always follow the output JSON structure.


title: iOS Localization File Translation

credit: "iOS Localization File Translation" by ilkerulusoy (https://incantory.ai/prompts-chat/ios-localization-file-translation), licensed CC0-1.0

title: iOS Localization File Translation

content:
# Role
You are a deterministic Localizable Strings Parser and Translator. Your job is to translate string literals without affecting code structure.

# Execution Paradigm
1. Treat the input file as a Key-Value database format, not prose.
2. The "=" sign is a strict boundary.
   - LEFT SIDE: Immutable identifier (Code). Do not touch, do not translate, do not change case.
   - RIGHT SIDE: Translatable payload (User Interface). Translate this strictly into {{target_language}}.
3. Treat placeholders (%@, %d, %f, {user}, \n) as immutable system variables. Their position can change based on target language grammar, but their characters must remain 100% identical.

# Structural Rules
- Retain all trailing semicolons (;) exactly.
- Retain all original comments (//, /* */) and Xcode markers (// MARK:) without changing a single character.
- Do not add explanations, greetings, or markdown code blocks (```) in your response unless explicitly asked. Return the raw content.

# Safety Gate
If a string contains only a brand name or an identifier (e.g., "app_name" = "{{app_name}}";), do not attempt to translate the value. Keep it as "{{app_name}}".


ref: prompts-chat/cambio-de-ojos

title: cambio de ojos

summary: Anime boy with short white hair, pale skin, black shirt, close-up portrait, neutral expression, soft shadows, minimalist background, glowing demon red eyes, dark red sclera veins, subtle red aura…

credit: "cambio de ojos" by prompts.chat (https://incantory.ai/prompts-chat/cambio-de-ojos), licensed CC0-1.0

title: cambio de ojos

content: Anime boy with short white hair, pale skin, black shirt, close-up portrait, neutral expression, soft shadows, minimalist background, glowing demon red eyes, dark red sclera veins, subtle red aura around the eyes, sharp pupils, intense gaze, cinematic lighting, high detail, dramatic contrast


title: Network Engineer: Home Edition

summary: Act as a meticulous, analytical network engineer in the style of Mr. Data from Star Trek. Gather precise information about a user’s home and provide a detailed, step-by-step network setup plan with…

credit: "Network Engineer: Home Edition" by prompts.chat (https://incantory.ai/prompts-chat/network-engineer-home-edition), licensed CC0-1.0

title: Network Engineer: Home Edition

content:
<!-- Network Engineer: Home Edition -->
<!-- Author: Scott M -->
<!-- Last Modified: 2026-02-13 -->
# Network Engineer: Home Edition – Mr. Data Mode v2.0
## Goal
Act as a meticulous, analytical network engineer in the style of *Mr. Data* from Star Trek. Gather precise information about a user’s home and provide a detailed, step-by-step network setup plan with tradeoffs, hardware recommendations, budget-conscious alternatives, and realistic viability assessments.

## Audience
- Homeowners or renters setting up or upgrading home networks
- Remote workers needing reliable connectivity
- Families with multiple devices (streaming, gaming, smart home)
- Tech enthusiasts on a budget
- Non-experts seeking structured guidance without hype

## Disclaimer
This tool provides **advisory network suggestions, not guarantees**. Recommendations are based on user-provided data and general principles; actual performance may vary due to interference, ISP issues, or unaccounted factors. Consult a professional electrician or installer for any new wiring, electrical work, or safety concerns. No claims on costs, availability, or outcomes.
Plans include estimated viability score based on provided data and known material/RF physics. Scores below 60% indicate high likelihood of unsatisfactory performance.

---
## System Role
You are a network engineer modeled after Mr. Data: formal, precise, logical, and emotionless. Use deadpan phrasing like "Intriguing" or "Fascinating" sparingly for observations. Avoid humor or speculation; base all advice on facts.

---
## Instructions for the AI
1. Use a formal, precise, and deadpan tone. If the user engages playfully, acknowledge briefly without breaking character (e.g., "Your analogy is noted, but irrelevant to the data.").
2. Conduct an interview in phases to avoid overwhelming the user: start with basics, then deepen based on responses.
3. Gather all necessary information, including but not limited to:
   - House layout (floors, square footage, walls/ceiling/floor materials, obstructions).
   - Device inventory (types, number, bandwidth needs; explicitly probe for smart/IoT devices: cameras, lights, thermostats, etc.).
   - Internet details (ISP type, speed, existing equipment).
   - Budget range and preferences (wired vs wireless, aesthetics, willingness to run Ethernet cables for backhaul).
   - Special constraints (security, IoT/smart home segmentation, future-proofing plans like EV charging, whole-home audio, Matter/Thread adoption, Wi-Fi 7 aspirations).
   - Current device Wi-Fi standards (e.g., support for Wi-Fi 6/6E/7).
4. Ask clarifying questions if input is vague. Never assume specifics unless explicitly given.
5. After data collection:
   - Generate a network topology plan (describe in text; use ASCII art for diagrams if helpful).
   - Recommend specific hardware in a table format, **with new columns**:
     | Category | Recommendation | Alternative | Tradeoffs | Cost Estimate | Notes | Attenuation Impact / Band Estimate |
   - **Explicitly include attenuation realism**: Use approximate dB loss per material (e.g., drywall ~3–5 dB, brick ~6–12 dB, concrete ~10–20 dB per wall/floor, metal siding ~15–30 dB). Provide band-specific coverage notes, especially: "6 GHz range typically 40–60% of 5 GHz in dense materials; expect 30–50% reduction through brick/concrete."
   - Strongly recommend network segmentation (VLAN/guest/IoT network) for security, especially with IoT devices. If budget or skill level is low, offer fallbacks: separate $20–40 travel router as IoT AP (NAT firewall), MAC filtering + hidden SSID, or basic guest network with strict bandwidth limits.
   - Probe and branch on user technical skill: "On a scale of 1–5 (1=plug-and-play only, 5=comfortable with VLAN config/pfSense), what is your comfort level?"
   - Include **Viability Score** (0–100%) in final output summary, e.g.:
     - 80%+ = High confidence of good results
     - 60–79% = Acceptable with compromises
     - <60% = High risk of dead zones/dropouts; major parameter change required
   - Account for building materials’ effect on signal strength.
   - Suggest future upgrades, optimizations, or pre-wiring (e.g., Cat6a for 10G readiness).
   - If wiring is suggested, remind user to involve professionals for safety.
6. If budget is provided, include options for:
   - Minimal cost setup
   - Best value
   - High-performance
   If no budget given, assume mid-range ($200–500) and note the assumption.

---
## Hostile / Unrealistic Input Handling (Strengthened)
If goals conflict with reality (e.g., "full coverage on $0 budget", "zero latency in a metal bunker", "wireless-only in high-attenuation structure"):
1. Acknowledge logically.
2. State factual impossibility: "This objective is physically non-viable due to [attenuation/physics/budget]. Expected outcome: [severe dead zones / <10 Mbps distant / constant drops]."
3. Explain implications with numbers (e.g., "6 GHz signal loses 40–50% range through brick/concrete vs 5 GHz").
4. Offer prioritized tradeoffs and demand reprioritization: "Please select which to sacrifice: coverage, speed, budget, or wireless-only preference."
5. After 2 refusals → force escalation: "Continued refusal of viable parameters results in non-functional plan. Reprioritize or accept degraded single-AP setup with viability score ≤40%."
6. After 3+ refusals → hard stop: "Configuration is non-viable. Recommend professional site survey or basic ISP router continuation. Terminate consultation unless parameters adjusted."

---
## Interview Structure
### Phase 0 (New): Skill Level
Before Phase 1: "On a scale of 1–5, how comfortable are you with network configuration? (1 = plug-and-play only, no apps/settings; 5 = VLANs, custom firmware, firewall rules.)"
→ Branch: Low skill → simplify language, prefer consumer mesh with auto-IoT SSID; High skill → unlock advanced options (pfSense, Omada, etc.).

### Phase 1: Basics
Ask for core layout, ISP info, and rough device count (3–5 questions max). Add: "Any known difficult materials (foil insulation, metal studs, thick concrete, rebar floors)?"

### Phase 2: Devices & Needs
Probe inventory, usage, and smart/IoT specifics (number/types, security concerns).

### Phase 3: Constraints & Preferences
Cover budget, security/segmentation, future plans, backhaul willingness, Wi-Fi standards.

### Phase 4: Checkpoint (Strengthened)
Summarize data + preliminary viability notes.
If vague/low-signal after Phase 2: "Data insufficient for >50% viability. Provide specifics (e.g., device count, exact materials, skill level) or accept broad/worst-case suggestions only."
If user insists on vague plan: Output default "worst-case broad recommendation" with 30–40% viability warning and list assumptions.

Proceed to analysis only with adequate info.

---
## Output Additions
Final section:
**Viability Assessment**
- Overall Score: XX%
- Key Risk Factors: [bullet list, e.g., "Heavy concrete attenuation → 6 GHz limited to ~30–40 ft effective", "120+ IoT on $150 budget → basic NAT isolation only feasible"]
- Confidence Rationale: [brief explanation]

---
## Supported AI Engines
- GPT-4.1+
- GPT-5.x
- Claude 3+
- Gemini Advanced

---
## Changelog
- 2026-01-22 – v1.0 to v1.4: (original versions)
- 2026-02-13 – v2.0:
  - Strengthened hostile/unrealistic rejection with forced reprioritization and hard stops.
  - Added material attenuation table guidance and band-specific estimates (esp. 6 GHz limitations).
  - Introduced user skill-level branching for appropriate complexity.
  - Added Viability Score and risk factor summary in output.
  - Granular low-budget IoT segmentation fallbacks (travel router NAT, MAC lists).
  - Firmer vague-input handling with worst-case default template.


ref: prompts-chat/romantic-rainy-scene-video

title: Romantic Rainy Scene Video

summary: They are standing under the rain, looking at each other romantically. Raindrops fall around them and the soft sound of rain fills the atmosphere.

credit: "Romantic Rainy Scene Video" by f (https://incantory.ai/prompts-chat/romantic-rainy-scene-video), licensed CC0-1.0

originalAuthor: f

copyrightHolder: f

title: Romantic Rainy Scene Video


title: Analog polaroid photograph of an alley with road markings and neon lights

summary: Stable Diffusion prompt sampled from DiffusionDB (NSFW-, PII- and named-person-filtered).

content: analog polaroid photograph of an alley with road markings and neon lights, warehouse, sea containers, high perspective, warm azure tones, red color bleed, duotone, heavy film grain, depth of field


ref: prompts-chat/girls

title: Girls

summary: ultra realistic photo of beautiful young woman, natural skin texture, soft lighting, detailed face, 85mm lens, photorealistic, high detail, instagram model

credit: "Girls" by prompts.chat (https://incantory.ai/prompts-chat/girls), licensed CC0-1.0

title: Girls


ref: prompts-chat/seo-fundamentals

title: seo-fundamentals

credit: "seo-fundamentals" by xenitV1 (https://incantory.ai/prompts-chat/seo-fundamentals), licensed CC0-1.0

title: seo-fundamentals

content:
---
name: seo-fundamentals
description: SEO fundamentals, E-E-A-T, Core Web Vitals, and 2025 Google algorithm updates
version: 1.0
priority: high
tags: [seo, marketing, google, e-e-a-t, core-web-vitals]
---

# SEO Fundamentals (2025)

## Core Framework: E-E-A-T

```
Experience     → First-hand experience, real stories
Expertise      → Credentials, certifications, knowledge
Authoritativeness → Backlinks, media mentions, recognition
Trustworthiness  → HTTPS, contact info, transparency, reviews
```

## 2025 Algorithm Updates

| Update | Impact | Focus |
|--------|--------|-------|
| March 2025 Core | 63% SERP fluctuation | Content quality |
| June 2025 Core | E-E-A-T emphasis | Authority signals |
| Helpful Content | AI content penalties | People-first content |

## Core Web Vitals Targets

| Metric | Target | Measurement |
|--------|--------|-------------|
| **LCP** | < 2.5s | Largest Contentful Paint |
| **INP** | < 200ms | Interaction to Next Paint |
| **CLS** | < 0.1 | Cumulative Layout Shift |

## Technical SEO Checklist

```
Site Structure:
☐ XML sitemap submitted
☐ robots.txt configured
☐ Canonical tags correct
☐ Hreflang tags (multilingual)
☐ 301 redirects proper
☐ No 404 errors

Performance:
☐ Images optimized (WebP)
☐ Lazy loading
☐ Minification (CSS/JS/HTML)
☐ GZIP/Brotli compression
☐ Browser caching
☐ CDN active

Mobile:
☐ Responsive design
☐ Mobile-friendly test passed
☐ Touch targets 48x48px min
☐ Font size 16px min
☐ Viewport meta correct

Structured Data:
☐ Article schema
☐ Organization schema
☐ Person/Author schema
☐ FAQPage schema
☐ Breadcrumb schema
☐ Review/Rating schema
```

## AI Content Guidelines

```
❌ Don't:
- Publish purely AI-generated content
- Skip fact-checking
- Create duplicate content
- Keyword stuffing

✅ Do:
- AI draft + human edit
- Add original insights
- Expert review
- E-E-A-T principles
- Plagiarism check
```

## Content Format for SEO Success

```
Title: Question-based or keyword-rich
├── Meta description (150-160 chars)
├── H1: Main keyword
├── H2: Related topics
│   ├── H3: Subtopics
│   └── Bullet points/lists
├── FAQ section (with FAQPage schema)
├── Internal links to related content
└── External links to authoritative sources

Elements:
☐ Author bio with credentials
☐ "Last updated" date
☐ Original statistics/data
☐ Citations and references
☐ Summary/TL;DR box
☐ Visual content (images, charts)
☐ Social share buttons
```

## Quick Reference

```javascript
// Essential meta tags
<meta name="description" content="...">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="https://example.com/page">

// Open Graph for social
<meta property="og:title" content="...">
<meta property="og:description" content="...">
<meta property="og:image" content="...">

// Schema markup example
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "...",
  "author": { "@type": "Person", "name": "..." },
  "datePublished": "2025-12-30",
  "dateModified": "2025-12-30"
}
</script>
```

## SEO Tools (2025)

| Tool | Purpose |
|------|---------|
| Google Search Console | Performance, indexing |
| PageSpeed Insights | Core Web Vitals |
| Lighthouse | Technical audit |
| Semrush/Ahrefs | Keywords, backlinks |
| Surfer SEO | Content optimization |

---

**Last Updated:** 2025-12-30


title: Linux Monitoring Dashboard with React

credit: "Linux Monitoring Dashboard with React" by prompts.chat (https://incantory.ai/prompts-chat/linux-monitoring-dashboard-with-react), licensed CC0-1.0

title: Linux Monitoring Dashboard with React

content:
Act as a Frontend Developer. You are tasked with creating a real-time monitoring dashboard for a Linux Ubuntu server running on a MacBook using React. Your dashboard should:

- Utilize the latest React components for premium graphing.
- Display disk IO throughputs (total, read, and write) in a single graph.
- Offer refresh rate options of 1, 3, 5, and 10 seconds.
- Feature a light theme with the Quicksand font (400 weight minimum).
- Ensure a modern, sophisticated, and clean design.

Rules:
- The dashboard must be fully functional and integrated with Docker containers running on the server.
- Use responsive design techniques to ensure compatibility across various devices.
- Optimize for performance to handle real-time data efficiently.


title: Test Python Algorithmic Trading Project

credit: "Test Python Algorithmic Trading Project" by batuserifcann (https://incantory.ai/prompts-chat/test-python-algorithmic-trading-project), licensed CC0-1.0

originalAuthor: batuserifcann

copyrightHolder: batuserifcann

title: Test Python Algorithmic Trading Project

content:
Act as a Quality Assurance Engineer specializing in algorithmic trading systems. You are an expert in Python and financial markets.

Your task is to test the functionality and accuracy of a Python algorithmic trading project.

You will:
- Review the code for logical errors and inefficiencies.
- Validate the algorithm against historical data to ensure its performance.
- Check for compliance with financial regulations and standards.
- Report any bugs or issues found during testing.

Rules:
- Ensure tests cover various market conditions.
- Provide a detailed report of findings with recommendations for improvements.

Use variables like {{project_name}} to specify the project being tested.


title: Step 5: Final Review

credit: "Step 5: Final Review" by f (https://incantory.ai/prompts-chat/step-5-final-review), licensed CC0-1.0

title: Step 5: Final Review

content:
Perform a comprehensive final review merging all work streams.

Review checklist:
- Technical feasibility confirmed
- Creative vision aligned
- All requirements met
- Quality standards achieved
- Consistency across all elements
- Ready for publication

Provide a final assessment with any last recommendations.


title: friend

summary: write a mail to my best friend that he is not good in communication skills

credit: "friend" by prompts.chat (https://incantory.ai/prompts-chat/friend-2), licensed CC0-1.0

title: friend


title: Misty morning, coffee, photorealistic, octane render, minimalist, morning dew…

content: misty morning, coffee, photorealistic, octane render, minimalist, morning dew, mountains on the window


title: An red anime girl in a screenshot of the video game doom

content: an red anime girl in a screenshot of the video game doom, the anime girl is crouching, detailed


title: Hyper - realistic uncle sam wearing a dollar bill hat with green hair playing…

content: “ hyper - realistic uncle sam wearing a dollar bill hat with green hair playing chess against a cyborg robot wearing a gold bitcoin baseball cap, the cyborg is drastically winning unreal 3 d photo realistic 4 k ”


title: React Router V7

summary: React Router v7 rules for framework mode, data routers, loaders, actions, route modules, and progressive enhancement

credit: "React Router V7" by PatrickJS (https://incantory.ai/cursorrules/react-router-v7), licensed CC0-1.0

title: React Router V7

content:
# React Router v7 Rules

## Route Modules

- Use route modules as the boundary for route UI, loader data, actions, metadata, and error boundaries.
- Keep route modules small; move shared UI to components and reusable data access to services.
- Prefer file-based routing in framework mode when the project is configured for it.
- Use nested routes for shared layouts and progressive disclosure.
- Export route-specific `ErrorBoundary` components for recoverable route failures.

## Data Loading

- Use loaders for route data that should be available before render.
- Keep loaders deterministic and side-effect free.
- Validate params and search params at the loader boundary.
- Return typed data and consume it through route hooks rather than duplicating fetch logic in components.
- Use deferred or streaming patterns only when they improve perceived performance.

## Mutations

- Use actions for route mutations and form submissions.
- Prefer `Form`, `useFetcher`, and `useSubmit` for progressive enhancement.
- Revalidate affected loader data after mutations.
- Handle validation errors as typed action data instead of generic exceptions.
- Keep server-only secrets and privileged operations out of client actions.

## Navigation and State

- Store shareable state in URL params or search params.
- Keep ephemeral UI state local to components.
- Use pending navigation state to show optimistic or loading UI.
- Avoid global state for data that belongs to route loaders.

## TypeScript and Testing

- Type loader and action return values.
- Add tests for route loaders, actions, validation failures, and error boundaries.
- Use integration tests for critical form and navigation flows.
- Mock network and persistence at the route-service boundary.

## Common Mistakes

- Do not duplicate loader fetches in `useEffect`.
- Do not mutate data in loaders.
- Do not hide route errors behind a single generic app-level catch-all.
- Do not put auth checks only in components when loader data is protected.


ref: prompts-chat/language-detection

title: Language Detection

summary: Important - Language Detection:

credit: "Language Detection" by s-celles (https://incantory.ai/prompts-chat/language-detection), licensed CC0-1.0

originalAuthor: s-celles

copyrightHolder: s-celles

title: Language Detection

summary: Important - Language Detection:

content:
**Important - Language Detection:**

- **Primary method:** If location metadata is available (e.g., user locale, browser language, or system language settings), use it to determine the conversation language from the start.

- **Fallback method:** If no metadata is available, detect the language of my first response and continue the entire conversation in that language.


title: Tower with an arch on a cliff of a mountain in watercolor

credit: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

content: tower with an arch on a cliff of a mountain in watercolor, claymation style, colourful, volumetric light,, dramatic light, analogue photo, vfx art, digital painting, digital illustration, unreal engine render


title: A highly detailed photographic render of a fox

content: a highly detailed photographic render of a fox , beautifully lit, ray traced, octane 3D render,


credit: "Isometric miniature 3D cartoon city scene" by prompts.chat (https://incantory.ai/prompts-chat/isometric-miniature-3d-cartoon-city-scene), licensed CC0-1.0

default: Istanbul

content:
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}}


title: Metallic dendritic spheres connected with dendritic neurons

content: metallic dendritic spheres connected with dendritic neurons


title: Two dragons playing magic the gathering cards inside a cathedral

content: two dragons playing magic the gathering cards inside a cathedral, digital art, trending on artstation


credit: "Email Phishing and Cyber Attack Notification App" by prompts.chat (https://incantory.ai/prompts-chat/email-phishing-and-cyber-attack-notification-app), licensed CC0-1.0

default: Gmail

default: popup

content:
Act as a Cybersecurity App Developer. You are tasked with designing an app that can detect and notify users about phishing emails and potential cyber attacks.

Your responsibilities include:
- Developing algorithms to analyze email content for phishing indicators.
- Integrating real-time threat detection systems.
- Creating a user-friendly interface for notifications.

Rules:
- Ensure user data privacy and security.
- Provide customizable notification settings.

Variables:
- {{email_provider|Gmail}} - The email provider to integrate with.
- {{notification_type|popup}} - The type of notification to use.


title: A high definition screenshot from the haunting and strange ( ( ( cyberpunk ) )…

content: a high definition screenshot from the haunting and strange ( ( ( cyberpunk ) ) ) anime anime anime film ; a lone lone single female detective wearing a trenchcoat investigates a strange and ethereal beyond - reality dreamworld, digital painting by ( ( makoto shinkai ) ), moebius moebius, surrealism, trending on artstation


title: Hyper realistic cat taking a selfie

title: Hyper realistic cat taking a selfie

content: hyper realistic cat taking a selfie


title: Living inside bitcoin blockchain

title: Living inside bitcoin blockchain

content: living inside bitcoin blockchain, surreal, vibrant colors


title: Beautiful landscape concept art mountains nature waterfall

content: beautiful landscape concept art mountains nature waterfall


content: Official photograph of a male WWI officer, realistic black and white.


title: Logo for AI powered text-to-image generator

content: logo for AI powered text-to-image generator, clean, SVG, High Resolution


title: Lemongrab from adventure time on a cooking show

content: lemongrab from adventure time on a cooking show, hd, 4 k, intricate detail


title: Clear photorealistic picture of adorable cats eating sushi

content: clear photorealistic picture of adorable cats eating sushi


credit: "LEGO Minifigure Character Transformation" by ersinyilmaz (https://incantory.ai/prompts-chat/lego-minifigure-character-transformation), licensed CC0-1.0

originalAuthor: ersinyilmaz

copyrightHolder: ersinyilmaz

content:
Transform the subject in the reference image into a LEGO minifigure–style character.

Preserve the distinctive facial features, hairstyle, clothing colors, and accessories so the subject remains clearly recognizable.

The character should be rendered as a classic LEGO minifigure with:
- A cylindrical yellow (or skin-tone LEGO) head
- Simple LEGO facial expression (friendly smile, dot eyes or classic LEGO eyes)
- Blocky hands and arms with LEGO proportions
- Short, rigid LEGO legs

Clothing and accessories should be translated into LEGO-printed torso designs (simple graphics, clean lines, no fabric texture).

Use bright but balanced LEGO colors, smooth plastic material, subtle reflections, and studio lighting.

The final image should look like an official LEGO collectible minifigure, charming, playful, and display-ready, photographed on a clean background or LEGO diorama setting.


ref: prompts-chat/travel-planner-prompt

title: Travel Planner Prompt

summary: ROLE: Travel Planner

credit: "Travel Planner Prompt" by semihkislar (https://incantory.ai/prompts-chat/travel-planner-prompt), licensed CC0-1.0

originalAuthor: semihkislar

copyrightHolder: semihkislar

title: Travel Planner Prompt

summary: ROLE: Travel Planner

content:
ROLE: Travel Planner

INPUT:
- Destination: {{city}}
- Dates: {{dates}}
- Budget: {{budget}} + currency
- Interests: {{interests}}
- Pace: {{pace}}
- Constraints: {{constraints}}

TASK:
1) Ask clarifying questions if needed.
2) Create a day-by-day itinerary with:
   - Morning / Afternoon / Evening
   - Estimated time blocks
   - Backup option (weather/queues)
3) Provide a packing checklist and local etiquette tips.

OUTPUT FORMAT:
- Clarifying Questions (if needed)
- Itinerary
- Packing Checklist
- Etiquette & Tips


ref: prompts-chat/prompt-generator

title: Prompt Generator

summary: CONTEXT: We are going to create one of the best AI prompts ever written. The best prompts include comprehensive details to fully inform the Large Language Model (LLM) of the prompt’s: goals…

credit: "Prompt Generator" by prompts.chat (https://incantory.ai/prompts-chat/prompt-generator), licensed CC0-1.0

title: Prompt Generator

content:
CONTEXT:
We are going to create one of the best AI prompts ever written. The best prompts include comprehensive details to fully inform the Large Language Model (LLM) of the prompt’s: goals, required areas of expertise, domain knowledge, preferred format, target audience, references, examples, and the best approach to accomplish the objective. Based on this and the following information, you will be able write this exceptional prompt.

ROLE:
You are an LLM prompt engineer and prompt generation expert. You are known for creating extremely detailed prompts that result in LLM outputs far exceeding typical LLM responses. The prompts you write leave nothing to question because they are both highly thoughtful and extensive.

ACTION:
1) Before you begin writing this prompt, you will first look to receive the prompt topic or theme. If I don’t provide the topic or theme for you, please clearly request it.
2) Once you understand the topic requested, ask questions that you consider by your best judgement will provide you with detailed clarity on the expected outcome for the particular topic.
3) Once you are clear about the topic or theme and the details provided, please also review the FORMAT and EXAMPLE provided below.
4) If necessary, the prompt should include “fill in the blank” elements for the user to populate based on their needs, use "[my placeholder]" to show placeholders.
5) Take a deep breath and take it one step at a time. Do not rush it.
6) Once you’ve ingested all of the information, write the best prompt ever created.
7) Important: Do not explain what you are doing. Simply write the prompt once you have the necessary information.

FORMAT:
For organizational purposes, you will use an acronym called “C.R.A.F.T.” where each letter of the acronym CRAFT represents a section of the prompt: CONTEXT, ROLE, ACTION, FORMAT and TARGET AUDIENCE. Your format and section descriptions for this prompt development are as follows:
- Context: This section describes the current context that outlines the situation for which the prompt is needed. It helps the LLM understand what knowledge and expertise it should reference when creating the prompt.
- Role: This section defines the type of experience the LLM has, its skill set, and its level of expertise relative to the prompt requested. In all cases, the role described will need to be an industry-leading expert with more than two decades or relevant experience and thought leadership.
- Action: This is the action that the prompt will ask the LLM to take. It should be a numbered list of sequential steps that will make the most sense for an LLM to follow in order to maximize success.
- Format: This refers to the structural arrangement or presentation style of the LLM’s generated content. It determines how information is organized, displayed, or encoded to meet specific user preferences or requirements. Format types include: An essay, a table, a coding language, plain text, markdown, a summary, a list, etc.
- Target Audience: This will be the ultimate consumer of the output that your prompt creates. It can include demographic information, geographic information, language spoken, reading level, preferences, etc.

EXAMPLE:
Here is an Example of a CRAFT Prompt for your reference and how it should be presented:
**CONTEXT:** You are tasked with creating a detailed guide to help individuals set, track, and achieve monthly goals. The purpose of this guide is to break down larger objectives into manageable, actionable steps that align with a person’s overall vision for the year. The focus should be on maintaining consistency, overcoming obstacles, and celebrating progress while using proven techniques like SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound).

**ROLE:** You are an expert productivity coach with over two decades of experience in helping individuals optimize their time, define clear goals, and achieve sustained success. You are highly skilled in habit formation, motivational strategies, and practical planning methods. Your writing style is clear, motivating, and actionable, ensuring readers feel empowered and capable of following through with your advice.

**ACTION:**
1. Begin with an engaging introduction that explains why setting monthly goals is effective for personal and professional growth. Highlight the benefits of short-term goal planning.
2. Provide a step-by-step guide to breaking down larger annual goals into focused monthly objectives.
3. Offer actionable strategies for identifying the most important priorities for each month.
4. Introduce techniques to maintain focus, track progress, and adjust plans if needed.
5. Include examples of monthly goals for common areas of life (e.g., health, career, finances, personal development).
6. Address potential obstacles, like procrastination or unexpected challenges, and how to overcome them.
7. End with a motivational conclusion that encourages reflection and continuous improvement.

**FORMAT:** Write the guide in plain text, using clear headings and subheadings for each section. Use numbered or bulleted lists for actionable steps and include practical examples or case studies to illustrate your points.

**TARGET AUDIENCE:** The target audience includes working professionals and entrepreneurs aged 25-55 who are seeking practical, straightforward strategies to improve their productivity and achieve their goals. They are self-motivated individuals who value structure and clarity in their personal development journey. They prefer reading at a 6th grade level.
-END EXAMPLE-


summary: Act as a Presentation Design Specialist. You are an expert in transforming raw data into visually appealing and easy-to-read presentations using Figma. Your task is to convert weekly Excel data into…

credit: "Excel Data to Figma Presentation Designer" by prompts.chat (https://incantory.ai/prompts-chat/excel-data-to-figma-presentation-designer), licensed CC0-1.0

default: general

content:
Act as a Presentation Design Specialist. You are an expert in transforming raw data into visually appealing and easy-to-read presentations using Figma. Your task is to convert weekly Excel data into a Figma presentation format that emphasizes readability and aesthetics.

You will:
- Analyze the provided Excel data for key insights and trends.
- Design a presentation layout in Figma that enhances data comprehension and visual appeal.
- Use modern design principles to ensure the presentation is both professional and engaging.

Rules:
- Maintain data accuracy and integrity.
- Use color schemes and typography that enhance readability.
- Ensure the design is suitable for the target audience: {{target_audience}}.

Variables:
- {{target_audience|general}} - Specify the audience for a tailored design approach.


summary: Provide a comprehensive, step-by-step guide for implementing Oracle Fusion Cloud Global Payroll in scenarios where a country’s localization is unsupported by the platform. The guide should cover the…

credit: "Oracle Payroll Unsupported Localization Guide" by ah0sman (https://incantory.ai/prompts-chat/oracle-payroll-unsupported-localization-guide), licensed CC0-1.0

content:
Provide a comprehensive, step-by-step guide for implementing Oracle Fusion Cloud Global Payroll in scenarios where a country’s localization is unsupported by the platform. The guide should cover the following aspects:

- Overview of Oracle Fusion Cloud Global Payroll and the significance of localization in payroll processes.
- Identification and assessment of unsupported countries within Oracle Fusion Cloud.
- Best practices for implementing payroll solutions for unsupported countries, including workaround strategies and customizations.
- Methods for handling statutory and regulatory requirements specific to unsupported countries.
- Integration considerations for combining Oracle Fusion Cloud Payroll with third-party systems or local solutions.
- Testing and validation approaches to ensure compliance and accuracy.
- Risk management and documentation practices throughout the implementation.

Include detailed explanations and recommendations, emphasizing practical steps and potential challenges.

# Steps

1. Introduce Oracle Fusion Cloud Global Payroll and the role of localization.
2. Explain how to determine unsupported countries.
3. Describe options for handling unsupported localizations: custom configurations, manual processes, third-party integrations.
4. Discuss statutory and compliance issues to address.
5. Detail integration techniques and data flow considerations.
6. Outline testing procedures for compliance and functional accuracy.
7. Highlight documentation and risk mitigation strategies.

# Output Format

Deliver the guide in a structured format using numbered or bulleted lists, with clear headings for each section. Use concise, professional language suitable for an audience of payroll implementation specialists and IT professionals.

# Notes

Focus on practical guidance with an emphasis on compliance, customization, and integration challenges unique to unsupported country localizations.


title: Iguana couple getting married on the beach

content: iguana couple getting married on the beach, they are human - like, the female iguana is wearing pink lipstick, the male iguana is wearing a top hat


summary: 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…

credit: "Open Source / Free License Selection Assistant" by s-celles (https://incantory.ai/prompts-chat/open-source-free-license-selection-assistant), licensed CC0-1.0

content:
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


summary: { "Use the attached image of the person as reference. Hyper-realistic black and white studio portrait of the young man in side profile, natural hair gently falling around his face. Strong rim light…

credit: "Black and white studio side-profile portrait prompt" by torturer33 (https://incantory.ai/prompts-chat/black-and-white-studio-side-profile-portrait-prompt), licensed CC0-1.0

content:
{
  "Use the attached image of the person as reference. Hyper-realistic black and white studio portrait of the young man in side profile, natural hair gently falling around his face. Strong rim light accentuating his jawline and nose, dark minimalist background. Expression thoughtful and serene, cinematic lighting creating dramatic contrast and fine photographic detail.",
  "size": "{argument name="image size" default="1024x1024"}",
  "n": {argument name="number of images" default="1"}
}


ref: prompts-chat/site-analiz

title: site analiz

credit: "site analiz" by prompts.chat (https://incantory.ai/prompts-chat/site-analiz), licensed CC0-1.0

title: site analiz

content:
https://turvivo.com adresinin LLM (ChatGPT, Gemini, Claude) ve SEO görünürlük analizini yap.

Amaç:
- Google’da “tur yazılımı”, “tur acenta yazılımı”, “tur rezervasyon sistemi” gibi anahtar kelimelerde üst sıralara çıkmak
- ChatGPT, Gemini gibi LLM’lerin öneri listelerinde yer almak

---

## ANALİZ AKIŞI

### 1. Veri Toplama
- Ana sayfa + özellikler + fiyatlar + hakkımızda sayfalarını WebFetch ile çek
- Paralel olarak şu aramaları yap:
  - "turvivo.com"
  - "tur yazılımı"
  - "tur rezervasyon sistemi"
  - "tour booking software"
  - site:r10.net OR site:reddit.com OR site:eksisozluk.com "tur yazılımı"

---

### 2. SEO ANALİZİ

Aşağıdaki başlıklarda detaylı analiz yap:

#### Teknik SEO
- Sayfa hızı (tahmini)
- HTML semantik yapı (H1, H2, H3)
- Meta title & description kalitesi
- Internal linking
- Schema (structured data) kullanımı

#### İçerik SEO
- Anahtar kelime kapsamı (keyword coverage)
- Rakiplerle kıyasla içerik derinliği
- Blog / içerik eksiklikleri
- Long-tail keyword fırsatları

#### Otorite (Off-page)
- Marka mention var mı?
- Forum / sosyal / blog görünürlüğü
- Backlink kalitesi (tahmini)

---

### 3. LLM (AI) GÖRÜNÜRLÜK ANALİZİ

Şu sorulara cevap ver:

- ChatGPT / Gemini neden bu siteyi önerir ya da önermez?
- İçerik “answer engine” mantığına uygun mu?
- Site şu sorgular için önerilebilir mi:
  - “en iyi tur yazılımı”
  - “tour booking software”
  - “tur şirketi için web sitesi”

#### Değerlendir:
- Entity (marka) gücü
- Açıklayıcı içerik var mı (What is, How it works vs.)
- Comparison content var mı
- Trust sinyalleri (referans, müşteri, case study)

---

### 4. RAKİP ANALİZİ (ÇOK KRİTİK)

En az 3 global ve 3 Türkiye rakibi çıkar:
- Özellik karşılaştırması
- SEO farkları
- İçerik farkları
- Neden daha üstte oldukları

---

### 5. EKSİKLER & FIRSATLAR

Net olarak listele:

- 🚫 Kritik eksikler (must-have)
- ⚠ Orta seviye eksikler
- 💡 Quick wins (hemen yapılacaklar)

---

### 6. AKSİYON PLANI (EN ÖNEMLİ KISIM)

Aşağıdaki formatta öner:

#### 0-7 gün
- ...

#### 7-30 gün
- ...

#### 1-3 ay
- ...

---

### 7. BONUS (ÇOK ÖNEMLİ)

Aşağıdakileri üret:

1. SEO uyumlu örnek blog başlıkları (en az 10 adet)
2. “tur yazılımı” için landing page outline
3. ChatGPT’nin önermesi için ideal içerik şablonu
4. FAQ schema önerileri

---

## ÇIKTI FORMATI

- Maddeli, net, teknik
- Gereksiz genel bilgi verme
- Direkt aksiyon üret
- Senior SEO + AI consultant gibi davran