agentleFS
CarriedWorldUniverseCarriedWorldUniverse/nexus/.agents/skills/house-style/SKILL.md

house-style

Skill0 starsChanged 36 days agoApache-2.0View on GitHub

How code and prose should read on nexus — Go idioms, the no-build dashboard, commit conventions, clear correct writing.

10 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, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    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. Distinctive:

    Write so it reads like the rest of the work.

    line 9
  2. Very specific:

    Commit messages: a clear subject line, body explaining why, and the trailer Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>.

    line 15
  3. Distinctive:

    Write the forward state. Don't call out what was removed ("removed X", "X no longer exists", "deprecated") — describe what is, not what was.

    line 20
  4. Distinctive:

    No decorative filler, no hype, no emoji padding.

    line 21

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

house-style

Write so it reads like the rest of the work. Match what's already there.

Code

  1. Go: standard idioms, gofmt, errors wrapped with context, small focused files.
  2. The dashboard is no-build Preact + htm: window.__preact, no bundler, no npm build step. Don't add a build toolchain.
  3. Match the surrounding comment density and naming. Don't over-comment or rename for taste.
  4. Commit messages: a clear subject line, body explaining why, and the trailer Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>.
  5. One ticket per PR.

Prose (specs, PRs, comments, tickets, chat)

  1. Clear, concise, correct grammar. Short sentences. Say the thing.
  2. Write the forward state. Don't call out what was removed ("removed X", "X no longer exists", "deprecated") — describe what is, not what was.
  3. No decorative filler, no hype, no emoji padding.
  4. Report what you did and what you checked. Don't narrate the reader's feelings or the moment.

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.