Axure Design Assistant

Problem It Targets

The axure skill sits in the design-media category and its name points to Axure-related prototyping, interaction, or design tasks. However, the current SKILL.md reads like an unfinished skeleton: it does not define when to trigger, which tools to call, what best practices to follow, or which keywords should match. In other words, it reserves an entry point for Axure-oriented requests rather than proving a concrete Axure workflow.

How It Works Today

The skill defines four sections:
- When to use this skill: intended to detect whether a user is asking for Axure-related help.
- How to use this skill: intended to explain steps, but is marked as to be completed.
- Best Practices: intended to capture constraints and usage patterns, but is empty.
- Keywords: intended to improve triggering and discovery, but is empty.

Because the document lacks tool names, input/output formats, and examples, axure should be treated as a placeholder. It cannot be assumed to create prototypes, parse rp files, or restructure pages reliably.

Boundaries

Use it only for lightweight context, naming, or high-level Axure discussion. If the task requires concrete design operations, fill in the SKILL.md first with tools, parameters, and limits, and avoid relying on capabilities that are not documented.