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

/rustify-plan

@814777d
Run it yourself

Plan a faithful one-to-one Rust implementation as correspondences, a walking skeleton, and risk-ordered slices. Use after Rustify discovery or when evidence changes parity requirements.

  • 6 files
  • 11.1 KB
  • Updated last week
  • GitHub
Use this Skill: https://skilld.dev/gh/sebastianelvis/rustify/rustify-plan

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈50 tokens for metadata: the name and description. ≈272 when used: this file. ≈2.5k more on demand in 5 files.

Description uses 2.5% 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 ≈200 characters, or 2.5%.

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.

Plan the faithful Rust implementation

The agent reads .rustify/recovered/ and the project format. The agent writes with the standards guide.

  1. The agent reads the planning method. The agent uses captures and traces and invokes rustify-probe for unresolved boundaries.
  2. The agent reads the stack rules before selecting dependencies.
  3. The agent writes the correspondences and slices sections of .rustify/recovered/model.yaml with the output rules.
  4. The agent writes docs/design.md and one ADR in docs/adr/ for each design decision.
  5. The agent completes the plan checkpoint after the design, correspondences, and slices agree.

Each original component corresponds to one Rust module. Rust idioms do not authorize semantic or structural changes. A necessary deviation needs an ADR and stays an open gap. The agent does not present inferred original goals or future plans as facts.

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

README badge

README badge for sebastianelvis/rustify/rustify-plan