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

scaffold

Skill49 starsChanged 25 days agoApache-2.0View on GitHub

Generate a full resource (migration, model, policy, controller, routes, views or pages, tests) in a Rust off Rails app, like `rails g scaffold`. Use when the user asks to scaffold or add a CRUD resource with fields, e.g. "scaffold Book title:string rating:integer".

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, docs-ci and 10 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.
  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • SethGammonSkill

    research-fleet

    Parallel research using Fleet wave mechanics. Spawns multiple scout agents, each investigating a different angle of the same question. Findings are compressed between waves. Produces a unified research brief from multiple independent perspectives.

    Also in 3 projects that use this

  • RachaelQuiselSkill

    client-docs

    Client documentation. Use when a build needs documentation updates or missing project documents need to be identified.

    Also in 3 projects that use this

  • vicoa-aiSkill

    live-preview

    Start a local app in the current user project, expose it through a tunnel, and return preview details in structured Markdown. Use when the user asks for a preview URL, public URL, shareable localhost, mobile/web preview, or tunnel setup.

    Also in 4 projects that use this

  • +4 more from jh941213

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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:

    If not already done this session, read .offrails/AGENTS.md and its load order, and note FRONTEND_MODE from the app's AGENTS.md.

    line 13
  3. Very specific:

    Ask the feature-level questions from .offrails/interview.md that the request leaves open (ownership, deletion, who can see it), and only …

    line 14

“Common” is measured: kept by at least 6 in 10 of the 42 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:scaffold

Only for Rust off Rails apps (a .offrails/ directory exists). If there isn't one, suggest /offrails:new and stop.

Request: $ARGUMENTS

  1. If not already done this session, read .offrails/AGENTS.md and its load order, and note FRONTEND_MODE from the app's AGENTS.md.
  2. Ask the feature-level questions from .offrails/interview.md that the request leaves open (ownership, deletion, who can see it), and only those.
  3. htmx mode: run cargo offrails g resource <plural> field:type… (--dry-run first; field syntax: .offrails/generators/README.md#fields; for a one-word public CRUD to read first, cargo offrails snippet show resource), commit, then do what it printed and what .offrails/generators/scaffold.md leaves to you (spec ACs into the tests, the // APP: lines, seeds, the browser smoke). Other modes: cargo offrails g model … (and g api … for a public API), then the rest of scaffold.md for the app's FRONTEND_MODE by hand.
  4. Finish with cargo offrails verify (--full if this is the last slice; .offrails/workflow.md#definition-of-done), then report per "Talking to the human".

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