agentleFS
Sign inStart free
PthahnixPthahnix/De-Anthropocentric-Research-Engine/skills/apply-separation-principle/SKILL.md

apply-separation-principle

Skill504 starsChanged 49 days agoApache-2.0View on GitHub

Resolve a physical contradiction by separating conflicting requirements in time, space, scale, condition, or system level.

1 other project uses 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. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Test separation in time, space, scale, condition, and system level.

    line 17
  2. Distinctive:

    Do not call parameter tuning a separation when both requirements still occur under the same condition.

    line 27

≈ “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

apply-separation-principle

Purpose

Resolve a physical contradiction by separating conflicting requirements in time, space, scale, condition, or system level.

Input contract

required: [contradiction, conflicting_requirements]
optional: [system_boundary, operating_conditions]
constraints: [requirements must be stated as mutually conflicting outcomes]

Procedure

  1. State the useful and harmful effects that cannot coexist (conflicting_requirements).
  2. Test separation in time, space, scale, condition, and system level.
  3. Select the separation that removes the conflict and state its operating condition.

Output contract

produces: [separation_candidates, selected_principle, operating_condition]
delta_fields: [findings, hypothesis_updates, decisions, uncertainties]

Quality gates

  • Each candidate names the separated dimension and preserves the useful effect while removing the harmful one.

Failure and counterexamples

Do not call parameter tuning a separation when both requirements still occur under the same condition.

Provenance map

  • triz/separation-principles: concept (the exact pool entry is singular separation-principle; near-name substitution is forbidden).

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