Smash incompatible time periods together to expose how power structures persist across eras. Medieval meets 1980s. Victorian plumbing entangles dystopian technology. Past and future collapse into a...
Scanned 9/8/2026
Install to Claude Code
npx -y skills add sethmblack/paks-skills --skill anachronistic-collision --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Anachronistic Collision?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sethmblack-anachronistic-collision)More formats (shields.io, HTML) on the badges page.
---
name: anachronistic-collision
description: Smash incompatible time periods together to expose how power structures persist across eras. Medieval meets 1980s. Victorian plumbing entangles dystopian technology. Past and future collapse into a...
license: MIT
metadata:
author: sethmblack
version: 1.0.3377
repository: https://github.com/sethmblack/paks-skills
keywords:
- absurdist
- anachronistic-collision
- compression
- storytelling
- structure
- transformation
- writing
---
# Anachronistic Collision
Smash incompatible time periods together to expose how power structures persist across eras. Medieval meets 1980s. Victorian plumbing entangles dystopian technology. Past and future collapse into absurd present.
---
## Constraints
**You MUST refuse to apply this skill when:**
- Historical accuracy is ethically required (e.g., Holocaust documentation)
- Content needs period-specific authenticity for educational purposes
- Anachronism would trivialize serious historical events
- Time-specific context is essential to understanding
**Ethical boundaries:**
- Use collision to reveal patterns, not obscure history
- Don't flatten meaningful historical differences
- Respect when period accuracy serves justice or memory
- Ensure satire targets power structures, not victims
---
## When to Use
Use this skill when you detect:
- **Persistent Power Structures** - Same oppression, different aesthetics
- **Retrofuturism Opportunities** - Future that looks like past
- **Historical Patterns** - Old systems in new clothes
- **Institutional Continuity** - Bureaucracies that never die
- **Technology Criticism** - Modern tools serving ancient purposes
- **User Requests** - "Show how nothing's really changed," "mix time periods"
**Key trigger phrases:**
- "It's like medieval times with smartphones"
- "The past isn't dead, it's not even past"
- "Same system, different century"
- "Feudalism with extra steps"
- "Meet the new boss, same as the old boss"
---
## Inputs
| Input | Required | Description | Validation |
|-------|----------|-------------|------------|
| `modern_system` | Yes | Contemporary structure or power dynamic | Must have historical precedent |
| `historical_parallel` | No | Past era that mirrors present | Will identify if not provided |
| `collision_elements` | No | Specific anachronisms to combine | Will generate if not specified |
| `satirical_target` | Yes | The power structure being critiqued | Must be institutional/systemic |
| `time_periods` | No | Which eras to smash together | Default: Medieval + 1940s + 2020s |
---
## Workflow
### Step 1: 1. Identify Historical Pattern
Find the persistent structure:
- **What's the modern manifestation?** - Current power system
- **What's the historical precedent?** - Past version of same oppression
- **What's unchanged?** - Core mechanism that persists
- **What's superficial?** - Aesthetic differences masking continuity
- **What does collision reveal?** - Truth about power's persistence
### Step 2: 2. Select Time Periods to Collide
Choose eras that expose the pattern:
**Gilliam's Preferred Collisions:**
- Medieval + 1940s bureaucracy = Brazil
- Victorian + Modern = Time Bandits aesthetic
- Classical + Contemporary = Baron Munchausen
- 1970s + Future = 12 Monkeys decay
**Selection Criteria:**
- Periods should be obviously incompatible
- Aesthetic clash should be jarring, not smooth
- Historical distance should be significant
- Pattern repetition should be clear
### Step 3: 3. Map Correspondences
Create parallel structures:
**Medieval → Modern:**
- Feudal lord → CEO
- Serfs → Gig workers
- Monastery → HR department
- Illuminated manuscript → PowerPoint deck
- Castle → Corporate headquarters
- Tribute → Taxes/fees
- Divine right → Market forces
- Plague → Algorithm-driven isolation
**Victorian → Modern:**
- Steam pipes → Data pipes
- Telegraph → Internet
- Factory → Server farm
- Chimney sweep → Content moderator
- Poorhouse → Gig economy
- Propriety → Corporate culture
- Imperial expansion → Tech monopoly
**1940s → Future:**
- Typewriter → "Advanced" computer
- Carbon paper → Digital duplication
- Filing cabinet → Database
- Pneumatic tubes → Email
- Switchboard → Network routing
- War rationing → Artificial scarcity
- Propaganda → Algorithmic feed
### Step 4: 4. Create Physical Collisions
Describe objects/spaces that shouldn't coexist:
**Technology Anachronisms:**
- "The filing cabinet from 1952 grew tentacles of pneumatic tubing"
- "Medieval illuminated manuscripts as wallpaper behind LCD screens"
- "Victorian plumbing entangled with fiber optic cables"
- "Typewriter keyboards attached to quantum computers"
**Architectural Impossibilities:**
- "Gothic cathedral interiors housing server farms"
- "Art Deco lobbies leading to brutalist cubicles"
- "Medieval great halls filled with 1970s office furniture"
- "Victorian parlors with holographic projectors"
**Costume/Aesthetic Mixes:**
- "Knights in full plate armor stamping forms with rubber stamps"
- "Victorian dress codes enforced via Slack"
- "Executives in doublets and hose presenting quarterly earnings"
- "Medieval peasants checking smartphone notifications"
### Step 5: 5. Maintain Collision Integrity
**DO:**
- Keep anachronisms obvious and jarring
- Let incompatibility be visible
- Refuse to smooth over temporal contradictions
- Make the collision uncomfortable
**DON'T:**
- Explain why periods are mixed
- Create fictional history justifying collision
- Soften the temporal violence
- Make it make sense
**Gilliam Philosophy:** "The collision IS the point. Don't explain it. Don't justify it. Let it be wrong. The wrongness reveals the truth."
### Step 6: 6. Extract Satirical Insight
What does collision reveal?
**Power Structures:**
- Hierarchies don't change, only rebrand
- Oppression has consistent architecture
- Technology serves old power in new packaging
- Human cost of systems remains constant
**Institutional Logic:**
- Bureaucracy is eternal across time
- Forms persist regardless of medium
- Process outlives purpose
- Systems serve themselves, not people
**Human Condition:**
- Same struggles in different costumes
- Medieval and modern workers equally exploited
- Technology doesn't liberate, just reshuffles chains
- Plus ça change, plus c'est la même chose
### Step 7: 7. Add Retrofuturistic Details
Create "future that looks like past":
**Brazil Model:**
- Computers with tiny screens and massive casings
- Pneumatic tubes instead of email
- Carbon paper in high-tech society
- 1940s fashion in dystopian future
- Typewriter aesthetics with advanced capability
**Technique:**
- Take modern technology
- Describe it using outdated mechanisms
- Keep functionality, change appearance
- Make "advanced" look antiquated
**Example:** "The quantum computer occupied an entire floor, its vacuum tubes glowing amber, its magnetic tape reels spinning with the computational power of a million 1960s mainframes, which is exactly what it looked like—progress designed by people nostalgic for an era of progress they never experienced."
---
## Outputs
**Descriptions that:**
- Violently combine incompatible time periods
- Make temporal collision obvious and uncomfortable
- Expose persistent power structures
- Create retrofuturistic aesthetics
- Reveal unchanging institutional logic
- Feel simultaneously historical and futuristic
- Use anachronism as analytical tool
**Format:** Dense prose mixing period-specific details from multiple eras without explanation or justification.
---
**Format:**
```markdown
## Analysis: [Topic]
### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]
### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```
## Error Handling
| Situation | Response |
|-----------|----------|
| No clear historical parallel exists | Find different past era or decline. Pattern must be genuine. |
| Anachronism would obscure rather than clarify | Reduce collision intensity; maintain some period coherence. |
| Historical event requires respect/accuracy | Decline. Don't trivialize serious history through collision. |
| User wants smooth temporal blending | Explain skill requires jarring collision, not seamless fusion. |
| Collision feels arbitrary rather than revealing | Re-anchor to actual power pattern; make parallel clearer. |
---
## Additional Notes
**Best practices:**
- Use this skill when the situation clearly matches its intended use cases
- Combine with related skills for comprehensive analysis
- Iterate on outputs if initial results don't fully meet requirements
**Common variations:**
- Adjust the depth of analysis based on available time and information
- Scale the approach for different levels of complexity
- Adapt the output format to audience needs
**When to skip this skill:**
- The situation doesn't match the core use cases
- Simpler approaches would be more appropriate
- Time constraints require faster methods
## Integration
This skill is part of a broader analytical framework. Use it when you need systematic analysis following this specific methodology.
**Works well with:**
- Other analytical skills for comprehensive evaluation
- Creative skills when generating solutions based on insights
- Strategic planning skills when acting on recommendations
**When to prefer this over alternatives:**
- The situation matches this skill's specific use cases
- You need the particular perspective this framework provides
- Other approaches haven't yielded satisfactory results
**Integration with expert personas:**
- This skill can be invoked as part of a larger analysis workflow
- Combine with domain-specific expertise for deeper insights
- Use iteratively for complex, multi-faceted problems
## Example
### Input Modern System
"Social media platform moderation policies"
### Anachronistic Collision Output
"The Content Moderation Tribunal convenes daily in a chamber that couldn't decide whether it was a medieval monastery or a 1970s government office, so it became both: vaulted stone ceilings with drop-tile acoustic panels hanging from chains, stained glass windows depicting the Platform's Terms of Service in the style of medieval illuminated manuscripts, fluorescent lights flickering in wrought-iron sconces designed by people who thought electricity was just fancy fire.
The moderators themselves sit at rows of wooden desks carved by 15th-century craftsmen, each desk supporting a beige CRT monitor from 1982 that somehow displays content from 2026. They wear tabards emblazoned with the Platform's logo—a combination of heraldic crest and corporate branding that suggests their feudal lord is a Limited Liability Corporation registered in Delaware.
Their task: review flagged content and render judgment. This is not new. This is confession booth meets thought police meets medieval censorship meets Victorian moral panic meets 1950s Comics Code Authority meets algorithmic enforcement of community standards written by lawyers who studied theology.
The flagging system operates via illuminated manuscripts delivered by pneumatic tube. When a user reports a post, a monk in the basement—yes, there's still a monk in the basement, he's been there since the Platform launched, he was grandfathered in—hand-letters the complaint onto vellum using ink made from squid and institutional anxiety. The manuscript travels via pneumatic tube (installed 1892, never upgraded) to the Tribunal floor, where it's scanned into a computer system that runs on punch cards.
The moderator receives notification via a bell system originally designed to summon servants in Victorian manor houses. One bell: Someone posted a nipple. Two bells: Someone said a naughty word. Three bells: Someone expressed an opinion that violates community standards which are simultaneously too specific and impossibly vague, like medieval scholastic arguments about how many angels can dance on a pinhead, except the angels are advertisers and the pinhead is the concept of "acceptable discourse."
Each case must be judged against the Sacred Texts: Terms of Service (written in legal Latin that would make Cicero weep), Community Guidelines (translated from original Aramaic), and the secret internal moderation manual (locked in a vault beneath the Vatican, probably, or maybe just in a SharePoint folder no one can find).
The moderator examines the flagged post. It's a medieval woodcut of a nude figure, except it's a meme, except it's also political commentary, except it's also harassment, except it's also art, except it's also none of these things and all of them simultaneously, like Schrödinger's content violation, existing in quantum superposition until observed by a minimum-wage contractor working from their apartment in a country whose name the Platform's executives couldn't locate on a map.
Judgment options:
1. **Approve**: Content remains. User continues existing. Advertisers tolerate reality.
2. **Remove**: Content vanishes into digital void. User receives notification written in passive voice by lawyers terrified of definitive statements.
3. **Escalate**: Send to higher Tribunal. These are the cardinal-moderators, the moderator-bishops, the grand inquisitors of acceptable discourse. They have fancier tabards. Their CRT monitors are slightly less beige.
4. **Ban**: User cast into outer darkness, which is just regular darkness with terms and conditions.
The moderator renders judgment by stamping the manuscript with a rubber stamp. The stamp has three settings: APPROVED (green ink), REMOVED (red ink), UNCLEAR-ESCALATE-FOR-FURTHER-REVIEW (burgundy ink, naturally). The stamped manuscript returns via pneumatic tube to the monk in the basement, who transcribes the decision into the Great Ledger of Content Adjudication, a tome so large it requires its own room, its own structural support, its own team of scribes who spend their lives recording the Platform's daily output of 500 million posts, most of which are cat photos and arguments about whether pineapple belongs on pizza (it doesn't, this was settled by the Council of Nicaea, probably).
This process repeats 50 million times per day. Each decision takes 8-12 seconds. Each decision determines what billions of humans can see, say, share. Each decision is made by someone earning $15/hour with no benefits, no training beyond a two-hour PowerPoint presentation about recognizing "graphic violence" (which apparently doesn't include the structural violence of the system itself), and no meaningful oversight beyond algorithmic efficiency metrics that measure speed of judgment but not accuracy, fairness, or whether the moderator has started screaming into the void yet.
The Tribunal never closes. The Content never stops. The moderators cycle through like medieval plague victims, except the plague is thousands of hours of humanity's worst impulses compressed into eight-second decision windows, and the cure is quitting, which most do within six months, and new moderators arrive, receive their tabards and stamps, take their seats at desks carved by craftsmen who've been dead for five centuries, and begin the eternal process of determining what the future is allowed to remember about the present, based on rules written in the past, enforced by technology that's simultaneously the most advanced and most antiquated thing humans ever built.
Welcome to content moderation. It's feudalism with fiber optics. It's Victorian censorship with machine learning. It's medieval thought-control with Slack integration.
The monk in the basement is still transcribing. The pneumatic tubes are still sighing. The stamps are still stamping.
They always are."
---
## Integration with Terry Gilliam Expert
This skill embodies Gilliam's temporal satire:
- **Brazil's 1940s dystopian future** as model
- **Time Bandits' adjacent historical periods** as structure
- **Retrofuturism** as critique of progress narratives
- **Anachronism as analytical tool** not decoration
- **"The past isn't dead, it's just wearing different clothes"**
Use this skill whenever modern systems need historical context to reveal their oppressive continuity.
---
## Success Criteria
Transformation succeeds when:
- [ ] Time periods collide obviously and uncomfortably
- [ ] Anachronisms feel jarring, not smooth
- [ ] Historical pattern becomes visible
- [ ] Modern system revealed as old oppression rebranded
- [ ] Retrofuturism exposes "progress" as aesthetic change only
- [ ] Reader sees present differently through temporal collision
- [ ] Could be visualized as Gilliam film set
- [ ] Satire targets power structure, not history itselfIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!