physical-contradictions
Skill14 starsChanged 43 days agoLicence not identifiedView on GitHub
TRIZ Physical Contradictions (ccTOPP v4.1) — formulates a physical contradiction with both justifications and resolves it with two documented strategy sets: the Litvin variant (separation in space, time, relation, system level, plus Satisfy and Bypass) and the Zlotin/Zusman variant (separation in space, time, on condition, between the parts and the whole, plus Transition to Alternative System), each mapped to the recommended Inventive Principles. Use this skill when the user mentions 'physical contradiction', 'physikalischer Widerspruch', 'separation principles', 'Separationsprinzipien', 'separation in space', 'separation in time', 'separation in relation', 'separation on condition', 'Litvin', 'Zlotin', 'Zusman', 'Satisfy', 'Bypass', or has conflicting requirements for one parameter of one component that must take two opposing values at the same time. Does NOT handle engineering contradictions ('IF … THEN … BUT …'), the Altshuller Matrix or Matrix 2003 — use the contradiction-solver skill for those.
In this repository26 other files it gives its agents.
- 76-standard-solutionsSkill
- business-function-analysisSkill
- cause-effect-chain-analysisSkill
- contradiction-solverSkill
- derivative-resourcesSkill
- feature-transferSkill
- function-analysis-advancedSkill
- function-analysisSkill
- function-interaction-analysisSkill
- function-oriented-searchSkill
- idealitySkill
- innovation-checklistSkill
- interactive-trimmingSkill
- mpv-analysisSkill
- patent-analyzerSkill
- perception-mappingSkill
- problem-operatorSkill
- resource-analysisSkill
- root-cause-analysisSkill
- root-conflict-analysisSkill
- smart-little-peopleSkill
- solutions-at-system-levelsSkill
- sustainability-assessmentSkill
- system-descriptionSkill
- system-operatorSkill
- trimmingSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.