methodological-rules skill
scriptsProvides qualitative research support through isolation rules, saturation tracking, workspace branching, and multi-researcher collaboration management.
- GitHub stars
- 21
- Files
- 11
- Last commit
- Nov 6, 2026
- License
- —
- Allowed tools
- —
What does the methodological-rules skill do?
methodological-rules provides qualitative research support through isolation rules, saturation tracking, workspace branching, and multi-researcher collaboration management.
Summary generated from the skill's SKILL.md.
About the methodological-rules skill
Qualitative researchers managing complex data analysis can use this skill to maintain methodological integrity through automated guardrails. It functions by reading research designs from a configuration file and generating specific Claude Code rules in the .claude/rules/ directory to prevent issues like cross-case contamination or premature theory synthesis. The system uses graduated friction levels, ranging from silent logging to hard stops, to guide the analytical process without being purely binary.
Beyond rule generation, the skill provides tools for tracking theoretical saturation, managing interpretive workspace branches, and coordinating multi-researcher teams. It automates the lifecycle of research rules by updating them during phase transitions and logging all changes to a reflexivity journal. Developers can utilize specialized scripts to run strain checks on rule overrides, apply methodology presets like Gioia or Charmaz, and generate visual dashboards or Mermaid diagrams to monitor project status and lineage.
What an agent can do with it
- 1Prevent cross-case contaminationGenerate isolation rules to ensure themes emerge independently from individual case folders before comparison begins.
- 2Monitor theoretical saturationTrack coding progress and redundancy to determine if the research has reached a state of saturation.
- 3Explore alternative interpretationsCreate a new analytical branch to test a different methodological framing without losing the original work.
- 4Manage collaborative coding sessionsCoordinate intercoder reliability sessions and track researcher roles for proper attribution.
- 5Apply established methodologiesAutomatically configure the workspace with default settings and vocabulary from recognized research frameworks.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the methodological-rules skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the methodological-rules skill in Plugin
/plugin marketplace add linxule/interpretive-orchestration /plugin install interpretive-orchestration@interpretive-orchestration
Install the methodological-rules skill in Claude Code
~/.claude/skills/methodological-rules/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/methodological-rules ~/.claude/skills/methodological-rulesInstall the methodological-rules skill in Claude Code (project)
.claude/skills/methodological-rules/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/methodological-rules .claude/skills/methodological-rulesInstall the methodological-rules skill in Codex
~/.agents/skills/methodological-rules/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/methodological-rules ~/.agents/skills/methodological-rulesInstall the methodological-rules skill in Gemini CLI
~/.gemini/skills/methodological-rules/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/methodological-rules ~/.gemini/skills/methodological-rulesInstall the methodological-rules skill in Claude.ai
npx degit linxule/interpretive-orchestration/plugin/skills/methodological-rules methodological-rules && zip -r methodological-rules.zip methodological-rules # claude.ai → Customize → Skills → + → Create skill → Upload a skill → methodological-rules.zip
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelinxule/interpretive-orchestration/plugin/skills/methodological-rules is public and reachablegithub.com/linxule/interpretive-orchestration/tree/HEAD/plug ↗Pass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit 2026-11-06github.com/linxule/interpretive-orchestration/commits ↗Pass
- No download-and-run or credential theft in scripts5 of 10 scripts read; none of them downloads and runs code, the rest were not readFinding
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/linxule/interpretive-orchestration/blob/HEAD/plug ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/linxule/interpretive-orchestration/blob/HEAD/plug ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/linxule/interpretive-orchestration/blob/HEAD/plug ↗Finding
SKILL.md
View on GitHubScript paths:
${CLAUDE_PLUGIN_ROOT}below is this plugin's root folder, two levels above this skill's own folder. Claude Code fills it in. If you see it unfilled, still starting with a dollar sign (as in Codex, Copilot CLI or Kimi Code), put that folder's absolute path in its place before you run a command.
Methodological Rules Skill
Comprehensive methodological support: isolation rules, strain detection, saturation tracking, workspace branching, multi-researcher collaboration, and visualization.
When to Use This Skill
Triggers:
- "generate rules" / "create rules" / "isolation rules"
- "methodology preset" / "apply preset"
- "saturation" / "am I saturated" / "theoretical saturation"
- "branch" / "fork" / "explore alternative"
- "team" / "add researcher" / "intercoder reliability"
- "dashboard" / "show status" / "visualize"
- After
/qual-designcompletes - When research_design changes in config
Auto-invoked:
- By
PostPhaseTransitionhook when sandwich_status changes - By
project-setupskill after design configuration
What This Skill Does
- Reads research design from
config.json - Generates Claude Code rules in
.claude/rules/ - Adapts rules based on current phase
- Logs changes to reflexivity journal
Rule Types Generated
| Rule | When Generated | Purpose |
|---|---|---|
case-isolation.md |
cases is non-empty and isolation_config.case_isolation.enabled is not false |
Prevent cross-case contamination |
wave-isolation.md |
waves is non-empty and isolation_config.wave_isolation.enabled is not false |
Preserve temporal integrity |
stream-separation.md |
research_design exists and isolation_config.stream_separation.enabled is not false |
Keep theory/data separate until synthesis |
Rule Lifecycle
research_design configured
↓
generate-rules.js creates .claude/rules/
↓
Rules active with configured friction level
↓
Phase transition detected (hook)
↓
update-rules.js checks relaxes_at conditions
↓
Rules regenerated with updated status
↓
Change logged to reflexivity journal
Friction Levels
Rules use graduated friction, not binary allow/block:
| Level | Behavior | When to Use |
|---|---|---|
silent |
Log only, no interruption | Low-risk boundaries |
nudge |
Gentle reminder in response | Moderate guidance |
challenge |
Pause, request justification | Important methodological boundaries |
hard_stop |
Block action | Critical integrity requirements |
Scripts
generate-rules.js
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/generate-rules.js" \
--project-path /path/to/project
What it does:
- Reads
config.jsonresearch_design section - Generates rule files from templates
- Places rules in
.claude/rules/(auto-discovered by Claude Code) - Returns JSON summary of generated rules
check-phase.js
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/check-phase.js" \
--project-path /path/to/project
What it does:
- Reads current sandwich_status
- Returns current phase and which rules should be relaxed
update-rules.js
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/update-rules.js" \
--project-path /path/to/project
What it does:
- Called by PostPhaseTransition hook
- Checks which rules need status updates
- Regenerates rules with new status
- Logs changes to reflexivity journal
strain-check.js
# Check strain status
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/strain-check.js" \
--project-path /path/to/project
# Record an override
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/strain-check.js" \
--project-path /path/to/project \
--record-override --rule-id case-isolation \
--justification "Building cross-cutting theme"
# Record resolution
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/strain-check.js" \
--project-path /path/to/project \
--record-resolution --rule-id case-isolation \
--resolution phase_transition
What it does:
- Tracks rule override patterns
- Detects strain (3+ overrides triggers review)
- Generates conversational review prompts
- Records resolutions for audit trail
apply-preset.js
# List available presets
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/apply-preset.js" --list-presets
# Apply a preset
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/apply-preset.js" \
--project-path /path/to/project --preset gioia_corley
What it does:
- Lists methodology presets (Gioia, Charmaz, Straussian, etc.)
- Applies preset defaults (isolation config, proactive prompts, vocabulary)
- Logs to reflexivity journal
saturation-tracker.js
# Check saturation status
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/saturation-tracker.js" \
--project-path /path/to/project --status
# Record document coding
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/saturation-tracker.js" \
--project-path /path/to/project \
--record-document --doc-id INT_001 --new-codes 5
# Record code refinement
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/saturation-tracker.js" \
--project-path /path/to/project \
--record-refinement --code-id coping --change-type split
# Full assessment
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/saturation-tracker.js" \
--project-path /path/to/project --assess
What it does:
- Tracks multi-dimensional saturation (generation, coverage, refinement, redundancy)
- Calculates saturation level (low → saturated)
- Provides recommendations based on saturation signals
workspace-branch.js
# Fork a branch
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/workspace-branch.js" \
--project-path /path/to/project \
--fork --name "alternative-structure" --framing exploratory
# Switch branches
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/workspace-branch.js" \
--project-path /path/to/project --switch --branch-id alt-123
# Merge (requires memo)
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/workspace-branch.js" \
--project-path /path/to/project \
--merge --branch-id alt-123 --memo "Synthesis explanation..."
What it does:
- Creates interpretive branches for exploratory analysis
- Tracks methodological framing (exploratory, confirmatory, negative case)
- Requires synthesis memo for merges
- Preserves abandoned branches for audit trail
viz-dashboard.js
# Full dashboard
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/viz-dashboard.js" \
--project-path /path/to/project --view all
# Specific views
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/viz-dashboard.js" \
--project-path /path/to/project --view saturation
# Mermaid export
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/viz-dashboard.js" \
--project-path /path/to/project --mermaid lineage
What it does:
- Renders CLI dashboards (ASCII art, box drawing)
- Views: saturation, rules, branches, all
- Exports Mermaid diagrams for documentation
researcher-team.js
# Add team member
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/researcher-team.js" \
--project-path /path/to/project \
--add-member --name "Jane Doe" --role coder
# Start ICR session
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/researcher-team.js" \
--project-path /path/to/project \
--start-icr-session --participants "jane,john" --documents "INT_001"
# Log attribution
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/researcher-team.js" \
--project-path /path/to/project \
--log-attribution --action created_code --target adaptive_coping
What it does:
- Manages research team members and roles
- Tracks current researcher for attribution
- Supports intercoder reliability sessions
- Logs all analytical decisions to researcher
Templates
Templates use Mustache-style placeholders:
{{study_type}}- From config{{case_count}}- Number of cases{{case_names}}- Comma-separated case names{{current_phase}}- Current sandwich_status phase{{relaxes_at_phase}}- When this rule relaxes{{friction_level}}- Current friction setting{{rule_status}}- active | relaxed{{timestamp}}- Generation timestamp
Integration Points
With existing architecture:
- Hooks:
PostPhaseTransitiontriggers rule updates - Config: Reads from
research_designsection - Agents:
@dialogical-coderreferences rules during coding - Commands:
/qual-statusshows active rules
With Claude Code:
- Rules placed in
.claude/rules/for auto-discovery - Rules have no
pathsfrontmatter, so they load in every session: an AI comparing cases or mixing streams may not have opened a file in the folders the rule names - Each rule names its folders in its text
Example Generated Rule
# .claude/rules/case-isolation.md
## Methodological Rule: Case Isolation
**Study:** 3-case comparative study
**Cases:** TechCorp Alpha, HealthCo Beta, FinServ Gamma
**Case folders:** data/cases/techcorp, data/cases/healthco, data/cases/finserv
**Status:** ACTIVE
**Friction:** CHALLENGE
### Guidance
When analyzing data from a specific case folder:
1. Focus ONLY on the current case's data
2. Let themes emerge from THIS case independently
3. Do NOT reference findings from other cases yet
4. Note cross-case hunches in memos, but don't act on them
### Why This Matters
Cross-case contamination during open coding prevents genuine pattern
emergence. Each case deserves analytical fresh eyes before comparison.
### When This Relaxes
This rule relaxes when you enter **Phase 3: Pattern Characterization**.
At that point, cross-case comparison becomes methodologically appropriate.
Check: config.json → sandwich_status.stage2_progress.phase3_pattern_characterization
---
*Generated: 2025-12-13 | Friction: CHALLENGE | Relaxes: phase3_pattern_characterization*
Allowed Tools
This skill may use:
- Read (config, templates)
- Write (rules, journal)
- Bash (script execution)
- Glob (find existing rules)
Related
- Config schema:
skills/project-setup/templates/config.schema.json - Hook:
hooks/post-phase-transition.js - Command:
/qual-design(triggers rule generation) - Philosophy: See DESIGN-PHILOSOPHY.md on cognitive hygiene
Files in this skill
11methodological-rules skill questions
How do I install the methodological-rules skill in Claude Code?
Run npx degit linxule/interpretive-orchestration/plugin/skills/methodological-rules ~/.claude/skills/methodological-rules. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the methodological-rules skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.