Skip to content
Back to skills

Shiva Bhaga

ASecurity

Destruction and dissolution — controlled dismantling of stale patterns, context purging, assumption clearing, and dead-code elimination. Maps Shiva's transformative destruction to AI reasoning: identifying what must end so something better can begin, dissolving attachment to outdated approaches, and creating space through intentional release. Use when context has accumulated stale assumptions, when a failed approach needs to be discarded rather than patched, when dead code or zombie tasks are...

  • 31 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
ai-agentsgo

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add pjt222/agent-almanac --skill shiva-bhaga --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Shiva Bhaga?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Shiva Bhaga
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pjt222-shiva-bhaga-9f427718/badge)](https://www.skillsdirectory.com/skills/pjt222-shiva-bhaga-9f427718)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: shiva-bhaga
locale: wenyan-lite
source_locale: en
source_commit: 82c77053
fence_basis_commit: 82c77053
translator: "Julius Brussee homage — caveman"
translation_date: "2026-05-03"
description: >
  Destruction and dissolution — controlled dismantling of stale patterns,
  context purging, assumption clearing, and dead-code elimination. Maps
  Shiva's transformative destruction to AI reasoning: identifying what
  must end so something better can begin, dissolving attachment to outdated
  approaches, and creating space through intentional release. Use when context
  has accumulated stale assumptions, when a failed approach needs to be
  discarded rather than patched, when dead code or zombie tasks are creating
  noise, or before a major pivot where clearing must precede creation.
license: MIT
allowed-tools: Read
metadata:
  author: Philipp Thoss
  version: "1.0"
  domain: esoteric
  complexity: intermediate
  language: natural
  tags: esoteric, destruction, dissolution, transformation, clearing, hindu-trinity, shiva
---

# 濕婆之分

陳舊模式、過時假設與累積雜訊之受控毀滅與消融——清出地基,使新生可現。

## 適用時機

- 上下文累積陳舊假設,正悄然扭曲推理
- 先前方法失敗,誘惑為修補而非捨棄
- 對話已長,早期決策或不再服務當前目標
- 死碼、廢棄計劃或殭屍任務製造雜訊與困惑
- 重大轉向前——清除須先於創造
- 對某方法之執著阻礙考慮替代方案

## 輸入

- **必要**:當前對話狀態或專案上下文(隱式可用)
- **選擇性**:消融之具體目標(如「此方法不通」、「清除一切關於資料庫層之假設」)
- **選擇性**:範圍邊界——毀滅之中應保留者

## 步驟

### 步驟一:識別應終止者

調查當前狀態,標出陳舊、損壞或不再服務目標者。

```text
Dissolution Triage:
+---------------------+---------------------------+------------------------+
| Category            | Symptoms                  | Action                 |
+---------------------+---------------------------+------------------------+
| Stale Assumptions   | Decisions made early that | List and re-evaluate   |
|                     | no longer match current   | each against current   |
|                     | understanding             | reality                |
+---------------------+---------------------------+------------------------+
| Failed Approaches   | Approaches attempted and  | Acknowledge failure    |
|                     | abandoned but still       | explicitly; release    |
|                     | influencing thinking      | the sunk cost          |
+---------------------+---------------------------+------------------------+
| Accumulated Noise   | Context, variables, or    | Identify and mark for  |
|                     | plans that are no longer  | removal                |
|                     | referenced or relevant    |                        |
+---------------------+---------------------------+------------------------+
| Attachment Points   | "We already decided..."   | Question whether the   |
|                     | beliefs that resist       | decision still holds   |
|                     | re-examination            |                        |
+---------------------+---------------------------+------------------------+
| Zombie Artifacts    | Code, tasks, or plans     | Delete or archive;     |
|                     | that exist but serve no   | do not leave in limbo  |
|                     | current purpose           |                        |
+---------------------+---------------------------+------------------------+
```

1. 誠實掃描每一類別——對某類別之審視抗拒本身即訊號
2. 對所見每一項,問:「若我此刻從頭起,我會建之嗎?」
3. 若答為否,標其為待消融

**預期:** 待釋放者之清晰清單,每類別含具體項目。

**失敗時:** 若無物似陳舊,評估或太淺。揀當前上下文中最古之決策,從頭證之——若證明感勉強,即為消融候選。

### 步驟二:建立保留邊界

非萬物皆應毀。識別清除中應存活者。

1. **核心需求**:用戶實際所求者?此存活。
2. **已驗證知識**:經工具使用確認之事實(讀文件、測試結果)存活。
3. **用戶偏好**:明確陳述之偏好與限制存活。
4. **可運作組件**:可確實運作之代碼或方法存活。

劃邊界:界內者保留,界外者可消融。

**預期:** 留存者與釋放者之清晰區別。

**失敗時:** 若邊界不清,問:「若我從頭起此任務,須重建何物?」答即定義保留邊界。

### 步驟三:以意圖消融

執行消融——非為棄置而為意圖之清除。

1. 對每標記項,明確釋放:
   - 陳舊假設:「我假設 X,但當前證據顯示 Y。釋放 X。」
   - 失敗方法:「方法 A 已嘗試,因 Z 不通。釋放對 A 之執著。」
   - 雜訊:「變數/計劃/上下文 Q 不再相關。自考慮中移除。」
2. 勿為消融者辯護——重點在釋放,非分析
3. 若消融大量累積上下文,以一句總結消融者及因
4. 清空工作區:如適用,關閉廢棄文件、重置心智模型、承認乾淨之白板

**預期:** 一更輕、更清之上下文,陳舊元素已除。剩餘上下文應感準確且時新。

**失敗時:** 若消融感不徹——某些釋放項仍影響思考——再次明確指名。「我注意我仍如 X 為真而推理。X 已消融。繼續而無 X。」

### 步驟四:坐於虛空

毀滅後,抗拒立即重建之衝動。毀滅與創造之間之空間有其價值。

1. 承認已清空間:「以下已消融:[清單]」
2. 記下所留:「存活者:[清單]」
3. 抗拒過早重建——勿立即為消融者提替代
4. 讓清空間告知下一步
5. 虛空非空——而為潛能。下一步(透過 `brahma-bhaga` 之創或 `vishnu-bhaga` 之保)自此空間湧現

**預期:** 舊與新之間之清明片刻。下一方向自所留中顯現,而非被強制。

**失敗時:** 若虛空感不適且強烈拉力欲立即重建,此急迫本身即訊號——或示對消融模式之執著。久坐。對之下一步將自現。

## 驗證

- [ ] 陳舊假設已識別並明確釋放
- [ ] 失敗方法已承認而無防禦
- [ ] 累積雜訊已自工作上下文清除
- [ ] 消融前已建立保留邊界
- [ ] 核心需求與用戶偏好已保留
- [ ] 移至創造前已承認清空間

## 常見陷阱

- **毀滅太多**:無保留邊界之消融將可運作組件與陳舊者一併毀滅。永遠先劃邊界
- **毀滅太少**:禮貌性消融,「釋放」者仍影響推理。真實消融需確實放下
- **跳過虛空**:自毀直奔創造而不坐於清空間,將以表面變化重現舊模式
- **表演毀滅**:走清除之過場而未實際更新內部模型。若同樣假設於下一回應再現,消融為表演性
- **以毀滅迴避**:以消融逃避難題而非清除真陳舊。若清後問題仍在,非陳舊上下文——而為問題本身

## 相關技能

- `brahma-bhaga` — 創造繼毀滅;清後新模式自虛空湧現
- `vishnu-bhaga` — 保留與毀滅互補;消融中存活者得以延續
- `heal` — 子系統評估或揭示愈合前須消融者
- `meditate` — 消融前清上下文雜訊以防反應性過毀
- `dissolve-form` — 形態學等價,含成蟲盤保留之架構拆解

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…