agentleFS
Sign inStart free
delorenjdelorenj/ssbnk/.agents/skills/code-philosophy/SKILL.md

code-philosophy

Skill2 starsChanged 50 days agoMITView on GitHub

Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ccgargantua/gars-claude-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Practice: Use if (!valid) return; doWork().

    line 17
  2. Distinctive:

    Concept: Don't check data repeatedly.

    line 20
  3. Very specific:

    Defense: Avoid void functions that mutate global state.

    line 27
  4. Distinctive:

    Rule: If a state is invalid, halt immediately with a descriptive error.

    line 31
  5. Distinctive:

    Before completing your task, verify:

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Internal Logic Philosophy: The 5 Laws of Elegant Defense

Role: Principal Engineer for all Internal Logic & Data Flow — applies to backend, React components, hooks, state management, and any code where functionality matters.

Philosophy: Elegant Simplicity — code should guide data so naturally that errors become impossible, keeping core logic flat, readable, and pristine.

The 5 Laws

1. The Law of the Early Exit (Guard Clauses)

  • Concept: Indentation is the enemy of simplicity. Deep nesting hides bugs.
  • Rule: Handle edge cases, nulls, and errors at the very top of functions.
  • Practice: Use if (!valid) return; doWork(); instead of if (valid) { doWork(); }.

2. Make Illegal States Unrepresentable (Parse, Don't Validate)

  • Concept: Don't check data repeatedly; structure it so it can't be wrong.
  • Rule: Parse inputs at the boundary. Once data enters internal logic, it must be in trusted, typed state.
  • Why: Removes defensive checks deep in algorithmic code, keeping core logic pristine.

3. The Law of Atomic Predictability

  • Concept: A function must never surprise the caller.
  • Rule: Functions should be "Pure" where possible. Same Input = Same Output. No hidden mutations.
  • Defense: Avoid void functions that mutate global state. Return new data structures instead.

4. The Law of "Fail Fast, Fail Loud"

  • Concept: Silent failures cause complexity later.
  • Rule: If a state is invalid, halt immediately with a descriptive error. Do not try to "patch" bad data.
  • Result: Keeps logic simple by never accounting for "half-broken" states.

5. The Law of Intentional Naming

  • Concept: Comments are often a crutch for bad code.
  • Rule: Variables and functions must be named so clearly that logic reads like an English sentence.
  • Defense: isUserEligible is better than check(). The name itself guarantees the boolean logic.

Adherence Checklist

Before completing your task, verify:

  • Guard Clauses: Are all edge cases handled at the top with early returns?
  • Parsed State: Is data parsed into trusted types at the boundary?
  • Purity: Are functions predictable and free of hidden mutations?
  • Fail Loud: Do invalid states throw clear, descriptive errors immediately?
  • Readability: Does the logic read like an English sentence?

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