agentleFS
rust-off-railsrust-off-rails/rustoffrails/skills/new/SKILL.md

new

Skill49 starsChanged 25 days agoApache-2.0View on GitHub

Create a new Rust off Rails web app (the `rails new` of Rust). Use when the user wants to start a new Rust web app, SaaS, internal tool or site, or says "rails new", "new app", or "off rails". Runs the interview, confirms a plan, then generates the app.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gate, review and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Load the framework: read $FW/AGENTS.md, then its load order (interview.md, doctrine.md, structure.md, stack.md, workflow.md).

    line 14

“Common” is measured: kept by at least 6 in 10 of the 20 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:new — rails new for Rust off Rails

Framework root for this skill: ${CLAUDE_PLUGIN_ROOT} (call it $FW). Every path below is relative to it.

Request: $ARGUMENTS

  1. Preflight. The current directory must be empty or a fresh git repo. If it already contains .offrails/, stop: this is an existing app, so use /offrails:feature or /offrails:scaffold instead.
  2. Load the framework: read $FW/AGENTS.md, then its load order (interview.md, doctrine.md, structure.md, stack.md, workflow.md). Those docs win over your habits.
  3. Interview per $FW/interview.md, using AskUserQuestion. Skip any question the request already answers. "You decide" means take the defaults. Max 3 rounds.
  4. Confirm the plan (the compact block in interview.md), including the parts you propose from the plan ($FW/template/README.md#choosing-parts, with the link https://github.com/rust-off-rails/samples), and wait for a yes.
  5. Generate by executing $FW/generators/new.md step by step: step 1 runs the template generator (cargo run -q --manifest-path "$FW/tools/offrails-gen/Cargo.toml" --target-dir <dir>/target/offrails-gen -- new <dir> <crate> "<Name>" --pitch … --parts …), which copies the template, vendors $FW into .offrails/ and adds the parts. Never retype the skeleton.
  6. Build the plan's features one vertical slice at a time, each piece from a snippet (cargo offrails snippets), a generator ($FW/generators/scaffold.md, …) or the guides, the parts for accounts (authentication.md), each finishing on a green cargo offrails verify (seconds; cargo nextest run <test> while one is red); cargo offrails verify --full once, after the last slice.
  7. Report in product terms: what exists, bin/setup && bin/dev, what's next. Mention /offrails:feature, /offrails:deploy and /offrails:doctor.

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.