mmforge-platform
Create or refine mouse-operated mod menus and their HUD widgets in the local MMForge platform canvas. Use for new UI prototypes, screenshot-based recreations, and targeted edits from MMForge element context.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/eunchae1110--mmforge-platform)HTML
<a href="/listings/eunchae1110--mmforge-platform"><img src="/api/listings/eunchae1110--mmforge-platform/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
npx skills add EunChae1110/mmforge-platform --skill mmforge-platform
Add `-g` to install it for every project on this machine. Add `-y` to skip the prompts.
Run these commands from the MMForge project root. For a standalone setup, copy the installed skill's `assets/canvas/` contents into your workspace first.
npm ci npm run dev
Open the URL Vite prints. Pick a design from the sidebar, or open it directly with `?design=example.tsx`.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 50 lines
- ---
- name: mmforge-platform
- description: Create or refine mouse-operated mod menus and their HUD widgets in the local MMForge platform canvas. Use for new UI prototypes, screenshot-based recreations, and targeted edits from MMForge element context.
- ---
- # MMForge platform
- Build interactive menus and HUD overlays that the user can try in the local MMForge canvas. The runnable canvas source is bundled in [assets/canvas](assets/canvas/). Keep gameplay-facing controls and widget data local to the prototype. Use the user's brief, screenshots, or copied element context as the design input.
- ## Start the canvas
- - Use the existing MMForge project when available. Its project root has a `package.json` named `mmforge-platform` with a `design-activity` script. For a standalone skill installation, copy the contents of `assets/canvas/` into a new writable folder in the user's workspace and work from that folder. Keep generated designs with that copy.
- - Create `designs/` if needed. If dependencies are missing, run `npm ci` from the canvas project root.
- - The skill is authorized to run `npm run dev` on localhost. Reuse the correct MMForge server if it is already running. Otherwise, start it yourself in a terminal session that stays running for preview. Verify the URL Vite prints before working on the design and use its actual port in the handoff. Keep it bound to localhost.
- ## Choose the design
- - For a new menu, identify the main task and choose a navigation structure and settings layout that suit it. For a recreation, match the reference's proportions, density, control shapes, and selected states. Carry two or three specific visual decisions through the whole menu, including open and hover states.
- - For a new menu without a screenshot, choose a layout from the menu reference based on the active page's actual controls. Work out the window proportions, navigation footprint, and control grouping before choosing the palette.
- - For an edit, locate the requested file and control. MMForge's copied context gives the design path, group hierarchy, label, and control type. Use the CSS selector when provided. Follow the imports if the actual control lives in a supporting component. Preserve the surrounding design and behavior outside the request.
- - Read [Mouse menu design](references/mouse-menu-design.md) before creating or recreating a layout or changing control patterns. For a focused edit, use the relevant section.
- - For a widget, inspect its owning menu and read the [HUD widget design reference](references/hud-widget-design.md). Decide what the player needs to read at a glance, then use the menu's visual language at the widget's scale.
- ## Implement in the local canvas
- 1. Put each design entry in a top-level `designs/<name>.tsx` file. Use a default-exported React component and export a numeric `previewWidth` when the intended width differs from the canvas default. Keep supporting components and scoped styles under `designs/shared/` or another subdirectory. The canvas treats every top-level TSX file as a design.
- 2. Put widgets in `designs/widgets/<menu-stem>/<widget>.tsx`. For `designs/cheatname.tsx`, use `designs/widgets/cheatname/`. Match the filename stem exactly. Give each widget entry a default-exported React component and optionally export `widgetTitle` for the Widgets picker. Size the widget root to its content and scope its styles to that root. Game Preview supplies positioning and dragging. Keep TSX helpers in a subfolder so the picker discovers only widget entries.
- 3. Signal activity before changing the design. Run the commands from the project root. Use the menu entry path for menu work and the nested widget entry path for widget work. Keep the same path through the activity phases, including when changing supporting styles.
- ```sh
- npm run design-activity -- creating designs/example.tsx
- npm run design-activity -- writing designs/example.tsx
- npm run design-activity -- editing designs/example.tsx
- npm run design-activity -- done designs/example.tsx
- ```
- For example, signal an existing widget edit with `npm run design-activity -- editing designs/widgets/cheatname/performance.tsx` and send `done` with the same widget path.
- Use `creating` followed by `writing` for a new file. Use `editing` for an existing design. Send `done` after the final save, before browser interaction checks. Also clear the activity with `done` if work stops early. The signal expires after 60 seconds, so repeat the active phase if a long edit should keep the aura visible.
- 4. Render dropdowns with custom UI. Use a custom select or listbox for setting values and a custom action menu for commands such as “⋯”. Use accessible primitives where available, such as the workspace's Radix Dropdown Menu for commands. Do not use a browser-native HTML `<select>` for visible menu controls.
- 5. Use the real mouse pointer for interaction in the canvas. Include a separate in-menu preview panel or cursor demonstration only if the user explicitly requests it.
- ## Verify and hand off
- - Run `npm run build`. Open the preview using the URL-encoded menu filename, including `.tsx`, as in `http://localhost:5173/?design=example.tsx`. The root URL opens a blank canvas. For menu work, check the sidebar entry, default state, main mouse controls, dropdowns, and scrolling at the intended width and a reduced viewport.
- - For widget work, open the owning menu, switch to **Game Preview**, and enable the widget in the **Widgets** picker. Verify that it renders and drags alongside the menu, then uncheck **Show menu** and review it over the game scene. Use the visual checks in the widget reference.
- - Review the rendered menu using the visual check in the design reference. Fix any layout or control hierarchy issues you see before handoff.
- - For a new entry, check discovery in an open canvas when practical. For an edit, check that the current design stays selected and reflects the saved change. The aura temporarily locks preview input, so check controls after the activity clears.
- - Give the user the edited files and verified localhost preview link. For widgets, link to the owning menu and include the widget's picker name. If you cannot start or reach the canvas, report the blocker and which checks you completed.
README.md · README · 77 lines
- <div align="center">
- <img src="assets/canvas/public/mmforge-icon.png" alt="MMForge logo" width="80" height="80">
- <h1>mmforge-platform</h1>
- <p>Design cheat menus and HUD widgets with AI.</p>
- <a href="https://github.com/EunChae1110/mmforge-platform">
- <img src="https://img.shields.io/github/stars/EunChae1110/mmforge-platform?style=social" alt="GitHub stars">
- </a>
- <a href="https://github.com/EunChae1110/mmforge-platform/releases/latest">
- <img src="https://img.shields.io/github/v/release/EunChae1110/mmforge-platform?display_name=tag&label=version" alt="Latest MMForge release version">
- </a>
- </div>
- Use MMForge with Cursor, Claude Code, Codex, and general ai agent. Build a cheat menu from a prompt, recreate one from a screenshot, or select a control in the local Canvas and ask AI to change it. Controls and HUD readings use demo data.
- 
- ## Install
- ```bash
- npx skills add EunChae1110/mmforge-platform --skill mmforge-platform
- ```
- Add `-g` to install it for every project on this machine. Add `-y` to skip the prompts.
- Run these commands from the MMForge project root. For a standalone setup, copy the installed skill's `assets/canvas/` contents into your workspace first.
- ```bash
- npm ci
- npm run dev
- ```
- Open the URL Vite prints. Pick a design from the sidebar, or open it directly with `?design=example.tsx`.
- ## Use
- Start a new agent chat after installing. Try one of these prompts.
- ```
- Design a cheat menu with a sidebar, grouped controls, and a keybind row.
- Recreate this cheat menu from the screenshot.
- Move the selected slider's value above the track.
- Add a player list and a weapon skin widget to Neverlose.
- ```
- The agent returns the design file and a localhost preview link.
- ## Game Preview and widgets
- 1. Open a menu and switch to **Game Preview**. Use **Load game screenshot** to add a background.
- 2. Open **Widgets**, enable the overlays, and drag them into position. Positions and visibility are saved per menu.
- 3. Uncheck **Show menu** to see the HUD by itself.
- 
- Widgets go in the folder matching their menu. For `designs/neverlose.tsx`, put widget files in `designs/widgets/neverlose/`. Each widget file default-exports a React component. Use `widgetTitle` to set its picker label. [HUD widget design guide](references/hud-widget-design.md)
- ## AI edit status
- During an AI edit, the Canvas shows a centered aura with the phase and design name below it. You can interact with the preview again as soon as the edit finishes.
- Agents can signal an existing widget edit from the canvas project root.
- ```bash
- npm run design-activity -- editing designs/widgets/neverlose/weapon.tsx
- # Save the widget changes.
- npm run design-activity -- done designs/widgets/neverlose/weapon.tsx
- ```
- ## Updates
- Use the download icon in the Canvas to check for updates and read release notes. In-app updates use Git and npm. They keep your `designs/` folder and ask you to restart the Canvas. [GitHub Releases](https://github.com/EunChae1110/mmforge-platform/releases)
- If you are running a checkout of the skill repository, commit or stash local changes before updating. Update a standalone Canvas through its own repository. To publish a release, set the version in `assets/canvas/package.json` and its lockfile, then publish a GitHub release with the matching version tag.
- > This project will continue to be updated until I am satisfied.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.