AI SummaryFF7 Ultima is a real-time editor for Final Fantasy VII that allows players to modify game stats, inventory, and mechanics on-the-fly through a Cursor-integrated interface. It's designed for FF7 fans and modders who want to customize their gameplay experience.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "ff7-ultima — Cursor Rules" prompt rules to my project. Repository: https://github.com/maciej-trebacz/ff7-ultima Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Real-time Final Fantasy VII editor
Project Structure
The project is organized as follows: • src/: This directory contains all the frontend code for the application, written in TypeScript. It utilizes the React framework along with shadcn-ui components and TailwindCSS for styling. You'll find the user interface components, application state management, and frontend logic here. • components/: Contains reusable UI components, further divided into modals/, map/ (for the detailed map viewer), and ui/ (customized shadcn components). • modules/: Holds the main UI views for different editor functionalities (e.g., General.tsx, Field.tsx, Battle.tsx, World.tsx, Party.tsx, Chocobos.tsx) that are accessible via the sidebar. • hooks/: Custom React hooks for managing stateful logic and side effects (e.g., useBattleLog.ts, useMapState.ts). • ff7/: Contains logic for parsing and handling FF7-specific game file formats (e.g., map files, texture files, LGP archives). • assets/: Stores static image assets like icons and maps. • data/: Holds larger static data files, such as scenes.json. • lib/: Contains utility functions and other shared library-like code. • TypeScript type definitions are primarily managed in types.ts and the src/@types/ directory. • src-tauri/: This is the heart of the backend, containing all the Rust code. It manages native functionalities, system interactions, and the core Tauri application setup, including the tauri.conf.json file which configures the application's build, windows, and plugin settings. • public/: Holds static assets that are directly accessible by the webview. This typically includes the main index.html file and could also contain images, fonts, or other resources that don't need to be processed by the frontend build system. • .github/: Contains GitHub-specific configurations, primarily for defining workflows (e.g., Continuous Integration/Continuous Deployment pipelines) using GitHub Actions. • .vscode/: Stores settings specific to the Visual Studio Code editor, such as recommended extensions, debugger configurations, and workspace settings to help maintain a consistent development environment. Key files and components used by the app: • src/Home.tsx - contains the main layout with the sidebar and content view.
Updating .cursorrules
Each time a functionality is added or a directory is created you should update the above section to include it.
Installing shadcn components
To add a new shadcn component to the project run the command: npx shadcn@latest add [component name here]
Invoking Rust backend commands from the frontend
In Tauri 2.0 this is how you invoke backend commands: `js import { invoke } from '@tauri-apps/api/core'; // Invocation from JavaScript invoke('my_custom_command', { number: 42, }) `
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts