القائمة
Use when an agent needs to understand a Feather Love2D project before making code, runtime, plugin, MCP, build, or QA changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when an agent should prepare or run debug-oriented Feather builds for desktop, web, Android, iOS, or Steam Deck development.
Use when an agent needs to diagnose Love2D behavior from Feather logs, observer values, assets, runtime messages, or telemetry.
Use when an agent should inspect or control a running Feather desktop session through MCP.
Use when an agent should create, preview, tune, export, or QA particle systems with Feather MCP Particle Playground tools.
Use when an agent needs to profile frame time, memory, runtime overhead, hotspots, or performance regressions in a Feather session.
Use when an agent should inspect, configure, enable, or invoke Feather built-in or live-session plugin behavior through MCP.
| name | feather-project-context |
| description | Use when an agent needs to understand a Feather Love2D project before making code, runtime, plugin, MCP, build, or QA changes. |
feather.config.lua, feather.build.json, feather.lock.json, and any local AGENTS.md.feather doctor <dir> --json when available for a structured health report.feather plugin list <dir> for installed plugins.feather://sessions, feather_session_snapshot, and section resources for config, logs, performance, debugger, plugins, assets, and observers.feather doctor <dir> --production --json before release-facing changes.Report concrete project facts first: launch command, session status, enabled plugins, risky opt-ins, build targets, and the smallest next action.
references/workflow.md for the project inventory checklist, risk posture, and report template.