agentleFS
wilaniswilanis/wilanis-js/.claude/skills/rfc/SKILL.md

rfc

Skill1 starsChanged 57 days agoApache-2.0View on GitHub

Propose or expand an RFC in wilanis-js: pick the next number, write the spec from the template, open the pull request and the tracking issue. Use when asked to "write an RFC", "spec this out", "expand stub NNNN", or when a task needs a new kind, rule family, hook or promise.

  • Commits and pushes

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research and setup.

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.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 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 11 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:

    Add the row to docs/rfcs/README.md.

    line 42

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

Proposing an RFC

The process is docs/rfcs/0001-the-rfc-process.md. This skill is the procedure.

When one is needed

A new document kind, a new checker rule family, a new plugin hook, a port or kind a plugin grants, a promise the runtime makes (a semantic, a compatibility rule), or a change to any of those. A fix, a refactor or a new rule inside an existing family under an accepted RFC needs none.

1. Number and file

ls docs/rfcs | sort | tail -1
cp docs/rfcs/0000-template.md docs/rfcs/NNNN-short-title.md

To expand a stub, edit its file in place and change draft (stub) to draft.

2. Write

Fill every section of the template; write "none" rather than deleting a subsection. Ground every claim in the code: name the file and function that changes, the existing rule the new one sits beside, the command whose output changes. Codes for new rules are written as the family letter and a placeholder (G0nn) with the note that numbers are assigned when the implementing pull request lands. Show the documents an author writes as JSON against example/. Say what the RFC does not do.

3. Track first

Open the tracking issue with the RFC form, gh issue create -R wilanis/wilanis-js --template rfc.yml (or on GitHub): paste the Summary and set the issue's milestone to the demo docs/roadmap.md names (add the RFC there if it is new). Its number N names the branch and goes into the RFC's header (**Tracking issue:** #N).

4. Index and propose

Add the row to docs/rfcs/README.md. Branch on the issue number, commit, push, open the pull request, and paste its link into the issue:

git switch -c N-rfc-NNNN-short-title main
gh pr create -R wilanis/wilanis-js --label rfc --title "RFC NNNN: Title" --fill

5. Acceptance

The maintainer validates every detail on the pull request. On merge the header's status is accepted, the tracking issue's label moves from status:draft to status:accepted, and the Implementation plan becomes sub-issues labelled task, the first unblocked ones status:ready.

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.