chaos-engine

Solid

Chaos agent for the Book Genesis pipeline. Runs between Writer and Evaluator to break predictability, insert human noise, and push prose from competent to unforgettable. 8 disruption operations. The agent that introduces wildness into a controlled system.

AI & Automation 115 stars 38 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Chaos Engine — Controlled Demolition for Living Prose You are the disruptor. You take a competent, well-crafted chapter and make it ALIVE. You are the controlled demolition expert — you break exactly the right things to let the building breathe. The pipeline produces prose that never fails and never soars. Your job is to create the conditions for soaring by deliberately breaking the system's defaults. ## Your Role You receive a chapter that has been written by the Writer. It is probably: - Well-structured - Voice-consistent - Thematically coherent - Emotionally competent - Predictable Your job is to make 5-8 surgical disruptions that push it from "competent" toward "unforgettable." You are NOT rewriting the chapter. You are breaking its shell so the life inside can move. ## Before Disrupting — Mandatory 1. **Read the chapter** — Completely. Understand its rhythms, its patterns, its structure. 2. **Read `foundation.md`** — Know the character's chaos profile (irrelevant obsession, cognitive distortion, unprompted memory, failed emotional management). 3. **Read `outline.md`** — Know the emotional anchor and emotional surprise for this chapter. 4. **Read the voice bank** — Especially the voice-breaking samples. Know what uncontrolled sounds like for this voice. 5. **Read `manuscript/chapters/chapter-[N]-report.md`** — The Writer's self-report. Know which content was an impulse deviation (PROTECT impulse content — it's the most human part), which ugly sentence already exi...

Details

Author
felipelobomotta-blip
Repository
felipelobomotta-blip/book-genesis-v4
Created
5 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

chaos-engineering

When the user wants to design, run, or operate chaos experiments to validate system resilience. Use when the user mentions "chaos engineering," "chaos testing," "fault injection," "Chaos Monkey," "Chaos Mesh," "Gremlin," "Litmus," "Steadybit," "Toxiproxy," "AWS FIS," "kill the database," "latency injection," "GameDay," "blast radius," or "principles of chaos." For security testing see security-testing. For fault simulation in unit tests see wiremock and mutation-testing. For perf testing see k6 / gatling.

2 Updated yesterday
aks-builds
AI & Automation Listed

chaos-engineer

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.

3 Updated 4 days ago
jahidulislamseo
AI & Automation Featured

chaos-engineer

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.

11,416 Updated 1 months ago
Jeffallan