Index of every page on this site: llms.txt
All skills
sebastianelvis avatar

/rustify-design

@814777d
Run it yourself

Recover an original interaction and design specification as EARS requirements with captures. Use during Rustify discovery for visual interfaces, CLI behavior, and other interaction contracts.

  • 5 files
  • 15.4 KB
  • Updated last week
  • GitHub
Use this Skill: https://skilld.dev/gh/sebastianelvis/rustify/rustify-design

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈333 when used: this file. ≈3.5k more on demand in 4 files.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈208 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Recover the interaction specification

The agent reads .rustify/state.yaml and the project format. The agent writes with the standards guide. The agent preserves original appearance and behavior without aesthetic improvements.

  1. The agent reads the investigation methods before capturing interactions.
  2. The agent invokes rustify-probe for interface captures and binary evidence. The orchestrator owns dependency setup and shared session coordination.
  3. The agent reads the output rules before writing .rustify/recovered/ux.md.
  4. The agent uses the interaction specification template for visual or stateful interfaces. The agent uses the CLI specification template for command-line interfaces. A mixed product uses both structures in one specification.
  5. The agent returns its requirement, evidence, scenario, and declarative-test shards to the orchestrator. The agent preserves original capture paths and REA Evidence IDs.

Every interface state and transition traces to captures and ux requirements. An unknown token, transition, or expected result stays an open gap.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 814777d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
Other metadata
metadata
{
  "dependencies": "rea",
  "rea-source": "https://github.com/morluto/rea",
  "rea-setup": "https://github.com/morluto/rea/blob/main/docs/installation.md"
}

README badge

README badge for sebastianelvis/rustify/rustify-design