agentleFS
Sign inStart free
maxwell2732maxwell2732/claudecode-research-harness-workflow/skills/principles/SKILL.md

principles

Skill42 starsChanged 6 days agoMITView on GitHub

Explicit helper for development principles, safety guidelines, and diff-aware editing rules. Do NOT load for: implementation, review, workflow coaching, or VibeCoder onboarding.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ketchup, benchmark-checklist 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.
  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 5 projects that use this

  • Xia-AtaraxiaSkill

    benchmark-checklist

    Vets performance measurements for the limiter, tuning, physical limits, errors, repeatability, relevance, and proof that timed work happened. It applies to 'check this benchmark', 'report this speedup', measured regressions, and choosing a library or configuration from numbers. It reports spread and gaps before drawing a conclusion. Not for general testing policy or choosing test oracles - use principle-testing.

    Also in 6 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 3 projects that use this

  • jaydubya818Skill

    interrogate

    Use when a change's assumptions, evidence, or design need adversarial review.

    Also in 9 projects that use this

  • jaydubya818Skill

    show-me-your-work

    Use when long-running work needs an auditable decision and evidence log.

    Also in 8 projects that use this

  • drafaelSkill

    sharpen

    Deepen a task without broadening its scope, then rewrite its prompt. Manual invocation only; use when the user explicitly invokes sharpen or requests this prompt-sharpening workflow. Do not execute the rewritten task or decide choices the user owns.

    Also in 4 projects that use this

  • +6 more from jaydubya818

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the appropriate reference file from "Feature Details" above

    line 26

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

Principles Skills

A set of skills providing development principles and guidelines.

Feature Details

FeatureDetails
Core PrinciplesSee references/general-principles.md
Diff EditingSee references/diff-aware-editing.md
Context ReadingSee references/repo-context-reading.md
VibeCoderSee references/vibecoder-guide.md

Execution Steps

  1. Classify the user's request
  2. Read the appropriate reference file from "Feature Details" above
  3. Reference and apply its contents

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