agentleFS
Sign inStart free
rust-off-railsrust-off-rails/rustoffrails/skills/generate/SKILL.md

generate

Skill49 starsChanged 25 days agoApache-2.0View on GitHub

Run a Rust off Rails generator other than scaffold, like `rails generate`: model, resource, migration, job, mailer, channel, authentication, task. Use when the user asks to add a background job, an email, live updates, login, a migration, or a model to a Rust off Rails app.

19 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Only for Rust off Rails apps (a .offrails/ directory exists).

    line 9
  2. Very specific:

    Read .offrails/AGENTS.md and its load order if not already done this session.

    line 13
  3. Very specific:

    Write or update the matching product/features/*.md spec first.

    line 15
  4. Very specific:

    Run each generator (cargo offrails g <kind> … --dry-run first when unsure, then without) or cargo offrails snippet add <name>, commit, then …

    line 16

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/offrails:generate

Only for Rust off Rails apps (a .offrails/ directory exists).

Request: $ARGUMENTS

  1. Read .offrails/AGENTS.md and its load order if not already done this session.
  2. Pick the generator(s) from the table in .offrails/generators/README.md (cargo offrails g --help), or a snippet when the request is a recipe (a feed, slugs, Markdown, a pager: cargo offrails snippets). If the request is in plain English ("email users a weekly digest"), map it to generators yourself; it may need several (mailer + job). A kernel need (mail, a queue, sign-in, sockets) is a part: cargo offrails parts, cargo offrails add <part>.
  3. Write or update the matching product/features/*.md spec first.
  4. Run each generator (cargo offrails g <kind> … --dry-run first when unsure, then without) or cargo offrails snippet add <name>, commit, then follow the recipe's "what to customize" and the next steps it printed: the // APP: lines, the spec's tests, migrate. Then run cargo offrails verify (--full when the work is done; .offrails/workflow.md#definition-of-done).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free