Skip to content
Skills Library
Science & research · Planning

methodological-rules

/methodological-rules

This skill should be used when users mention 'generate rules', 'isolation rules', 'methodology preset', 'apply preset', 'saturation', 'am I saturated', 'branch', 'fork', 'explore alternative', 'team', 'add researcher', 'intercoder reliability', 'dashboard', 'show status', or after /qual-design completes.

Licence
MIT
Last repository change
06.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
16
Scripts
10
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 10 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/apply-preset.js, scripts/check-phase.js, scripts/generate-rules.js, scripts/phase.js, scripts/researcher-team.js, scripts/saturation-tracker.js, scripts/strain-check.js, scripts/update-rules.js, scripts/viz-dashboard.js, scripts/workspace-branch.js

What it does and when to use it

This skill should be used when users mention 'generate rules', 'isolation rules', 'methodology preset', 'apply preset', 'saturation', 'am I saturated', 'branch', 'fork', 'explore alternative', 'team', 'add researcher', 'intercoder reliability', 'dashboard', 'show status', or after /qual-design completes.

Triggers from the description

generate rulesisolation rulesmethodology presetapply presetsaturationam I saturatedbranchfork
Original author description

This skill should be used when users mention 'generate rules', 'isolation rules', 'methodology preset', 'apply preset', 'saturation', 'am I saturated', 'branch', 'fork', 'explore alternative', 'team', 'add researcher', 'intercoder reliability', 'dashboard', 'show status', or after /qual-design completes.

How it works

  1. When to Use This Skill
  2. What This Skill Does
  3. Rule Types Generated
  4. Rule Lifecycle
  5. Friction Levels
  6. Scripts
  7. Templates
  8. Integration Points
  9. Example Generated Rule
  10. Allowed Tools
Original SKILL.md headings · 345 lines, 1,184 words
SKILL.md preview
---
name: methodological-rules
description: "This skill should be used when users mention 'generate rules', 'isolation rules', 'methodology preset', 'apply preset', 'saturation', 'am I saturated', 'branch', 'fork', 'explore alternative', 'team', 'add researcher', 'intercoder reliability', 'dashboard', 'show status', or after /qual-design completes."
---

> Script 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-design` completes
- When research_design changes in config

**Auto-invoked:**
- By `PostPhaseTransition` hook when sandwich_status changes
- By `project-setup` skill after design configuration

---

## What This Skill Does

1. **Reads research design** from `config.json`
2. **Generates Claude Code rules** in `.claude/rules/`
3. **Adapts rules** based on current phase
4. **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

```bash
node "${CLAUDE_PLUGIN_ROOT}/skills/methodological-rules/scripts/generate-rules.js" \
  --project-path /path/to/project
```

**What it does:**
- Reads `config.json` research_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

```bash
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

```bash
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

```bash
# 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

```bash
# 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

```bash
# 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

```bash
# 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

```bash
# 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

```bash
# 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: `PostPhaseTransition` triggers rule updates
- Config: Reads from `research_design` section
- Agents: `@dialogical-coder` references rules during coding
- Commands: `/qual-status` shows active rules

**With Claude Code:**
- Rules placed in `.claude/rules/` for auto-discovery
- Rules have no `paths` frontmatter, 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

```markdown
# .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 package (16)
  • SKILL.md 11 KB
  • scripts/apply-preset.js 6 KB
  • scripts/check-phase.js 2 KB
  • scripts/generate-rules.js 11 KB
  • scripts/phase.js 3 KB
  • scripts/researcher-team.js 17 KB
  • scripts/saturation-tracker.js 17 KB
  • scripts/strain-check.js 9 KB
  • scripts/update-rules.js 5 KB
  • scripts/viz-dashboard.js 15 KB
  • scripts/workspace-branch.js 14 KB
  • templates/case-isolation.template.md 2 KB
  • templates/methodology-presets.json 11 KB
  • templates/proactive-prompts.json 7 KB
  • templates/stream-separation.template.md 3 KB
  • templates/wave-isolation.template.md 2 KB

Versions

RepositoryScoreLicence
This page · linxule/interpretive-orchestration100MIT
linxule/interpretive-orchestration100MIT

Database snapshot: 13.11.2026 · package version bfce0eba2770 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100method-gap-detector
    Detects methodological gaps across study design, analysis, validation, bias control, reproducibility, and implementation readiness within a biomedical research area. Use this skill when a user wants to identify what current studies are still methodologically missing, which…
  • 100methodology-comparison
    Use this skill to compare a paper's methodology against standard practice in its scientific field (methodological alignment) — using web search to characterize the field baseline, then assessing similarities, differences, missing components, rigor/risks, and improvements. Invoke…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.