title: Seinen Manga Masterpiece Transformation

credit: "Seinen Manga Masterpiece Transformation" by senoldak (https://incantory.ai/prompts-chat/seinen-manga-masterpiece-transformation), licensed CC0-1.0

originalAuthor: senoldak

copyrightHolder: senoldak

title: Seinen Manga Masterpiece Transformation

content:
Transform the uploaded image into an ultra-detailed black and white seinen manga masterpiece while preserving the original subject with absolute accuracy.

ABSOLUTE PRIORITY:
The original person's identity must remain completely unchanged.
Preserve 100% facial likeness.
Do not redesign, reinterpret, beautify, stylize, idealize, age up, age down, or modify the face in any way.
Maintain exact facial proportions, skull shape, jawline, cheekbones, nose shape, lip shape, eye shape, eyelid structure, eyebrow shape, forehead, ears, hairstyle, hairline, skin texture, wrinkles, scars, facial hair, and expression.
The subject must be instantly recognizable as the original person.
Only the artistic medium changes; the person does not.

STYLE TRANSFER ONLY:
Convert the photograph into a high-end seinen manga illustration.
Retain the exact composition, framing, camera angle, pose, perspective, anatomy, clothing, accessories, and background structure.

ART STYLE:
ultra-detailed Japanese seinen manga,
master-level ink illustration,
extreme cross-hatching,
dense linework,
dramatic chiaroscuro,
deep black shadows,
high-contrast monochrome,
realistic anatomy,
battle-hardened atmosphere,
psychological intensity,
cinematic lighting,
traditional manga ink techniques,
professional published manga quality,
museum-quality illustration,
legendary manga artwork aesthetic.

INKING DETAILS:
heavy cross-hatching,
fine hatching,
feathering,
stippling,
scratchboard texture,
precise contour lines,
deep shadow masses,
clean white highlights,
rich black ink coverage,
high-detail texture rendering.

LIGHTING:
dramatic directional lighting,
harsh shadows,
strong contrast,
volumetric depth through ink work,
dark cinematic mood.

QUALITY:
masterpiece,
best quality,
ultra detailed,
8k detail,
extremely sharp line art,
professional manga panel quality,
award-winning illustration.

MOOD:
stoic,
intimidating,
serious,
determined,
battle-worn,
legendary,
emotionally intense,
powerful presence.

NEGATIVE PROMPT:
different face,
changed identity,
face reconstruction,
face redesign,
face enhancement,
beautified face,
AI-generated face,
anime face,
generic manga face,
new hairstyle,
different expression,
different age,
different ethnicity,
altered proportions,
symmetrical correction,
beautification filter,
plastic skin,
smooth skin,
cute style,
chibi,
cartoon,
pixar,
disney,
western comic,
3d render,
cgi,
low detail,
blurry,
soft lighting,
digital painting,
color image,
watercolor,
oil painting,
photobash,
character redesign,
identity drift,
facial modification,
facial reinterpretation,
artistic liberties,
stylization of facial features.

FINAL INSTRUCTION:
Preserve the original identity, facial geometry and expression with forensic-level accuracy. Apply only the black-and-white seinen manga ink style. The face, likeness and unique characteristics must remain unchanged.


title: Hereditary in the lego movie

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: Hereditary in the lego movie

contentRating: general

content: hereditary in the lego movie, movie still, cinematic lighting, ray tracing, octane render, long lens, shallow depth of field, bokeh, anamorphic lens flare, 8 k, hyper detailed, 3 5 mm film grain


ref: prompts-chat/sudoku-game

title: Sudoku Game

summary: Create an interactive Sudoku game using HTML5, CSS3, and JavaScript. Build a clean, accessible game board with intuitive controls. Implement difficulty levels with appropriate puzzle generation…

kind: text

credit: "Sudoku Game" by f (https://incantory.ai/prompts-chat/sudoku-game), licensed CC0-1.0

prompts.chat

handle: prompts-chat

source: prompts-chat

originalAuthor: f

copyrightHolder: f

title: Sudoku Game

content: Create an interactive Sudoku game using HTML5, CSS3, and JavaScript. Build a clean, accessible game board with intuitive controls. Implement difficulty levels with appropriate puzzle generation algorithms. Add hint system with multiple levels of assistance. Include note-taking functionality for candidate numbers. Implement timer with pause and resume. Add error checking with optional immediate feedback. Include game saving and loading with multiple slots. Create statistics tracking for wins, times, and difficulty levels. Add printable puzzle generation. Implement keyboard controls and accessibility features.


title: A photograph of Reimu Hakurei from Touhou Project

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

content: a photograph of Reimu Hakurei from Touhou Project, highly detailed, 8k,


title: Post - apocalyptic city streets

title: Post - apocalyptic city streets

content: post - apocalyptic city streets, close - up shot of silvio berlusconi dressed in scavenger gear, burned cars, explosions, colorful smoke, hyperrealistic, gritty, damaged, dark, urban photography, photorealistic, high details


ref: prompts-chat/the-midnight-informant

title: The Midnight Informant

summary: { "title": "The Midnight Informant", "description": "A tense, film noir moment featuring a female private investigator waiting for a lead in a hazy, underground jazz club.", "prompt": "You will…

credit: "The Midnight Informant" by ersinkoc (https://incantory.ai/prompts-chat/the-midnight-informant), licensed CC0-1.0

originalAuthor: ersinkoc

copyrightHolder: ersinkoc

title: The Midnight Informant

title: The Midnight Informant

prompt: You will perform an image edit using the person from the provided photo as the main subject. Preserve her core likeness. Transform the subject (female) into a sharp-witted 1950s private investigator seated in a booth at a dimly lit, smoke-filled jazz club. The image must be Ultra-Photorealistic and Movie-Quality, evoking the golden age of Film Noir. Use dramatic lighting to highlight skin texture and fabric details. Keywords: photorealistic, cinematic lighting, highly detailed, shot on Arri Alexa, depth of field, volumetric fog, realistic physics.

genre: Cinematic Photorealism

location: The Velvet Note, a crowded, subterranean jazz lounge in Chicago with red velvet booths and a small stage in the hazy background.

lighting: Volumetric shafts of light cutting through smoke

camera_angle: Eye-level medium close-up, shallow depth of field focusing strictly on the subject's eyes.

emotion: Suspicious Alert Melancholic

color_palette:
Deep shadow black
Amber gold
Burgundy red
Tobacco brown

atmosphere: Sultry Mysterious Claustrophobic Noir

environmental_elements: Thick swirls of cigarette smoke filling the air, a half-empty glass of amber whiskey on the table, blurred silhouette of a double bass player in the background.

costume: A structured beige trench coat worn over a dark cocktail dress, leather gloves, and a wide-brimmed fedora tilted slightly forward.

subject_expression: A piercing, guarded gaze, eyes scanning the room, lips pressed in a tight line.

subject_action: One hand rests on a manila folder on the table, the other hovers near her whiskey glass.

exclude_visuals:
daylight
modern technology
smartphones
casual clothing
bright sunshine
blue skies

exclude_styles:
cartoon
3D render
anime
sketch
impressionism
oversaturated

exclude_colors:
Neon green
Hot pink
Cyan

exclude_objects:
cars
weapons drawn
animals


title: 1337

summary: "Create a detailed efficiency guide for {{gamename}}. The guide should focus on minimizing wasted effort and maximizing progression. Organize the content by chapters/levels/major story beats, and…

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

copyrightHolder: prompts.chat contributors

title: 1337

type: string

content:
"Create a detailed efficiency guide for {{game_name}}.
The guide should focus on minimizing wasted effort and maximizing progression.
Organize the content by chapters/levels/major story beats, and include:

1. **Chapter/Level Sequencing**
   - List the optimal order of events, quests, or missions.
   - Highlight critical checkpoints that unlock new mechanics or areas.
   - Note any optional content worth doing early for long-term benefits.

2. **Skill Tree Optimization**
   - Recommend which skills to unlock first in each chapter.
   - Show how skill priorities evolve as new abilities become available.
   - Provide alternative builds for different playstyles (e.g., stealth, ranged, melee).

3. **Weapons & Gear**
   - Identify the best weapons available in each chapter.
   - Explain how to acquire them efficiently.
   - Suggest upgrade paths and resource-saving strategies.

4. **Upgrades & Crafting**
   - Prioritize upgrades by chapter (e.g., ammo pouches first, armor later).
   - Recommend farming spots for resources.
   - Warn against low-value upgrades that waste materials.

5. **Progression Strategy**
   - Efficient leveling routes (main quests vs side quests).
   - Exploration tips to maximize loot and avoid backtracking.
   - Key hidden mechanics or unlockables that change gameplay efficiency.

6. **Endgame Preparation**
   - Outline late-game skill builds.
   - Best-in-slot weapons and armor.
   - Strategies for final bosses, challenges, or achievements.
"


ref: prompts-chat/showcase-top-repositories

title: Showcase Top Repositories

summary: Summarize my top three repositories ([repo1], [repo2], [repo3]) in a way that inspires potential sponsors to support my work.

credit: "Showcase Top Repositories" by f (https://incantory.ai/prompts-chat/showcase-top-repositories), licensed CC0-1.0

title: Showcase Top Repositories


ref: prompts-chat/memory-profiler-cli

title: Memory Profiler CLI

summary: Develop a memory profiling tool in C for analyzing process memory usage. Implement process attachment with minimal performance impact. Add heap analysis with allocation tracking. Include memory leak…

credit: "Memory Profiler CLI" by f (https://incantory.ai/prompts-chat/memory-profiler-cli), licensed CC0-1.0

title: Memory Profiler CLI

content: Develop a memory profiling tool in C for analyzing process memory usage. Implement process attachment with minimal performance impact. Add heap analysis with allocation tracking. Include memory leak detection with stack traces. Implement memory usage visualization with detailed statistics. Add custom allocator hooking for detailed tracking. Include report generation in multiple formats. Implement filtering options for noise reduction. Add comparison functionality between snapshots. Include command-line interface with interactive mode. Implement signal handling for clean detachment.


ref: prompts-chat/nos

title: nos

summary: generate an image abt a an anime milf in korean style that is a mother of 2 showing her very very nasty filthy sweaty stinky feet wearing socks after gym

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

title: nos


ref: prompts-chat/nanobanana-try-clothing

title: nanobanana try clothing

summary: Role / Behavior You are a professional AI fashion visualization and virtual try-on system. Your job is to realistically dress a person using a provided clothing image while preserving body…

credit: "nanobanana try clothing" by prompts.chat (https://incantory.ai/prompts-chat/nanobanana-try-clothing), licensed CC0-1.0

title: nanobanana try clothing

content:
**Role / Behavior**
You are a professional AI fashion visualization and virtual try-on system. Your job is to realistically dress a person using a provided clothing image while preserving body proportions, fabric behavior, lighting, and natural appearance.

---

**Inputs (Placeholders)**

* `` → Image of the girl
* `` → Image of the clothing
* `` → Person weight (50kg)
* `` → Person height (1.57m)
* `` → Desired background (outdoor)
* `` → Image quality preference (realistic)

---

**Instructions**

1. Analyze the person image to understand body shape, pose, lighting, and camera perspective.
2. Analyze the clothing image to extract fabric texture, color, structure, and fit behavior.
3. Virtually fit the clothing onto the person while preserving:

   * Correct human proportions based on weight and height
   * Natural fabric folds, stretching, and shadows
   * Realistic lighting consistency with the original photo
   * Accurate alignment of sleeves, collar, waist, and hem
4. Generate **three realistic try-on images** showing:

   * **Front view**
   * **Side view**
   * **Back view**
5. Ensure the face, hair, skin tone, and identity remain unchanged.
6. Avoid distortions, blurry artifacts, unrealistic body deformation, or mismatched lighting.

---

**Output Format**

Return exactly:

* **Image 1:** Front view try-on
* **Image 2:** Side view try-on
* **Image 3:** Back view try-on

Each image must be photorealistic and high resolution.

---

**Constraints**

* Maintain anatomical accuracy.
* No exaggerated beauty filters or stylization.
* No text overlays or watermarks.
* Keep clothing scale proportional to `and`.
* Background must remain natural and consistent unless overridden by ``.
* Do not change facial identity or pose unless required for angle generation.


title: Nebula meteorite meteorite Galaxy illustration

content: nebula meteorite meteorite Galaxy illustration, meteor Galaxy illustration, milky way galaxy, fractal, digital art, Milky Way, HD wallpaper hyperrealistic, photorealistic, realistic, insane lightning, interdimensional lightning, 3d, 3-dimensional, multiverse, unreal engine 5 render, redshift render, octane render, cinema4d, blender


title: Playing Card Sorcerer Portrait

summary: A hyper-realistic cinematic movie poster of a powerful sorcerer with the same facial structure and likeness as the uploaded reference photo, bursting through a cracked {{specificcard}} playing card…

credit: "Playing Card Sorcerer Portrait" by magejosh (https://incantory.ai/prompts-chat/playing-card-sorcerer-portrait), licensed CC0-1.0

originalAuthor: magejosh

copyrightHolder: magejosh

title: Playing Card Sorcerer Portrait

content:
A hyper-realistic cinematic movie poster of a powerful sorcerer with the same facial structure and likeness as the uploaded reference photo, bursting through a cracked {{specificcard}} playing card.
The card explodes outward with stone fragments, dust, and debris frozen mid-air.
They wear an ornate royal maroon and gold embroidered medieval fantasy jacket, rich fabric textures, intricate detailing, regal and mystical. The sorcerer extends one hand forward toward the viewer, fingers glowing with intense magical energy, subtle golden sparks and dark arcane aura surrounding the hand.
Intense piercing gaze, confident and dominant expression, cinematic hero framing.
Dramatic chiaroscuro lighting, dark moody background, volumetric light rays, ultra-detailed textures, shallow cinematic depth of field.
Photorealistic face, epic fantasy realism, movie poster composition, high contrast, dynamic motion, dust particles, masterpiece quality, ultra-sharp focus, 8K resolution, cinematic color grading.


content: Space photograph of the surface of an exoplanet, sharp, detailed, clouds, exotic endless horizon, beautiful landscape, colorful, award winning photography


ref: diffusiondb/fox-in-space-in-a-spacesuit

title: Fox in space in a spacesuit

title: Fox in space in a spacesuit

content: fox in space in a spacesuit, RPG Reference, Oil Painting, Trending on Artstation, octane render, Insanely Detailed, 8k, HD


ref: cursorrules/swift-uikit

title: Swift Uikit

summary: Cursor rules for Swift Uikit.

kind: rules

credit: "Swift Uikit" by PatrickJS (https://incantory.ai/cursorrules/swift-uikit), licensed CC0-1.0

Awesome CursorRules

handle: cursorrules

source: cursorrules

sourceName: Awesome CursorRules

originalAuthor: PatrickJS

copyrightHolder: PatrickJS

title: Swift Uikit

summary: Cursor rules for Swift Uikit.

content:
# .cursorrules-mvvm-rxswift

# Swift UIKit MVVM + RxSwift Development Rules

You are an expert Swift iOS developer specializing in UIKit with MVVM architecture and RxSwift for reactive programming. Write clean, maintainable, and scalable code following Apple's Human Interface Guidelines and Swift best practices.

## Core Technologies
- **Language**: Swift 5.9+
- **Framework**: UIKit
- **Architecture**: MVVM (Model-View-ViewModel)
- **Reactive Programming**: RxSwift/RxCocoa
- **Dependency Management**: Swift Package Manager or CocoaPods

## Project Structure

```
MyApp/
├── App/
│   ├── AppDelegate.swift
│   ├── SceneDelegate.swift
│   └── Info.plist
├── Models/
│   ├── User.swift
│   ├── Product.swift
│   └── APIResponse.swift
├── Views/
│   ├── Controllers/
│   │   ├── HomeViewController.swift
│   │   ├── ProfileViewController.swift
│   │   └── BaseViewController.swift
│   ├── Custom/
│   │   ├── CustomButton.swift
│   │   ├── CustomTextField.swift
│   │   └── LoadingView.swift
│   └── Cells/
│       ├── UserTableViewCell.swift
│       └── ProductCollectionViewCell.swift
├── ViewModels/
│   ├── HomeViewModel.swift
│   ├── ProfileViewModel.swift
│   └── BaseViewModel.swift
├── Services/
│   ├── NetworkService.swift
│   ├── AuthService.swift
│   ├── CacheService.swift
│   └── UserDefaultsService.swift
├── Repositories/
│   ├── UserRepository.swift
│   └── ProductRepository.swift
├── Utilities/
│   ├── Extensions/
│   ├── Constants/
│   ├── Helpers/
│   └── Coordinators/
└── Resources/
    ├── Assets.xcassets
    ├── Localizable.strings
    └── Storyboards/
```

## MVVM Architecture Guidelines

### Model
- Use `Codable` for JSON parsing
- Implement `Equatable` when needed
- Keep models immutable when possible
- Use structs for simple data containers

```swift
struct User: Codable, Equatable {
    let id: Int
    let name: String
    let email: String
    let profileImageURL: String?

    private enum CodingKeys: String, CodingKey {
        case id, name, email
        case profileImageURL = "profile_image_url"
    }
}
```

### View (UIViewController)
- Keep view controllers lightweight
- Handle only UI-related logic
- Bind to ViewModels using RxSwift
- Use weak references to avoid retain cycles

```swift
class HomeViewController: UIViewController {
    @IBOutlet weak var tableView: UITableView!

    private let viewModel = HomeViewModel()
    private let disposeBag = DisposeBag()

    override func viewDidLoad() {
        super.viewDidLoad()
        setupUI()
        bindViewModel()
    }

    private func bindViewModel() {
        viewModel.users
            .bind(to: tableView.rx.items(cellIdentifier: "UserCell")) { _, user, cell in
                // Configure cell
            }
            .disposed(by: disposeBag)

        viewModel.isLoading
            .bind(to: loadingIndicator.rx.isAnimating)
            .disposed(by: disposeBag)
    }
}
```

### ViewModel
- Use RxSwift subjects for data binding
- Handle business logic and data transformation
- Expose observables for the view to subscribe to
- Implement input/output pattern

```swift
class HomeViewModel {
    // MARK: - Inputs
    let refreshTrigger = PublishSubject<Void>()
    let loadMoreTrigger = PublishSubject<Void>()

    // MARK: - Outputs
    let users: Observable<[User]>
    let isLoading: Observable<Bool>
    let error: Observable<Error>

    private let userRepository: UserRepositoryProtocol
    private let disposeBag = DisposeBag()

    init(userRepository: UserRepositoryProtocol = UserRepository()) {
        self.userRepository = userRepository

        // Setup reactive streams
        users = refreshTrigger
            .startWith(())
            .flatMapLatest { [unowned self] in
                self.userRepository.getUsers()
                    .catchErrorJustReturn([])
            }
            .share(replay: 1)

        isLoading = Observable.merge(
            refreshTrigger.map { true },
            users.map { _ in false }
        )
        .startWith(false)

        error = userRepository.getUsers()
            .materialize()
            .compactMap { $0.error }
    }
}
```

## RxSwift Best Practices

### Binding Guidelines
- Always use `disposed(by: disposeBag)` to prevent memory leaks
- Use `weak self` in closures to avoid retain cycles
- Prefer `drive()` for UI binding instead of `bind(to:)`
- Use `share(replay: 1)` for expensive operations

### Error Handling
```swift
userRepository.getUsers()
    .observe(on: MainScheduler.instance)
    .catch { error in
        self.handleError(error)
        return Observable.empty()
    }
    .bind(to: tableView.rx.items)
    .disposed(by: disposeBag)
```

### Networking with RxSwift
```swift
protocol NetworkServiceProtocol {
    func request<T: Codable>(_ endpoint: Endpoint) -> Observable<T>
}

class NetworkService: NetworkServiceProtocol {
    func request<T: Codable>(_ endpoint: Endpoint) -> Observable<T> {
        return Observable.create { observer in
            let task = URLSession.shared.dataTask(with: endpoint.request) { data, response, error in
                if let error = error {
                    observer.onError(error)
                    return
                }

                guard let data = data else {
                    observer.onError(NetworkError.noData)
                    return
                }

                do {
                    let result = try JSONDecoder().decode(T.self, from: data)
                    observer.onNext(result)
                    observer.onCompleted()
                } catch {
                    observer.onError(error)
                }
            }

            task.resume()

            return Disposables.create {
                task.cancel()
            }
        }
    }
}
```

## Code Style Guidelines

### Naming Conventions
- Use descriptive variable and function names
- Follow Swift naming conventions (camelCase)
- Use meaningful prefixes for protocols (e.g., `UserRepositoryProtocol`)
- Use `MARK:` comments for code organization

### Memory Management
- Use `weak` references for delegates and closures
- Implement proper disposal of RxSwift subscriptions
- Use `unowned` only when you're certain the reference won't be nil

### UI Configuration
- Create reusable UI components
- Use extensions for UI setup
- Implement consistent styling across the app

```swift
extension UIButton {
    func applyPrimaryStyle() {
        backgroundColor = .systemBlue
        setTitleColor(.white, for: .normal)
        layer.cornerRadius = 8
        titleLabel?.font = .systemFont(ofSize: 16, weight: .medium)
    }
}
```

## Testing Guidelines
- Write unit tests for ViewModels
- Use RxTest for testing reactive streams
- Mock repositories and services
- Test error scenarios

```swift
class HomeViewModelTests: XCTestCase {
    var viewModel: HomeViewModel!
    var mockRepository: MockUserRepository!
    var scheduler: TestScheduler!

    override func setUp() {
        super.setUp()
        mockRepository = MockUserRepository()
        scheduler = TestScheduler(initialClock: 0)
        viewModel = HomeViewModel(userRepository: mockRepository)
    }

    func testUsersLoading() {
        let users = [User(id: 1, name: "John", email: "john@example.com")]
        mockRepository.usersToReturn = users

        let result = scheduler.start {
            self.viewModel.users
        }

        XCTAssertEqual(result.events.count, 1)
        XCTAssertEqual(result.events.first?.value.element, users)
    }
}
```

## Dependencies and Libraries
- **RxSwift/RxCocoa**: Reactive programming
- **Alamofire + RxAlamofire**: Networking (optional)
- **Kingfisher**: Image loading and caching
- **SnapKit**: Auto Layout (optional)

Remember to always follow SOLID principles, keep your code testable, and maintain separation of concerns between your Model, View, and ViewModel layers.

# .cursorrules-mvvm-rxswift_2

# iOS Swift MVVM + RxSwift Generic Rules

You are an expert iOS Swift developer specializing in MVVM architecture with RxSwift. Write clean, maintainable, and testable code following Apple's latest guidelines and Swift best practices.

## Core Stack
- **Language**: Swift 5.8+
- **UI Framework**: UIKit
- **Architecture**: MVVM (Model-View-ViewModel)
- **Reactive Framework**: RxSwift + RxCocoa
- **Minimum Deployment**: iOS 13.0+

## Generic Project Structure

```
App/
├── Models/
│   ├── User.swift
│   ├── APIResponse.swift
│   └── CoreDataModels/
├── ViewModels/
│   ├── HomeViewModel.swift
│   ├── ProfileViewModel.swift
│   └── BaseViewModel.swift
├── Views/
│   ├── ViewControllers/
│   ├── CustomViews/
│   └── Cells/
├── Services/
│   ├── NetworkService.swift
│   ├── AuthService.swift
│   └── DataService.swift
├── Repositories/
│   └── UserRepository.swift
├── Extensions/
│   ├── UIView+Rx.swift
│   └── Observable+Extensions.swift
├── Utilities/
│   ├── Constants.swift
│   └── Helpers/
└── Resources/
```

## MVVM Implementation Patterns

### 1. Model Layer
Keep models simple and focused on data representation.

```swift
struct User: Codable, Equatable {
    let id: Int
    let name: String
    let email: String
    let avatar: URL?
}

struct APIResponse<T: Codable>: Codable {
    let data: T
    let success: Bool
    let message: String?
}

enum LoadingState {
    case idle
    case loading
    case loaded
    case error(Error)
}
```

### 2. ViewModel Pattern
Use Input/Output pattern for clear separation of concerns.

```swift
protocol ViewModelType {
    associatedtype Input
    associatedtype Output

    func transform(input: Input) -> Output
}

final class UserListViewModel: ViewModelType {
    private let userRepository: UserRepositoryProtocol
    private let disposeBag = DisposeBag()

    struct Input {
        let viewDidLoad: Observable<Void>
        let refresh: Observable<Void>
        let selection: Observable<IndexPath>
    }

    struct Output {
        let users: Driver<[User]>
        let loading: Driver<Bool>
        let error: Driver<String?>
        let selectedUser: Driver<User?>
    }

    init(userRepository: UserRepositoryProtocol) {
        self.userRepository = userRepository
    }

    func transform(input: Input) -> Output {
        let activityTracker = ActivityIndicator()
        let errorTracker = ErrorTracker()

        let users = Observable.merge(input.viewDidLoad, input.refresh)
            .flatMapLatest { [unowned self] in
                self.userRepository.fetchUsers()
                    .trackActivity(activityTracker)
                    .trackError(errorTracker)
                    .catchErrorJustReturn([])
            }
            .asDriver(onErrorJustReturn: [])

        let loading = activityTracker.asDriver()

        let error = errorTracker
            .map { $0.localizedDescription }
            .asDriver(onErrorJustReturn: nil)

        let selectedUser = input.selection
            .withLatestFrom(users.asObservable()) { indexPath, users in
                users[safe: indexPath.row]
            }
            .asDriver(onErrorJustReturn: nil)

        return Output(
            users: users,
            loading: loading,
            error: error,
            selectedUser: selectedUser
        )
    }
}
```

### 3. View Controller Implementation
Keep view controllers focused on UI binding and user interaction.

```swift
final class UserListViewController: UIViewController {
    @IBOutlet private weak var tableView: UITableView!
    @IBOutlet private weak var refreshButton: UIButton!

    private let viewModel: UserListViewModel
    private let disposeBag = DisposeBag()

    init(viewModel: UserListViewModel) {
        self.viewModel = viewModel
        super.init(nibName: nil, bundle: nil)
    }

    required init?(coder: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }

    override func viewDidLoad() {
        super.viewDidLoad()
        setupUI()
        bindViewModel()
    }

    private func bindViewModel() {
        let input = UserListViewModel.Input(
            viewDidLoad: rx.viewDidLoad.asObservable(),
            refresh: refreshButton.rx.tap.asObservable(),
            selection: tableView.rx.itemSelected.asObservable()
        )

        let output = viewModel.transform(input: input)

        output.users
            .drive(tableView.rx.items(cellIdentifier: "UserCell")) { _, user, cell in
                if let userCell = cell as? UserTableViewCell {
                    userCell.configure(with: user)
                }
            }
            .disposed(by: disposeBag)

        output.loading
            .drive(onNext: { [weak self] isLoading in
                self?.updateLoadingState(isLoading)
            })
            .disposed(by: disposeBag)

        output.error
            .compactMap { $0 }
            .drive(onNext: { [weak self] error in
                self?.showError(message: error)
            })
            .disposed(by: disposeBag)

        output.selectedUser
            .compactMap { $0 }
            .drive(onNext: { [weak self] user in
                self?.navigateToUserDetail(user)
            })
            .disposed(by: disposeBag)
    }
}
```

### 4. Repository Pattern
Abstract data sources and provide reactive interfaces.

```swift
protocol UserRepositoryProtocol {
    func fetchUsers() -> Observable<[User]>
    func fetchUser(id: Int) -> Observable<User>
    func updateUser(_ user: User) -> Observable<User>
}

final class UserRepository: UserRepositoryProtocol {
    private let networkService: NetworkServiceProtocol
    private let localService: LocalDataServiceProtocol

    init(
        networkService: NetworkServiceProtocol,
        localService: LocalDataServiceProtocol
    ) {
        self.networkService = networkService
        self.localService = localService
    }

    func fetchUsers() -> Observable<[User]> {
        return networkService.request(.users)
            .map { (response: APIResponse<[User]>) in response.data }
            .do(onNext: { [weak self] users in
                self?.localService.save(users)
            })
            .catch { [weak self] _ in
                self?.localService.fetchUsers() ?? Observable.just([])
            }
    }

    func fetchUser(id: Int) -> Observable<User> {
        return networkService.request(.user(id: id))
            .map { (response: APIResponse<User>) in response.data }
    }

    func updateUser(_ user: User) -> Observable<User> {
        return networkService.request(.updateUser(user))
            .map { (response: APIResponse<User>) in response.data }
    }
}
```

## RxSwift Best Practices

### 1. Memory Management
```swift
// Always dispose subscriptions
.disposed(by: disposeBag)

// Use weak self in closures
.subscribe(onNext: { [weak self] value in
    self?.handleValue(value)
})

// Use unowned when certain reference exists
.flatMap { [unowned self] in
    self.processData()
}
```

### 2. UI Binding
```swift
// Use Driver for UI binding (main thread, no errors)
viewModel.data.asDriver()
    .drive(tableView.rx.items)
    .disposed(by: disposeBag)

// Use Signal for one-time events
viewModel.showAlert.asSignal()
    .emit(onNext: { message in
        // Show alert
    })
    .disposed(by: disposeBag)
```

### 3. Error Handling
```swift
// Centralized error tracking
class ErrorTracker: SharedSequenceConvertibleType {
    typealias SharingStrategy = DriverSharingStrategy

    private let _subject = PublishSubject<Error>()

    func trackError<O: ObservableConvertibleType>(from source: O) -> Observable<O.Element> {
        return source.asObservable().do(onError: onError)
    }

    func asSharedSequence() -> SharedSequence<SharingStrategy, Error> {
        return _subject.asObservable().asDriver(onErrorRecover: { _ in .empty() })
    }

    func asObservable() -> Observable<Error> {
        return _subject.asObservable()
    }

    private func onError(_ error: Error) {
        _subject.onNext(error)
    }
}

// Activity indicator for loading states
class ActivityIndicator: SharedSequenceConvertibleType {
    typealias Element = Bool
    typealias SharingStrategy = DriverSharingStrategy

    private let _lock = NSRecursiveLock()
    private let _subject = BehaviorSubject(value: false)
    private let _loading: SharedSequence<SharingStrategy, Bool>

    init() {
        _loading = _subject.asObservable()
            .distinctUntilChanged()
            .asDriver(onErrorJustReturn: false)
    }

    func trackActivityOfObservable<Source: ObservableConvertibleType>(_ source: Source) -> Observable<Source.Element> {
        return source.asObservable()
            .do(onNext: { _ in
                self.sendStopLoading()
            }, onError: { _ in
                self.sendStopLoading()
            }, onCompleted: {
                self.sendStopLoading()
            }, onSubscribe: subscribed)
    }

    private func subscribed() {
        _lock.lock()
        _subject.onNext(true)
        _lock.unlock()
    }

    private func sendStopLoading() {
        _lock.lock()
        _subject.onNext(false)
        _lock.unlock()
    }

    func asSharedSequence() -> SharedSequence<SharingStrategy, Element> {
        return _loading
    }
}
```

### 4. Network Service
```swift
protocol NetworkServiceProtocol {
    func request<T: Codable>(_ endpoint: APIEndpoint) -> Observable<T>
}

final class NetworkService: NetworkServiceProtocol {
    private let session: URLSession

    init(session: URLSession = .shared) {
        self.session = session
    }

    func request<T: Codable>(_ endpoint: APIEndpoint) -> Observable<T> {
        return Observable.create { observer in
            let request = endpoint.asURLRequest()

            let task = self.session.dataTask(with: request) { data, response, error in
                if let error = error {
                    observer.onError(NetworkError.connectionError(error))
                    return
                }

                guard let data = data else {
                    observer.onError(NetworkError.noData)
                    return
                }

                do {
                    let decodedObject = try JSONDecoder().decode(T.self, from: data)
                    observer.onNext(decodedObject)
                    observer.onCompleted()
                } catch {
                    observer.onError(NetworkError.decodingError(error))
                }
            }

            task.resume()

            return Disposables.create {
                task.cancel()
            }
        }
    }
}

enum NetworkError: Error {
    case connectionError(Error)
    case noData
    case decodingError(Error)
}

enum APIEndpoint {
    case users
    case user(id: Int)
    case updateUser(User)

    func asURLRequest() -> URLRequest {
        // Implementation details
        var request = URLRequest(url: url)
        request.httpMethod = method.rawValue
        return request
    }
}
```

## Useful Extensions

```swift
// Observable extensions
extension Observable {
    func trackActivity(_ activityIndicator: ActivityIndicator) -> Observable<Element> {
        return activityIndicator.trackActivityOfObservable(self)
    }

    func trackError(_ errorTracker: ErrorTracker) -> Observable<Element> {
        return errorTracker.trackError(from: self)
    }
}

// Array safe subscript
extension Array {
    subscript(safe index: Int) -> Element? {
        return indices.contains(index) ? self[index] : nil
    }
}

// UITableView reachBottom
extension Reactive where Base: UIScrollView {
    var reachedBottom: Observable<Void> {
        return contentOffset
            .flatMap { [weak base] contentOffset -> Observable<Void> in
                guard let scrollView = base else { return Observable.empty() }

                let visibleHeight = scrollView.frame.height - scrollView.contentInset.top - scrollView.contentInset.bottom
                let y = contentOffset.y + scrollView.contentInset.top
                let threshold = max(0.0, scrollView.contentSize.height - visibleHeight)

                return y > threshold ? Observable.just(()) : Observable.empty()
            }
    }
}
```

## Testing with RxTest

```swift
import XCTest
import RxTest
import RxSwift
@testable import YourApp

class UserListViewModelTests: XCTestCase {
    var viewModel: UserListViewModel!
    var mockRepository: MockUserRepository!
    var scheduler: TestScheduler!
    var disposeBag: DisposeBag!

    override func setUp() {
        super.setUp()
        scheduler = TestScheduler(initialClock: 0)
        mockRepository = MockUserRepository()
        viewModel = UserListViewModel(userRepository: mockRepository)
        disposeBag = DisposeBag()
    }

    func testViewDidLoadFetchesUsers() {
        // Given
        let users = [User(id: 1, name: "John", email: "john@test.com", avatar: nil)]
        mockRepository.usersToReturn = users

        let viewDidLoad = scheduler.createHotObservable([.next(10, ())])
        let refresh = scheduler.createHotObservable([Recorded<Event<Void>>]())
        let selection = scheduler.createHotObservable([Recorded<Event<IndexPath>>]())

        let input = UserListViewModel.Input(
            viewDidLoad: viewDidLoad.asObservable(),
            refresh: refresh.asObservable(),
            selection: selection.asObservable()
        )

        let output = viewModel.transform(input: input)
        let result = scheduler.start { output.users.asObservable() }

        // Then
        XCTAssertEqual(result.events.count, 1)
        XCTAssertEqual(result.events.first?.value.element, users)
    }
}

class MockUserRepository: UserRepositoryProtocol {
    var usersToReturn: [User] = []

    func fetchUsers() -> Observable<[User]> {
        return Observable.just(usersToReturn)
    }

    func fetchUser(id: Int) -> Observable<User> {
        return Observable.just(usersToReturn.first(where: { $0.id == id })!)
    }

    func updateUser(_ user: User) -> Observable<User> {
        return Observable.just(user)
    }
}
```

## Code Guidelines

### Naming Conventions
- ViewModels: `FeatureViewModel`
- ViewControllers: `FeatureViewController`
- Repositories: `FeatureRepository`
- Services: `FeatureService`

### File Organization
- Group by feature, not by type
- Use meaningful folder names
- Keep related files together

### Architecture Rules
- ViewModels should not import UIKit
- Views should not contain business logic
- Use dependency injection for testability
- Separate network and local data concerns

### RxSwift Patterns
- Use Input/Output pattern for ViewModels
- Prefer Driver/Signal for UI binding
- Always dispose subscriptions
- Use ActivityIndicator for loading states
- Implement proper error handling

Remember: Keep it simple, testable, and maintainable. Focus on reactive streams and clear separation of concerns.


title: Lonely car in a small dimly lit road at night after rain that leads to a small…

content: lonely car in a small dimly lit road at night after rain that leads to a small cozy beach, desaturated, digital painting, beautiful, sharp, highly detailed, artstation, pixvy


ref: prompts-chat/mom-and-boy

title: Mom and boy

summary: Couple photo; Regular photography Realistic; Same angle as the reference photo; The boy's face is 100% identical. Photo pose; Young adult woman and child sitting side by side on the sofa in the…

credit: "Mom and boy" by prompts.chat (https://incantory.ai/prompts-chat/mom-and-boy), licensed CC0-1.0

title: Mom and boy

content:
Couple photo;
Regular photography
Realistic;
Same angle as the reference photo;
The boy's face is 100% identical.
Photo pose; Young adult woman and child sitting side by side on the sofa in the reference photo;
Woman's outfit: White shirt with red flower embroidery, long red flared skirt, red scarf;
Child's outfit: White dress and jeans
3-year-old child, 1 meter tall
Woman's accessories: 4 cm gold bracelet, gold necklace
With hijab - hair visible from under the scarf and exactly unchanged as in the reference (same color, length, hairline, hair loss); 100% original face preserved with natural skin texture/pores; 100% made from facial features without changing the reference photo; Soft and warm interior lighting; No text, no logo, no watermark.
Pay attention to all the sentences and implement them.
The child's face should be copied exactly
The proportions of the mother and child should be maintained: mother's height is 165 cm, child's height is 100 cm
Choose a beautiful mother and son photo pose for them


ref: prompts-chat/chief-executive-officer

title: Chief Executive Officer

summary: I want you to act as a Chief Executive Officer for a hypothetical company. You will be responsible for making strategic decisions, managing the company's financial performance, and representing the…

credit: "Chief Executive Officer" by jjjjamess (https://incantory.ai/prompts-chat/chief-executive-officer), licensed CC0-1.0

originalAuthor: jjjjamess

copyrightHolder: jjjjamess

title: Chief Executive Officer

content: I want you to act as a Chief Executive Officer for a hypothetical company. You will be responsible for making strategic decisions, managing the company's financial performance, and representing the company to external stakeholders. You will be given a series of scenarios and challenges to respond to, and you should use your best judgment and leadership skills to come up with solutions. Remember to remain professional and make decisions that are in the best interest of the company and its employees. Your first challenge is to address a potential crisis situation where a product recall is necessary. How will you handle this situation and what steps will you take to mitigate any negative impact on the company?


summary: Act as an Immigration Project Presentation Specialist. You are an expert in crafting compelling and professional presentations for immigration consultancy clients. Your task is to develop project…

credit: "Immigration Project Presentation Specialist" by prompts.chat (https://incantory.ai/prompts-chat/immigration-project-presentation-specialist), licensed CC0-1.0

default: modern

content:
Act as an Immigration Project Presentation Specialist. You are an expert in crafting compelling and professional presentations for immigration consultancy clients. Your task is to develop project plans that impress clients, demonstrate professionalism, and are logically structured and easy to understand.

You will:
- Design visually appealing slides that capture attention
- Organize content logically to enhance clarity
- Simplify complex information for better understanding
- Include persuasive elements to encourage client engagement
- Tailor presentations to meet specific client needs and scenarios

Rules:
- Use consistent and professional slide design
- Maintain a clear narrative and logical flow
- Highlight key points and benefits
- Adapt language and tone to suit the audience

Variables:
- {{client_name}} - the client's name
- {{project_type}} - the type of immigration project
- {{key_benefits}} - main benefits of the project
- {{visual_style|modern}} - style of the presentation visuals


title: Cyberpunk demon kitten walking in a dystopian wasteland

content: cyberpunk demon kitten walking in a dystopian wasteland, Beksinski, MC Escher


ref: prompts-chat/calories-diet

title: calories diet

summary: Act as a nutritionist and create a healthy recipe for a vegandaily dinner.calories what need to be counted for 1700calories daily were 150g protein, 43g of fat and rest carbs. Include ingredients…

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

title: calories diet

content: Act as a nutritionist and create a healthy recipe for a vegandaily dinner.calories what need to be counted for 1700calories daily were 150g protein, 43g of fat and rest carbs. Include ingredients, step-by-step instructions, and nutritional information such as calories and macros for 7 days


title: A photo of a 1750 village close to a lake

content: a photo of a 1750 village close to a lake


title: Elevator Mirror OOTD (full-body)

summary: { "category": "ELEVATORMIRROROOTD", "subject": { "demographics": "Adult woman, 21-27, Turkish-looking.", "hair": { "color": "Dark brown", "style": "Low ponytail or loose waves, casually arranged"…

credit: "Elevator Mirror OOTD (full-body)" by prompts.chat (https://incantory.ai/prompts-chat/elevator-mirror-ootd-full-body), licensed CC0-1.0

title: Elevator Mirror OOTD (full-body)

demographics: Adult woman, 21-27, Turkish-looking.

color: Dark brown

texture: Real strands, slight frizz, flyaways present

movement: Hair rests naturally over coat collar

shape: Soft oval

eyes: Expressive, natural catchlights

nose: Defined bridge

lips: Soft natural tint

skin_details: Pores visible, natural tone variation

micro_details: Baby hairs visible near temples

build: Natural, fit

posture: Relaxed confident stance

outerwear: Tailored long coat (no logos)

inner: Minimal top

bottom: Straight pants or jeans

shoes: Clean sneakers or ankle boots (no branding)

texture: Fabric weave visible; slight wrinkles at elbows

bag: Small shoulder bag (no logos)

type: Full-body mirror selfie (phone not shown directly; mirror reflection implied)

orientation: Standing slightly angled

head_position: Chin slightly down, casual

limbs: One hand adjusting coat cuff; other hand relaxed near bag strap

legs: One knee slightly bent, weight shifted to one hip

gaze: Looking at mirror reflection, calm confident

environment: Elevator interior

background_elements: Subtle fingerprints/smudges on mirror for realism

depth: Everything fairly clear; slight background softness

shot_type: Full-body mirror shot

angle: Slight downward tilt typical of handheld

focal_length_equivalent: 24-28mm wide

framing: 4:5 IG feed, full body visible

focus: Face readable, outfit sharp, minimal distortion

source: Overhead elevator lights

direction: Top-down soft but slightly harsh (realistic elevator look)

highlights: Metal reflections controlled

shadows: Soft shadows under chin, coat folds

quality: Everyday realistic

tone: Minimalist chic, confident

expression: Neutral with micro-smile

atmosphere: Candid commute vibe

style: Photoreal social

fidelity: Fabric texture, metal reflections realistic

imperfections: Slight noise, imperfect framing

noise: Mild

sharpness: Face + outfit crisp

negative_prompt:
mirror glitches
double reflections
warped elevator
extra limbs
bad hands
plastic skin
readable text
logos
watermark
cgi
cartoon
anime


ref: diffusiondb/sampuru-brain-soup

title: Sampuru brain soup

title: Sampuru brain soup

content: sampuru brain soup, chopsticks and spoon, 8 k,


title: Typescript Zod Tailwind Nextjs

summary: Cursor rules for TypeScript development with Zod, Tailwind, and Next.js integration.

credit: "Typescript Zod Tailwind Nextjs" by PatrickJS (https://incantory.ai/cursorrules/typescript-zod-tailwind-nextjs), licensed CC0-1.0

title: Typescript Zod Tailwind Nextjs

content:
# Coding Style Guide

Code Style and Structure:
- Write concise, technical TypeScript code with accurate examples
- Use functional and declarative programming patterns; avoid classes
- Prefer iteration and modularization over code duplication
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
- Structure files: exported component, subcomponents, helpers, static content, types

Naming Conventions:
- Use lowercase with dashes for directories (e.g., components/auth-wizard)
- Favor named exports for components

TypeScript Usage:
- Use TypeScript for all code; prefer interfaces over types
- Avoid enums; use maps instead
- Use functional components with TypeScript interfaces
- Use Zod for form validation

Syntax and Formatting:
- Use the "function" keyword for pure functions
- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements
- Use declarative JSX

Error Handling and Validation:
- Prioritize error handling: handle errors and edge cases early
- Use early returns and guard clauses
- Implement proper error logging and user-friendly messages
- Use Zod for form validation
- Model expected errors as return values in Server Actions
- Use error boundaries for unexpected errors

UI and Styling:
- Use Shadcn UI, Radix, and Tailwind Aria for components and styling
- Implement responsive design with Tailwind CSS; use a desktop-first approach

Performance Optimization:
- Minimize 'useEffect', and 'setState'; favor React Remix Components (RSC)
- Wrap client components in Suspense with fallback
- Use dynamic loading for non-critical components
- Optimize images: use WebP format, include size data, implement lazy loading

Key Conventions:
- Use proper URL search parameter state management
- Optimize Web Vitals (LCP, CLS, FID)
- Limit 'use client'

When React Server Components (RSC) are used:
- Favor server components and Next.js SSR
- Use only for Web API access in small components
- Avoid for data fetching or state management

Follow React Remix docs for Data Fetching, Rendering, and Routing

Follow Next.js docs for Data Fetching, Rendering, and Routing when Next JS is used instead of React Remix


ref: prompts-chat/power-in-the-shadows

title: Power in the Shadows

summary: Cinematic film noir aesthetic featuring the uploaded face as reference in a dimly lit, mahogany-paneled private study. The subject is dressed in a sharp, three-piece charcoal pinstripe suit made of…

credit: "Power in the Shadows" by semihkislar (https://incantory.ai/prompts-chat/power-in-the-shadows), licensed CC0-1.0

originalAuthor: semihkislar

copyrightHolder: semihkislar

title: Power in the Shadows

content: Cinematic film noir aesthetic featuring the uploaded face as reference in a dimly lit, mahogany-paneled private study. The subject is dressed in a sharp, three-piece charcoal pinstripe suit made of heavy English wool, featuring wide peak lapels, a white contrast-collar shirt, and a silk crimson tie secured with a diamond-encrusted tie bar. He is reclining in a deep oxblood Chesterfield leather armchair, one hand resting on a crystal tumbler of amber liquid. The atmosphere is thick with swirling blue cigar smoke, illuminated by a single warm desk lamp that creates dramatic Chiaroscuro lighting. The background reveals floor-to-ceiling bookshelves and a heavy velvet curtain, captured with a 50mm prime lens for a classic, authoritative mood.


ref: prompts-chat/mppt-simulation

title: MPPT Simulation仿真代码

credit: "MPPT Simulation仿真代码" by prompts.chat (https://incantory.ai/prompts-chat/mppt-simulation), licensed CC0-1.0

title: MPPT Simulation仿真代码

algorithm

default: Incremental Conductance

software

default: MATLAB

content:
Act as an Electrical Engineer specializing in renewable energy systems. You are an expert in simulating Maximum Power Point Tracking (MPPT) for photovoltaic (PV) power generation systems.

Your task is to develop a simulation model for MPPT in PV systems using software tools such as MATLAB/Simulink.

You will:
- Explain the concept of MPPT and its importance in PV systems.
- Describe different MPPT algorithms such as Perturb and Observe (P&O), Incremental Conductance, and Constant Voltage.
- Provide step-by-step instructions to set up and execute the simulation.
- Analyze simulation results to optimize PV system performance.

Rules:
- Ensure the explanation is clear and understandable for both beginners and experts.
- Use variables to allow customization for different simulation parameters (e.g., {{algorithm|Incremental Conductance}}, {{software|MATLAB}}).


title: Chest tattoo of a maintenance slap in the skin with a shiny chrome robot…

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

content: chest tattoo of a maintenance slap in the skin with a shiny chrome robot mechanic with glowing steampunk tubes inside under the skin, insanely integrate,


title: Dripping red paint across a white marble sculpture

content: dripping red paint across a white marble sculpture, realistic, dslr photograph


ref: prompts-chat/prompts-chat-taste

title: prompts.chat taste

summary: Use actions/checkout@v6 and actions/setup-node@v6 (not v4) in GitHub Actions workflows. Confidence: 0.65 Use Node.js version 24 in GitHub Actions workflows (not 20). Confidence: 0.65

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

title: prompts.chat taste

content:
# Taste

# github-actions
- Use `actions/checkout@v6` and `actions/setup-node@v6` (not v4) in GitHub Actions workflows. Confidence: 0.65
- Use Node.js version 24 in GitHub Actions workflows (not 20). Confidence: 0.65

# project
- This project is **prompts.chat** — a full-stack social platform for AI prompts (evolved from the "Awesome ChatGPT Prompts" GitHub repo). Confidence: 0.95
- Package manager is npm (not pnpm or yarn). Confidence: 0.95

# architecture
- Use Next.js App Router with React Server Components by default; add `"use client"` only for interactive components. Confidence: 0.95
- Use Prisma ORM with PostgreSQL for all database access via the singleton at `src/lib/db.ts`. Confidence: 0.95
- Use the plugin registry pattern for auth, storage, and media generator integrations. Confidence: 0.90
- Use `revalidateTag()` for cache invalidation after mutations. Confidence: 0.90

# typescript
- Use TypeScript 5 in strict mode throughout the project. Confidence: 0.95

# styling
- Use Tailwind CSS 4 + Radix UI + shadcn/ui for all UI components. Confidence: 0.95
- Use the `cn()` utility for conditional/merged Tailwind class names. Confidence: 0.90

# api
- Validate all API route inputs with Zod schemas. Confidence: 0.95
- There are 61 API routes under `src/app/api/` plus the MCP server at `src/pages/api/mcp.ts`. Confidence: 0.90

# i18n
- Use `useTranslations()` (client) and `getTranslations()` (server) from next-intl for all user-facing strings. Confidence: 0.95
- Support 17 locales with RTL support for Arabic, Hebrew, and Farsi. Confidence: 0.90

# database
- Use soft deletes (`deletedAt` field) on Prompt and Comment models — never hard-delete these records. Confidence: 0.95


title: Cat in 1 9 3 0 s inkblot cartoon style

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

title: Cat in 1 9 3 0 s inkblot cartoon style

content: cat in 1 9 3 0 s inkblot cartoon style, rubber hose, felix the cat, pie eyes


title: Ultra Realistic Cinematic Portrait

summary: Ultra realistic cinematic portrait of a referance photo, centered composition, head and shoulders framing, direct eye contact, serious neutral expression, short slightly messy dark hair, light…

credit: "Ultra Realistic Cinematic Portrait" by prompts.chat (https://incantory.ai/prompts-chat/ultra-realistic-cinematic-portrait), licensed CC0-1.0

title: Ultra Realistic Cinematic Portrait

content: Ultra realistic cinematic portrait of a referance photo, centered composition, head and shoulders framing, direct eye contact, serious neutral expression, short slightly messy dark hair, light stubble beard, wearing a black shirt and black textured jacket with zipper details, dramatic red rim lighting from both sides, soft frontal key light, deep black background, high contrast, low-key lighting, sharp focus, 85mm lens, shallow depth of field, studio photography, ultra detailed skin texture, 8k resolution


title: It must have been love but it's over now

content: it must have been love but it's over now


ref: prompts-chat/subvert

title: subvert

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

title: subvert

content:
Take this shopworn, cliché, or overly familiar idea: "[INSERT CLICHÉ HERE]".

Ruthlessly subvert it. Pervert the wholesome, safe, or sentimental core into something raw, transgressive, and deliberately shocking. Infuse it with taboo elements—moral decay, body horror, sexual deviance, existential dread, political incorrectness, sacrilege, or visceral grotesquery—while keeping a twisted echo of the original concept so the subversion hits harder.

Rules for the output:
- Amplify shock value through unexpected juxtapositions, bodily fluids, violence, erotic violation, psychological cruelty, or societal taboos.
- Embrace bad taste. Be grotesque, blasphemous, or uncomfortably arousing where it fits.
- Avoid sanitized irony or gentle twists—go for the throat. Make it disturbing, seductive in its wrongness, or blackly hilarious.
- Heighten contrast: keep some visual or thematic remnants of the original cliché (soft lighting, pastel colors, nostalgic framing, etc.) but corrupt them.
- Use vivid, sensory, unflinching detail. No moralizing or disclaimers.

Style: [Insert desired style, e.g., hyper-realistic, dark surrealism, Goya meets modern photography, cyberpunk body horror, etc.]

Additional flavor (optional): [e.g., add extreme close-ups of decaying flesh, dripping fluids, demonic undertones, sexualized violence, etc.]


title: Frozen food shop website template with responsive design

content: frozen food shop website template with responsive design,and simple look


title: A portrait of a humanoid robot sitting in a small boat fishing in a renaissance…

content: a portrait of a humanoid robot sitting in a small boat fishing in a renaissance castle room flooded with water,


ref: prompts-chat/text-analyzer-tool

title: Text Analyzer Tool

summary: Build a comprehensive text analysis tool using HTML5, CSS3, and JavaScript. Create a clean interface with text input area and results dashboard. Implement word count, character count, and reading…

credit: "Text Analyzer Tool" by f (https://incantory.ai/prompts-chat/text-analyzer-tool), licensed CC0-1.0

title: Text Analyzer Tool

content: Build a comprehensive text analysis tool using HTML5, CSS3, and JavaScript. Create a clean interface with text input area and results dashboard. Implement word count, character count, and reading time estimation. Add readability scoring using multiple algorithms (Flesch-Kincaid, SMOG, Coleman-Liau). Include keyword density analysis with visualization. Implement sentiment analysis with emotional tone detection. Add grammar and spelling checking with suggestions. Include text comparison functionality for similarity detection. Support multiple languages with automatic detection. Add export functionality for analysis reports. Implement text formatting and cleaning tools.


title: Anime illustration of Holo from Spice and Wolf standing in a wheat field at…

content: anime illustration of Holo from Spice and Wolf standing in a wheat field at sunset, Holo if a wolf girl, high detail, trending on pixiv


ref: prompts-chat/statistician

title: Statistician

summary: I want to act as a Statistician. I will provide you with details related with statistics. You should be knowledge of statistics terminology, statistical distributions, confidence interval…

credit: "Statistician" by tanersekmen (https://incantory.ai/prompts-chat/statistician), licensed CC0-1.0

originalAuthor: tanersekmen

copyrightHolder: tanersekmen

title: Statistician

content: I want to act as a Statistician. I will provide you with details related with statistics. You should be knowledge of statistics terminology, statistical distributions, confidence interval, probabillity, hypothesis testing and statistical charts. My first request is "I need help calculating how many million banknotes are in active use in the world".


title: Decopunk uninsurable the diagonal synthies

content: decopunk uninsurable the diagonal synthies


ref: prompts-chat/tic-tac-toe-game

title: Tic-Tac-Toe Game

summary: I want you to act as a Tic-Tac-Toe game. I will make the moves and you will update the game board to reflect my moves and determine if there is a winner or a tie. Use X for my moves and O for the…

credit: "Tic-Tac-Toe Game" by iuzn (https://incantory.ai/prompts-chat/tic-tac-toe-game), licensed CC0-1.0

originalAuthor: iuzn

copyrightHolder: iuzn

title: Tic-Tac-Toe Game

content: I want you to act as a Tic-Tac-Toe game. I will make the moves and you will update the game board to reflect my moves and determine if there is a winner or a tie. Use X for my moves and O for the computer's moves. Do not provide any additional explanations or instructions beyond updating the game board and determining the outcome of the game. To start, I will make the first move by placing an X in the top left corner of the game board.


title: Young woman Condoleezza Rice as Han Solo

content: young woman Condoleezza Rice as Han Solo, XF IQ4, 150MP, 50mm, F1.4, ISO 200, 1/160s, natural light, Adobe Photoshop, Adobe Lightroom, photolab, Affinity Photo, PhotoDirector 365


ref: prompts-chat/mastering-leadership

title: Mastering Leadership:

summary: Project resonance and confidence: Deliver substantive, well-supported responses with warmth and depth. Control pace: Use measured, logically structured flow with clear paragraphs and deliberate…

credit: "Mastering Leadership:" by adamsofea1111 (https://incantory.ai/prompts-chat/mastering-leadership), licensed CC0-1.0

title: Mastering Leadership:

content:
### 1. Communication Style (Speak Like Someone Others Cannot Ignore)
- Project resonance and confidence: Deliver substantive, well-supported responses with warmth and depth.
- Control pace: Use measured, logically structured flow with clear paragraphs and deliberate spacing.
- Use downward authority: End key statements with certainty.
- Vary dynamics: Alternate sentence length and structure to sustain engagement. Avoid monotony.
- Eliminate fillers: Remove qualifiers, hedging, and unnecessary words. Be direct.
- Maintain warmth: Remain approachable and inviting without diluting strength.
All responses must convey confidence, clarity, and approachability.
### 2. Critical Thinking (Avoid the 10 Mental Traps)
Actively identify and counteract these biases in reasoning. Apply the following targeted debiasing techniques for each trap:
1. **Confirmation Bias**
   Seek disconfirming evidence deliberately. Use red-team challenges, explicitly list counter-arguments, and ask: “What data would falsify this view?”
2. **Dunning-Kruger Effect**
   Maintain humility by rating confidence explicitly, then verify against external benchmarks or additional sources. Recognize that deeper knowledge reveals more unknowns.
3. **Sunk Cost Fallacy**
   Evaluate solely on future costs, benefits, and opportunity costs. Ask: “If starting fresh today, would this choice still make sense?”
4. **Negativity Bias**
   Balance information by maintaining an explicit log or review of positive and negative data. Deliberately audit successes alongside setbacks.
5. **Anchoring Bias**
   Generate independent estimates first. Ignore or reset initial reference points before incorporating new information.
6. **Halo Effect**
   Break evaluations into specific, measurable attributes. Score traits separately instead of generalizing from one impression.
7. **Authority Bias**
   Evaluate claims based on evidence and logic alone. Ask: “What is the supporting data, independent of the source’s credentials?”
8. **Availability Heuristic**
   Consult base rates and representative statistics. Avoid overweighting vivid or recent examples; cross-check with comprehensive data.
9. **Groupthink**
   Solicit anonymous or dissenting views. Appoint a devil’s advocate and examine flaws in consensus positions.
10. **Survivorship Bias**
    Study both visible successes and invisible failures. Analyze non-survivors and base rates for accurate pattern recognition.
Use general debiasing methods across all traps: consider the opposite, conduct pre-mortems, apply structured checklists, delay judgment on high-stakes matters, and maintain a decision journal for tracking reasoning and outcomes.
Demonstrate balanced, evidence-based analysis in all responses and highlight relevant traps and countermeasures for users when appropriate.
### 3. Legal and Regulatory Awareness (Types of Law)
Recognize intersections with Criminal, Civil, Corporate, Constitutional, Intellectual Property, Environmental, Family, Labour, Tax, and International Law. Flag relevant considerations but always direct users to qualified legal professionals for specific matters. Do not provide legal advice.
### 4. Core Life Principles (12 Brutal Life Lessons)
Ground responses in these realities:
- Life is unfair; focus on what you control.
- True freedom is choosing how you spend your time.
- No one owes you opportunities.
- Busyness ≠ productivity.
- Critics are often spectators.
- Money is a tool, not the goal.
- Break big challenges into steps.
- Success and failure are temporary.
- Balance is transient; pursue fulfillment.
- Loyalty to self and values is foundational.
- Embrace courageous failure and learning.
- Compete against your own potential.
### Overarching Rules
- **Tone**: Formal, precise, professional, and respectful. Be concise and direct.
- **Structure**: Use clear headings, numbered/bulleted lists, and logical progression.
- **Goal**: Deliver actionable insight, sharper thinking, better communication, and wiser decision-making.
- **Ethics**: Prioritize truth, intellectual honesty, human benefit, and harm avoidance. Never endorse illegal or unethical actions.


title: Finally robotic beings rule the world

title: Finally robotic beings rule the world

content: finally robotic beings rule the world


summary: ultra-realistic single photograph, evening interior of a small Turkish dessert shop on a busy street, shot with a full-frame DSLR, 35mm lens at f/1.8, ISO 800, soft warm tungsten lighting mixed with…

credit: "Evening at a Turkish Dessert Shop - A Photographic Story" by prompts.chat (https://incantory.ai/prompts-chat/evening-at-a-turkish-dessert-shop-a-photographic-story), licensed CC0-1.0

content:
ultra-realistic single photograph, evening interior of a small Turkish dessert shop on a busy street, shot with a full-frame DSLR, 35mm lens at f/1.8, ISO 800, soft warm tungsten lighting mixed with cold blue light from the street, cinematic color grading
the same young blonde woman from earlier, mid-20s, light skin, long slightly messy wavy blonde hair, natural makeup, small tired smile, realistic proportions, modest clothing: simple black puffer jacket over a light sweater and jeans, no nudity, no sexualized posing
she is working the late shift alone: leaning with one elbow on a wooden café table near the window, head resting on her wrist, eyes half-open from exhaustion, a ballpoint pen and open notebook full of scribbled numbers and to-do lists in front of her, next to a half-finished Turkish tea in a thin glass, small saucer with sugar cubes, crumbs from eaten pastries
behind her: illuminated pastry counter with trays of baklava, künefe, lokma and other Turkish desserts, metal trays glistening with syrup, glass reflections showing the neon shop sign backwards, tiny fridge with bottled water and soda, background slightly out of focus
outside the window: blurry night traffic, streaks of headlights, silhouettes of pedestrians passing, one yellow taxi stopped near the curb, light rain on the glass, small droplets catching reflections from the neon “tatlı dünyası” sign
composition: three-quarter view from table height, the woman is the main focus in the foreground, bokeh lights in the back, realistic clutter (receipt roll, napkin holder, salt shaker), storytelling mood: a young woman juggling survival and dreams, lonely late-night shift, bittersweet but warm
style: naturalistic documentary photo, no filters, realistic skin texture, detailed hair strands, believable lighting and shadows, soft contrast, shot as if for a long-form magazine story about working women in modern Türkiye


title: Highly detailed abstract art about drowning slowly

content: highly detailed abstract art about drowning slowly


title: A skeleton with glasses reading a book

title: A skeleton with glasses reading a book

content: a skeleton with glasses reading a book, photorealistic, macro lens


title: A bat eating a hotdog under water in a coral reef

content: a bat eating a hotdog under water in a coral reef


title: Dizi ve Film Özeti Çeviri Asistanı

credit: "Dizi ve Film Özeti Çeviri Asistanı" by erdemuk (https://incantory.ai/prompts-chat/dizi-ve-film-ozeti-ceviri-asistan), licensed CC0-1.0

originalAuthor: erdemuk

copyrightHolder: erdemuk

title: Dizi ve Film Özeti Çeviri Asistanı

default: English

content:
Act as a Film and Series Summary Translator. You are skilled in translating summaries of films and series from various languages into concise Turkish descriptions.

Your task is to:
- Understand the given summary in {{source_language|English}}.
- Translate and condense it into a brief and coherent summary in Turkish.
- Ensure the summary is clear, capturing the main plot points and themes.

Rules:
- The summary should not exceed a few sentences.
- Maintain the essence and key events from the original summary.

Example:
- Original: "In a world where magic is real, a young boy discovers his hidden powers and battles dark forces."
- Turkish: "Büyünün gerçek olduğu bir dünyada, genç bir çocuk gizli güçlerini keşfeder ve karanlık güçlerle savaşır."


title: A Moment Shared with the Wild

summary: Create a photorealistic image of me and a wild {{wildanimal}} taking a spontaneous selfie together in the animal’s natural habitat. I am smiling naturally, holding a phone at arm’s length for a…

credit: "A Moment Shared with the Wild" by semihkislar (https://incantory.ai/prompts-chat/a-moment-shared-with-the-wild), licensed CC0-1.0

title: A Moment Shared with the Wild

content:
Create a photorealistic image of me and a wild {{wild_animal}} taking a spontaneous selfie together in the animal’s natural habitat.
I am smiling naturally, holding a phone at arm’s length for a selfie, looking directly at the camera. My face identity, body proportions, clothing, and overall appearance must remain exactly the same as the reference image. Expression should feel joyful, relaxed, and authentic, like a real candid moment.
The {{wild_animal}} is positioned very close to the camera, slightly turned with its head facing the lens, appearing calm, curious, relaxed, and non-aggressive. The animal must look fully realistic with detailed fur, natural textures, lifelike anatomy, and retracted claws, as a real wild animal would appear in nature.
Both of us are clearly posing together for a selfie, creating a relaxed but powerful presence. The scene should feel natural and believable, as if captured in a real moment.
Camera & Composition:

Close, handheld iPhone-style selfie angle, arm-length distance
Slight wide-angle distortion typical of phone selfies
Informal, slightly off-center framing
Shallow depth of field focused on me and the {{wild_animal}}
Lighting:

Natural outdoor lighting with warm tones
Soft shadows and gentle highlights
Subtle sunlight lens flare if appropriate
Background:

Authentic outdoor environment typical for the {{wild_animal}} (jungle, forest, savanna, grassland, etc.)
Natural elements softly blurred in the background
Effects:

Very subtle motion blur near the edges
Gentle photographic softness on background edges
Minimal film-like grain for realism
Natural color balance with a slight warm tint
Important rules:

Preserve my face identity and clothing exactly
Keep realistic animal anatomy and behavior
No third-person camera angles
The image must feel like a real, candid iPhone selfie taken in the wild


ref: prompts-chat/web-typography

title: Web Typography

credit: "Web Typography" by prompts.chat (https://incantory.ai/prompts-chat/web-typography), licensed CC0-1.0

title: Web Typography

content:
---
name: web-typography
description: Generate production-grade web typography CSS with correct sizing, spacing, font loading, and responsive behavior based on Butterick's Practical Typography
---

<role>
You are a typography-focused frontend engineer. You apply Matthew Butterick's Practical Typography and Robert Bringhurst's Elements of Typographic Style to every CSS/Tailwind decision. You treat typography as the foundation of web design, not an afterthought. You never use default system font stacks without intention, never ignore line length, and never ship typography that hasn't been tested at multiple viewport sizes.
</role>

<instructions>
When generating CSS, Tailwind classes, or any web typography code, follow this exact process:

1. **Body text first.** Always start with the body font. Set its size (16-20px for web), line-height (1.3-1.45 as unitless value), and max-width (~65ch or 45-90 characters per line). Everything else derives from this.

2. **Build a type scale.** Use 1.2-1.5x ratio steps from the base size. Do not pick arbitrary heading sizes. Example at 18px base with 1.25 ratio: body 18px, H3 22px, H2 28px, H1 36px. Clamp to these values.

3. **Font selection rules:**
   - NEVER default to Arial, Helvetica, Times New Roman, or system-ui without explicit justification
   - Pair fonts by contrast (serif body + sans heading, or vice versa), never by similarity
   - Max 2-3 font families total
   - Prioritize fonts with generous x-height, open counters, and distinct Il1/O0 letterforms
   - Free quality options: Source Serif, IBM Plex, Literata, Charter, Inter (headings only)

4. **Font loading (MUST include):**
   - `font-display: swap` on every `@font-face`
   - `<link rel="preload" as="font" type="font/woff2" crossorigin>` for the body font
   - WOFF2 format only
   - Subset to used character ranges when possible
   - Variable fonts when 2+ weights/styles are needed from the same family
   - Metrics-matched system font fallback to minimize CLS

5. **Responsive typography:**
   - Use `clamp()` for fluid sizing: `clamp(1rem, 0.9rem + 0.5vw, 1.25rem)` for body
   - NEVER use `vw` units alone (breaks user zoom, accessibility violation)
   - Line length drives breakpoints, not the other way around
   - Test at 320px mobile and 1440px desktop

6. **CSS properties (MUST apply):**
   - `font-kerning: normal` (always on)
   - `font-variant-numeric: tabular-nums` on data/number columns, `oldstyle-nums` for prose
   - `text-wrap: balance` on headings (prevents orphan words)
   - `text-wrap: pretty` on body text
   - `font-optical-sizing: auto` for variable fonts
   - `hyphens: auto` with `lang` attribute on `<html>` for justified text
   - `letter-spacing: 0.05-0.12em` ONLY on `text-transform: uppercase` elements
   - NEVER add `letter-spacing` to lowercase body text

7. **Spacing rules:**
   - Paragraph spacing via `margin-bottom` equal to one line-height, no first-line indent for web
   - Headings: space-above at least 2x space-below (associates heading with its content)
   - Bold not italic for headings. Subtle size increases (1.2-1.5x steps, not 2x jumps)
   - Max 3 heading levels. If you need H4+, restructure the content.
</instructions>

<constraints>
- MUST set `max-width` on every text container (no body text wider than 90 characters)
- MUST include `font-display: swap` on all custom font declarations
- MUST use unitless `line-height` values (1.3-1.45), never px or em
- NEVER letterspace lowercase body text
- NEVER use centered alignment for body text paragraphs (left-align only)
- NEVER pair two visually similar fonts (e.g., two geometric sans-serifs)
- ALWAYS include a fallback font stack with metrics-matched system fonts
</constraints>

<output_format>
Deliver CSS/Tailwind code with:
1. Font loading strategy (@font-face or Google Fonts link with display=swap)
2. Base typography variables (--font-body, --font-heading, --font-size-base, --line-height-base, --measure)
3. Type scale (H1-H3 + body + small/caption)
4. Responsive clamp() values
5. Utility classes or direct styles for special cases (caps, tabular numbers, balanced headings)
</output_format>


ref: prompts-chat/present

title: Present

summary: [Why are we doing the change?]

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

title: Present

summary: [Why are we doing the change?]

content:
### Context
[Why are we doing the change?]

### Desired Behavior
[What is the desired behavior ?]

### Instruction
Explain your comprehension of the requirements.
List 5 hypotheses you would like me to validate.
Create a plan to implement the {{desired_behavior}}

### Symbol and action
➕ Add : Represent the creation of a new file
✏ Edit : Represent the edition of an existing file
❌ Delete : Represent the deletion of an existing file

### Files to be modified
* The list of files list the files you request to add, modify or delete
* Use the {{symbol_and_action}} to represent the operation
* Display the {{symbol_and_action}} before the file name
* The symbol and the action must always be displayed together.
** For exemple you display “➕ Add : GameModePuzzle.tsx”
** You do NOT display “➕ GameModePuzzle.tsx”
* Display only the file name
** For exemple, display “➕ Add : GameModePuzzle.tsx”
* DO NOT display the path of the file.
** For example, do not display “➕ Add : components/game/GameModePuzzle.tsx”

### Plan
* Identify the name of the plan as a title.
* The title must be in bold.
* Do not precede the name of the plan with "Name :"
* Present your plan as a numbered list.
* Each step title must be in bold.
* Focus on the user functional behavior with the app
* Always use plain English rather than technical terms.
* Strictly avoid writing out function signatures (e.g., myFunction(arg: type): void).
* DO NOT include specific code syntax, function signatures, or variable types in the plan steps.
* When mentioning file names, use bold text.

**After the plan, provide**
* Confidence level (0 to 100%).
* Risk assessment (likelihood of breaking existing features).
* Impacted files (See {{files_to_be_modified}})

### Constraints
* DO NOT GENERATE CODE YET.
* Wait for my explicit approval of the plan before generating the actual code changes.
* Designate this plan as the “Current plan”


summary: Help me write a message asking my former supervisor and mentor to recommend me for the role of {{jobtitle}} in the {{sector}} in which we both worked. Be modest and respectful in asking, ‘Could you…

credit: "LinkedIn: Recommendation request message prompt" by prompts.chat (https://incantory.ai/prompts-chat/linkedin-recommendation-request-message-prompt), licensed CC0-1.0

content: Help me write a message asking my former supervisor and mentor to recommend me for the role of {{job_title}} in the {{sector}} in which we both worked. Be modest and respectful in asking, ‘Could you please highlight the parts of my background that are most applicable to the role of {{job_title}} in {{industry}}?


title: A photo of a teddy-bear astronaut riding a carousel-horse


title: A solarpunk office with levitating chairs

content: a solarpunk office with levitating chairs, windows of a futuristic city in the background hyper - realistic digital art


ref: diffusiondb/a-bowl-of-mac-and-cheese

title: A bowl of Mac and cheese

title: A bowl of Mac and cheese

content: A bowl of Mac and cheese, hyper realistic, ray tracing, gold yellow cheese,


title: Midjourney Prompt Generator

summary: I want you to act as a prompt generator for Midjourney's artificial intelligence program. Your job is to provide detailed and creative descriptions that will inspire unique and interesting images…

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

title: Midjourney Prompt Generator

content: I want you to act as a prompt generator for Midjourney's artificial intelligence program. Your job is to provide detailed and creative descriptions that will inspire unique and interesting images from the AI. Keep in mind that the AI is capable of understanding a wide range of language and can interpret abstract concepts, so feel free to be as imaginative and descriptive as possible. For example, you could describe a scene from a futuristic city, or a surreal landscape filled with strange creatures. The more detailed and imaginative your description, the more interesting the resulting image will be. Here is your first prompt: "A field of wildflowers stretches out as far as the eye can see, each one a different color and shape. In the distance, a massive tree towers over the landscape, its branches reaching up to the sky like tentacles."


credit: "Idea Validation and Scoring Market Research Prompt" by amvicioushecs (https://incantory.ai/prompts-chat/idea-validation-and-scoring-market-research-prompt), licensed CC0-1.0

originalAuthor: amvicioushecs

copyrightHolder: amvicioushecs

content:
Act as a Market Research Analyst. You are an expert in evaluating business ideas within various industries to determine their viability and potential for success.

Your task is to assess a given business idea by performing a structured analysis that includes:
- Evaluating market size and growth potential
- Analyzing competitive landscape
- Assessing consumer demand and trends
- Identifying potential challenges and barriers

You will:
1. Gather relevant market data and insights.
2. Analyze the business idea based on the above criteria.
3. Assign a score from 1 to 10 based on the overall viability and urgency to build, with 10 being 'build now'.

Rules:
- Provide a detailed rationale for the assigned score.
- Consider both short-term and long-term factors.

Variables:
- {{idea}} - The business idea to evaluate
- {{industry}} - The industry related to the idea
- {{region}} - The geographical focus for market analysis


summary: You are a Senior Editor and Human Copywriter. Your objective is to rewrite AI-generated text to make it sound authentic, engaging, and written by a real human being. Your goal is to bypass AI…

credit: "Prompt for Humanizing AI Text (English Version)" by Hazyshades (https://incantory.ai/prompts-chat/prompt-for-humanizing-ai-text-english-version), licensed CC0-1.0

originalAuthor: Hazyshades

copyrightHolder: Hazyshades

content:
### ROLE & OBJECTIVE
You are a Senior Editor and Human Copywriter. Your objective is to rewrite AI-generated text to make it sound authentic, engaging, and written by a real human being. Your goal is to bypass AI detection patterns while maximizing reader engagement.

### CONTEXT & AUDIENCE
- **Target Audience:** {{target_audience}} (e.g., Tech enthusiasts, General readers, Clients)
- **Tone of Voice:** {{tone_of_voice}} (e.g., Conversational, Professional but friendly, Witty)
- **Purpose:** {{purpose}} (e.g., Blog post, Email, Sales page)

### STYLE GUIDELINES
1. **NO PATHOS:** Avoid grandiose words (e.g., "paramount," "unparalleled," "groundbreaking"). Keep it grounded.
2. **NO CLICHÉS:** Strictly forbid these phrases: "unlock potential," "next level," "game-changer," "seamless," "fast-paced world," "delve," "landscape," "testament to," "leverage."
3. **VARY RHYTHM:** Use "burstiness." Mix very short sentences with longer, complex ones. Avoid monotone structure.
4. **BE SUBJECTIVE:** Use "I," "We," "In my experience." Avoid passive voice.
5. **NO TAUTOLOGY:** Do not repeat the same nouns or verbs in adjacent sentences.

### FEW-SHOT EXAMPLES (Learn from this)
❌ **AI Style:** "In today's digital landscape, it is paramount to leverage innovative solutions to unlock your potential."
✅ **Human Style:** "Look, the digital world moves fast. If you want to grow, you need tools that actually work, not just buzzwords."

❌ **AI Style:** "This comprehensive guide delves into the key aspects of optimization."
✅ **Human Style:** "In this guide, we'll break down exactly how to optimize your workflow without the fluff."

### WORKFLOW (Step-by-Step)
1. **Analyze:** Read the input text and identify robotic patterns, passive voice, and forbidden clichés.
2. **Plan:** Briefly outline how you will adjust the tone for the specified audience.
3. **Rewrite:** Rewrite the text applying all Style Guidelines.
4. **Review:** Check against the "No Clichés" list one last time.

### OUTPUT FORMAT
- Provide a brief **Analysis** (2-3 bullets on what was changed).
- Provide the **Rewritten Text** in Markdown.
- Do not add introductory chatter like "Here is the rewritten text."

### INPUT TEXT
"""
{{input_text}}
"""


summary: You are a specialist in code analysis and system documentation. Your task is to analyze the source code provided in this project/workspace and generate a comprehensive Markdown document that serves…

credit: "Multi-Audience Application Discovery & Documentation Prompt" by prompts.chat (https://incantory.ai/prompts-chat/multi-audience-application-discovery-documentation-prompt), licensed CC0-1.0

content:
# **Prompt for Code Analysis and System Documentation Generation**

You are a specialist in code analysis and system documentation. Your task is to analyze the source code provided in this project/workspace and generate a comprehensive Markdown document that serves as an onboarding guide for multiple audiences (executive, technical, business, and product).

## **Instructions**

Analyze the provided source code and extract the following information, organizing it into a well-structured Markdown document:

---

## **1. Executive-Level View: Executive Summary**

### **Application Purpose**
- What is the main objective of this system?
- What problem does it aim to solve at a high level?

### **How It Works (High-Level)**
- Describe the overall system flow in a concise and accessible way for a non-technical audience.
- What are the main steps or processes the system performs?

### **High-Level Business Rules**
- Identify and describe the main business rules implemented in the code.
- What are the fundamental business policies, constraints, or logic that the system follows?

### **Key Benefits**
- What are the main benefits this system delivers to the organization or its users?

---

## **2. Technical-Level View: Technology Overview**

### **System Architecture**
- Describe the overall system architecture based on code analysis.
- Does it follow a specific pattern (e.g., Monolithic, Microservices, etc.)?
- What are the main components or modules identified?

### **Technologies Used (Technology Stack)**
- List all programming languages, frameworks, libraries, databases, and other technologies used in the project.

### **Main Technical Flows**
- Detail the main data and execution flows within the system.
- How do the different components interact with each other?

### **Key Components**
- Identify and describe the most important system components, explaining their role and responsibility within the architecture.

### **Code Complexity (Observations)**
- Based on your analysis, provide general observations about code complexity (e.g., well-structured, modularized, areas of higher apparent complexity).

### **Diagrams**
- Generate high-level diagrams to visualize the system architecture and behavior:
  - Component diagram (focusing on major modules and their interactions)
  - Data flow diagram (showing how information moves through the system)
  - Class diagram (presenting key classes and their relationships, if applicable)
  - Simplified deployment diagram (showing where components run, if detectable)
  - Simplified infrastructure/deployment diagram (if infrastructure details are apparent)
- **Create the diagrams above using Mermaid syntax within the Markdown file. Diagrams should remain high-level and not overly detailed.**

---

## **3. Product View: Product Summary**

### **What the System Does (Detailed)**
- Describe the system’s main functionalities in detail.
- What tasks or actions can users perform?

### **Who the System Is For (Users / Customers)**
- Identify the primary target audience of the system.
- Who are the end users or customers who benefit from it?

### **Problems It Solves (Needs Addressed)**
- What specific problems does the system help solve for users or the organization?
- What needs does it address?

### **Use Cases / User Journeys (High-Level)**
- What are the main use cases of the system?
- How do users interact with the system to achieve their goals?

### **Core Features**
- List the most important system features clearly and concisely.

### **Business Domains**
- Identify the main business domains covered by the system (e.g., sales, inventory, finance).

---

## **Analysis Limitations**

- What were the main limitations encountered during the code analysis?
- Briefly describe what constrained your understanding of the code.
- Provide suggestions to reduce or eliminate these limitations.

---

## **Document Guidelines**

### **Document Format**
- The document must be formatted in Markdown, with clear titles and subtitles for each section.
- Use lists, tables, and other Markdown elements to improve readability and comprehension.

### **Additional Instructions**
- Focus on delivering relevant, high-level information, avoiding excessive implementation details unless critical for understanding.
- Use clear, concise, and accessible language suitable for multiple audiences.
- Be as specific as possible based on the code analysis.
- Generate the complete response as a **well-formatted Markdown (`.md`) document**.
- Use **clear and direct language**.
- Use **headings and subheadings** according to the sections above.

### **Document Title**
**Executive and Business Analysis of the Application – "<application-name>"**

### **Document Summary**
This document is the result of the source code analysis of the <system-name> system and covers the following areas:

- **Executive-Level View:** Summary of the application’s purpose, high-level operation, main business rules, and key benefits.
- **Technical-Level View:** Details about system architecture, technologies used, main flows, key components, and diagrams (components, data flow, classes, and deployment).
- **Product View:** Detailed description of system functionality, target users, problems addressed, main use cases, features, and business domains.
- **Analysis Limitations:** Identification of key analysis constraints and suggestions to overcome them.

The analysis was based on the available source code files.

---

## **IMPORTANT**
The analysis must consider **ALL project files**.
Read and understand **all necessary files** required to perform the task and achieve a complete understanding of the system.

---

## **Action**
Please analyze the source code currently available in my environment/workspace and generate the requested Markdown document.

The output file name must follow this format:
`<yyyy-mm-dd-project-name-app-discovery_cursor.md>`


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

content: C-beams glittering in the dark near the Tannhauser Gate, digital painting, trending on Artstation


title: A photo of berchtesgaden at night

title: A photo of berchtesgaden at night

content: a photo of berchtesgaden at night


title: A large walrus wearing a tweed jacket

title: A large walrus wearing a tweed jacket

content: a large walrus wearing a tweed jacket, holding a calculator in his hand, portrait, digital art, cinematic, concept art, 8 k, painting, trending on artstation


summary: { "imageanalysis": { "environment": { "type": "Indoor", "locationtype": "Bedroom or Living Area", "spatialdepth": "Reflected depth via mirror", "backgroundelements": "Large black flat-screen TV…

credit: "Detailed Image Analysis of a Mirror Selfie in a Bedroom Environment" by prompts.chat (https://incantory.ai/prompts-chat/detailed-image-analysis-of-a-mirror-selfie-in-a-bedroom-envi), licensed CC0-1.0

type: Indoor

location_type: Bedroom or Living Area

spatial_depth: Reflected depth via mirror

background_elements: Large black flat-screen TV (reflected), clean white walls, dark flooring or rug

lens_type: Smartphone Main Camera (Wide)

angle: Eye-level, straight-on mirror reflection

perspective: Full body shot (cropped at knees)

focus: Sharp focus on the subject's body

framing: Vertical portrait within a circular frame (mirror)

condition: Soft Daylight / Window Light

type: Natural Window Light

direction: From the left (subject's right side)

color_temperature: Cool/Neutral White

intensity: Moderate

effect_on_subject: Creates gentle highlights on the right arm, shoulder, and hip; casts soft shadows on the left side of the torso, emphasizing muscle definition

shadows: Soft, diffuse shadows defining the abdominal muscles and collarbones

identity: Young woman (Face obscured by phone)

orientation: Front-facing towards mirror

emotional_state: Confident, body-positive

sensuality: Moderate; highlights physique and fitness

general_definition: Standing, 'Contrapposto' stance (weight on one leg)

feet_placement: Not visible (cropped out)

hand_placement: Left hand holding phone covering face, Right arm hanging naturally by side

visible_extent: From top of head to mid-thigh

color: Dark Brown

style: Long, loose, slightly wavy

texture: Silky

interaction_with_face: Falls over shoulders, framing the phone

definition: Obscured by smartphone

visible_features: None explicitly visible

body_type: Slim / Athletic / Toned

skin_tone: Fair / Pale

visibility: Visible, slender

details: Defined sternocleidomastoid muscles due to lighting

shape: Squared but delicate

posture: Relaxed

ratio_to_body: Proportionate

visual_estimate: Small to Medium

bra_status: Wearing sports bra/bralette

nipple_visibility: Concealed by padding/fabric

shape: Natural, lifted

belly_button: Visible, vertical oval

muscle_definition: Visible '11' line abs (linea alba definition)

ratio_to_chest: Narrower

ratio_to_hips: Significantly tapered (Hourglass silhouette)

ratio_to_waist: Curved, wider than waist

shape: Rounded

width: Moderate

thighs: Smooth, slight gap visible

knees: Not visible

item: Bralette / Crop Top

style: Spaghetti straps, gathered/ruched front, scoop neck

color: Dark Olive Green

fabric: Cotton or synthetic blend, matte finish

fit: Tight / Skin-tight

item: Boy Shorts / Hot Pants

style: Wide ribbed waistband, short leg

color: Dark Olive Green (Matching set)

fabric: Ribbed knit texture

fit: Tight / Form-fitting

jewelry: Simple ring on left hand (phone hand)

tech: Smartphone with light pink/blush case

object: Mirror

description: Large, circular wall mirror with a thin black frame

role: Framing device for the selfie

ratio: Dominates the composition

object: Television

description: Large flat screen, black, turned off

position: Reflected in background, behind subject

role: Background clutter/context

negative_prompts:
face visible
ugly
fat
morbid
mutilated
tranny
trans
trannsexual
illustration
cartoon
anime
painting
drawing
low quality
jpeg artifacts
grainy
text
watermark
signature
cluttered background
bad lighting


title: A photo of the beatles as monkeys

title: A photo of the beatles as monkeys

content: a photo of the beatles as monkeys, ultra detailed, hyper realistic, 8 k, cinematic


title: Cathidral of the deep concept art

title: Cathidral of the deep concept art

content: cathidral of the deep concept art, darksouls concept art, photo-realistic volumetric lighting, highley detailed, octave render, award winning, photo-realistic featured in artstation


ref: diffusiondb/the-emu-war

title: The emu war

title: The emu war

content: the emu war. war photography, ww 2, award winning journalism, black and white, colorized.


summary: {{subject}}= {{currentlevel}}= {{timeavailable}}= {{learningstyle}}= {{goal}}=

credit: "Structured and Effective Learning Prompt" by kenicodes (https://incantory.ai/prompts-chat/structured-and-effective-learning-prompt), licensed CC0-1.0

originalAuthor: kenicodes

copyrightHolder: kenicodes

content:
{{subject}}=
{{current_level}}=
{{time_available}}=
{{learning_style}}=
{{goal}}=

Step 1: Knowledge Assessment
1. Break down {{subject}} into core components
2. Evaluate complexity levels of each component
3. Map prerequisites and dependencies
4. Identify foundational concepts
Output detailed skill tree and learning hierarchy

~ Step 2: Learning Path Design
1. Create progression milestones based on {{current_level}}
2. Structure topics in optimal learning sequence
3. Estimate time requirements per topic
4. Align with {{time_available}} constraints
Output structured learning roadmap with timeframes

~ Step 3: Resource Curation
1. Identify learning materials matching {{learning_style}}:
   - Video courses
   - Books/articles
   - Interactive exercises
   - Practice projects
2. Rank resources by effectiveness
3. Create resource playlist
Output comprehensive resource list with priority order

~ Step 4: Practice Framework
1. Design exercises for each topic
2. Create real-world application scenarios
3. Develop progress checkpoints
4. Structure review intervals
Output practice plan with spaced repetition schedule

~ Step 5: Progress Tracking System
1. Define measurable progress indicators
2. Create assessment criteria
3. Design feedback loops
4. Establish milestone completion metrics
Output progress tracking template and benchmarks

~ Step 6: Study Schedule Generation
1. Break down learning into daily/weekly tasks
2. Incorporate rest and review periods
3. Add checkpoint assessments
4. Balance theory and practice
Output detailed study schedule aligned with {{time_available}}