package-blured
Package the Blured Engine into a distributable directory
Best use case
package-blured is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Package the Blured Engine into a distributable directory
Teams using package-blured should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/package-blured/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How package-blured Compares
| Feature / Agent | package-blured | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Package the Blured Engine into a distributable directory
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Package Blured Engine
This skill packages the built Blured Engine into a distributable directory at `dist/blured-engine/`.
## Instructions
When the user asks to "package blured", "package the engine", "create a dist", or similar, run:
```bash
bash g:/blured-engine/.claude/skills/package-blured/scripts/package_blured.sh
```
## Prerequisites
Both OpenCode and Godot must be built first. If not, tell the user to run `/build-blured`.
## Output
The packaged engine is created at `dist/blured-engine/` with this structure:
```
dist/blured-engine/
blured.exe (launcher with auto-update)
bin/
blured.exe (Godot editor)
opencode.exe (AI server)
tools/
ScreenCapture.exe (snipping tool)
docs/
blured.json
blured-models.json
VERSION
LICENSE
```
## Notes
- Image processing (sharp, gifenc, opencv-js) is now handled natively by Godot's Image class -- no node_modules needed
- The `tools/` directory contains ScreenCapture.exe for the snipping feature
- The launcher is built from Rust source in `launcher/`Related Skills
start-blured
Start the Blured Engine (OpenCode AI server + Godot editor)
build-blured
Build the Blured Engine (OpenCode + Godot)
worldbuilding
Build the game world's foundation before generating concept art. Use when starting a new game project, when user says "build world", "worldbuilding", "world design", or before art direction. Guides the user through 3 questions to establish the world's unique identity.
ui-production
Create polished player-facing UI from whitebox to final assets. 5-step workflow from UI mockup to deployed game UI. Do NOT use for whitebox/prototype UI.
ui-layout-replicate
Replicate a UI layout from a cornerstone reference image into a pixel-perfect .tscn scene. Use when user says "replicate UI layout", "build layout from reference", "1:1 UI copy", or has a cornerstone UI image to turn into a scene.
polish
Systematic polish pass — add juice, screen effects, audio, transitions, UI animations, and game feel improvements. Use when user says "polish", "add juice", "make it feel better", "add effects", or similar.
analyze-screenshot
Analyze game screenshots for visual design issues, UI problems, and art consistency. Automatically triggers when a screenshot is attached.
add-level
Guided level design — create a new level with purpose, environment, layout, enemies, and auto-generated assets. Use when user says "add a level", "new level", "create a stage", or similar.
tech-debt
Clean up tech debt - remove obsolete files, temporary files, unused code, dead imports, and other cruft. Use when user wants to clean up the codebase, remove unused code, or reduce tech debt.
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
git-dev-merge
Merge feature branches back to their base branches across the main repo and submodules. Use when user says "merge feature", "finish feature", "merge back", or invokes /git-dev-merge.
git-dev-feature
Start a new feature development workflow by creating an issue and feature branches across the main repo and submodules.