unity-tool-creation
Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context. [GENERATED BY MOTIF — review and customize]
Best use case
unity-tool-creation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context. [GENERATED BY MOTIF — review and customize]
Teams using unity-tool-creation 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/unity-tool-creation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How unity-tool-creation Compares
| Feature / Agent | unity-tool-creation | 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?
Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context. [GENERATED BY MOTIF — review and customize]
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
# Unity Tool Creation Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context. ## When to Use - User describes a visual effect or camera angle needed - User requests a new scene element or UI component for Unity - Especially when: the feature involves multiplayer elements that are hard to test alone ## Instructions 1. Clarify the visual requirements if the description is ambiguous 2. Create a C# script implementing the requested feature 3. Add a debug/test button in the Unity Inspector so the feature can be tested without other players 4. Integrate with the existing camera or scene system 5. Provide clear instructions for testing in Unity Editor 6. Note any dependencies on other systems (WebRTC, multiplayer state) ## Best Practices - Always add a debug button for isolated testing - Keep new scripts focused on one feature - **Avoid:** Don't modify existing camera systems without discussing first ## Common Pitfalls | Problem | Solution | |---|---| | Feature can't be tested without multiple players connected | Add mock/debug mode that simulates multiplayer input | | New script breaks existing camera system | Test with existing features enabled before committing | ## Key Constraints - Every visual feature must have a debug/test button - Don't modify existing camera systems without user approval
Related Skills
motif-analyze
Run Motif to generate your vibe report, launch the live dashboard, or personalize your CLAUDE.md and skills. Use when the user says "motif", "run motif", "vibe report", "generate my report", "motif live", "start the dashboard", "analyze my coding patterns", "personalize my AI", "generate rules for me", or "motif analyze".
session-wrapup
Handles end-of-session housekeeping: committing code, pushing to remote, deploying, and summarizing progress. Prevents forgotten commits and undocumented progress. [GENERATED BY MOTIF — review and customize]
session-startup
Ensures the agent is oriented on the current project state before taking action. Prevents the agent from working with stale context or making assumptions about project status. [GENERATED BY MOTIF — review and customize]
deploy-production
Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. [GENERATED BY MOTIF — review and customize]
bug-fix-iteration
Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. [GENERATED BY MOTIF — review and customize]
Skill Maker: AI Skill Factory for Tools
Meta-skill that generates domain-specific AI skills from tool documentation
performing-windows-artifact-analysis-with-eric-zimmerman-tools
Perform comprehensive Windows forensic artifact analysis using Eric Zimmerman's open-source EZ Tools suite including KAPE, MFTECmd, PECmd, LECmd, JLECmd, and Timeline Explorer for parsing registry hives, prefetch files, event logs, and file system metadata.
analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware samples using apktool for decompilation, jadx for Java source recovery, and androguard for permission analysis, manifest inspection, and suspicious API call detection.
tool-discovery
Recommend the right agents and skills for any task. Covers both heavyweight agents (Task tool) and lightweight skills (Skill tool). Triggers on: which agent, which skill, what tool should I use, help me choose, recommend agent, find the right tool.
no-tools
Instructions only skill
toolkit-recall
Search past decisions, prior research, conversation history, monorepo docs, and fetched web pages. Use toolkit recall search to find context from previous work, and toolkit fetch to save web pages for future search.
modern-cli-tools
Modern Unix command alternatives - faster, more user-friendly tools for everyday tasks When Claude is about to use legacy tools (find, grep, ls, cat, sed, du, df, ps) OR when user mentions fd, rg, eza, bat, or asks about faster alternatives