S4h Constraint Hardness Testing
Tests whether a stated constraint is real — distinguishing genuine limits from assumptions, habits, or politics dressed as facts. Triggers: 'is this really a constraint', 'challenge the assumption', 'who says we can't', 'is this actually fixed', 'test the constraint'.
Install
npx skills add human-avatar/skills-for-humanity --skill s4h-constraint-hardness-testinggit clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-constraint-hardness-testing ~/.claude/skills/s4h-constraint-hardness-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Constraint Hardness Testing Organisations accumulate phantom constraints — rules that were real once and calcified, or beliefs that were never tested, or someone's preference that got repeated until it sounded like policy. This skill separates genuine limits from assumed ones before any energy is spent working around or accepting them. --- ## Your Process **Step 1: State the Constraint** Write it exactly as it's been stated or assumed. Don't clean it up — the imprecision is often where the phantom lives. **Framing check:** Confirm the specific constraint and the goal it is blocking before continuing. State what you've identified — the exact constraint as you understand it and the goal or action it prevents — in one sentence, then use `AskUserQuestion`: - **Question:** "I'm reading this as: [your one-sentence framing of the constraint and the goal it blocks]. Is that right?" - **Header:** "Framing" - **Options:** - **Yes — proceed** — framing is correct - **Adjust** — one element is off; user will correct it before you continue - **Reframe** — different situation than read; incorporate the correction before proceeding **Step 2: Source It** Who said this constraint exists? When? Is the source a law or regulation, a signed contract, a technical impossibility, a leadership decision, a team preference, or unknown? The source determines the hardness ceiling. **Step 3: Consequence Test**
Details
- Skill name
s4h-constraint-hardness-testing- Repository
- human-avatar/skills-for-humanity
- Path
skills/s4h-constraint-hardness-testing/SKILL.md- License
- MIT
- Repo updated
- 15 July 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the S4h Constraint Hardness Testing skill do?
Tests whether a stated constraint is real — distinguishing genuine limits from assumptions, habits, or politics dressed as facts. Triggers: 'is this really a constraint', 'challenge the assumption', 'who says we can't', 'is this actually fixed', 'test the constraint'.
How do I install the S4h Constraint Hardness Testing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add human-avatar/skills-for-humanity --skill s4h-constraint-hardness-testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is S4h Constraint Hardness Testing popular?
It lives in human-avatar/skills-for-humanity, which has 242 GitHub stars and 25 forks, and is included in 1 curated skill list.
Related skills
S4h
242human-avatar/skills-for-humanity
Master orchestration skill. Takes any situation in plain English, identifies the underlying goal, designs a multi-skill reasoning workflow, and executes it sequentially — feeding each skill's output into the next. Use when you say 'help me think through this', 'I need to figure out what to do', 'where do I start', or any time you want structured thinking applied end-to-end rather than routed to a single tool.
S4h Aesthetic
242human-avatar/skills-for-humanity
Entry point for the aesthetic toolkit. Routes to the right aesthetic skill based on your situation. Use when you say 'aesthetic', 'check the design', 'does this feel right', 'is this elegant', 'is this too complex', 'what pattern is this', 'find the simpler version', or want an aesthetic lens applied without knowing which specific tool fits.
S4h Aesthetic Coherence Check
242human-avatar/skills-for-humanity
Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision. TRIGGERS: 'coherence check', 'does this feel unified', 'something feels off', 'inconsistent', 'check the whole', 'does this hang together'.
S4h Design Iteration
242human-avatar/skills-for-humanity
Structures the feedback loop between making and learning — prototyping, testing, and convergence toward fit. Triggers: 'prototype and test', 'iterate on the design', 'how do we test this', 'get feedback on the design', 'what should we prototype', 'design feedback loop', 'test and learn', 'are we converging'.
S4h Analogy Structure Mapping
242human-avatar/skills-for-humanity
Identifies the deep structural correspondence between two situations — genuine isomorphism vs superficial similarity. Triggers: 'does this analogy hold', 'map the structure', 'is this really like that', 'structural similarity', 'test the comparison'.
S4h Epistemology Justification
242human-avatar/skills-for-humanity
Analyzes what would actually justify believing a claim. Maps the justification structure (foundationalist, coherentist, reliabilist) and identifies the weakest link in the chain. Use when you say 'what would it actually take to know this', 'is this belief actually justified', 'what's the foundation for this assumption', 'we keep citing the same evidence for everything', 'I believe this but I can't say why', 'what would change my mind', or when a claim feels supported but you want to make the support structure explicit and test it.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.