agentleFS
jblosseyjblossey/houserules/.claude/skills/project-knowledge/SKILL.md

project-knowledge

Skill2 starsChanged 20 days agoMITView on GitHub

Use before reading or changing any file in this repository

16 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

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Before editing, run houserules for <every file you will change> and read the rules it prints.

    line 14
  2. Very specific:

    Run houserules get <ids> for any rule you are unsure about, and for every id your task names.

    line 15

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

Generated from knowledge/ by houserules render. Do not edit.

Project knowledge

Retrieval protocol

Save the output of every houserules command to a file, then read the file with your file-read tool.

  1. Before editing, run houserules for <every file you will change> and read the rules it prints.
  2. Run houserules get <ids> for any rule you are unsure about, and for every id your task names.

Topics

houserules 54 Working in the houserules kit repository knowledge-base 7 Authoring knowledge entries process 56 How work runs: batches, dispatch, reviews, rulings quality 11 Quality principles security-hygiene 7 Dependency, commit, and test hygiene writing-style 5 Writing style for docs, comments, commits, reports

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.