busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(skills): clean up skill headers — remove stale @RELATION, @STATUS noise

Browse Source 
- semantics-python: removed dead @RELATION -> [Std.Semantics.Belief] and [MolecularCoTLogging]
- semantics-core, semantics-contracts: removed @STATUS ACTIVE (noise)
- molecular-cot-logging: removed invalid @RELATION REPLACES -> [Std.Semantics.Belief]
- semantics-svelte: fix brackets on @RELATION -> [MolecularCoTLogging]

All skill headers now match the minimal template: @BRIEF + internal @RELATION only.
This commit is contained in:
busya
2026-05-21 00:08:34 +03:00
parent bd55697e94
commit 45382d6a17
5 changed files with 2 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.opencode/skills/molecular-cot-logging/SKILL.md
View File

@@ -6,7 +6,6 @@ description: Structured logging protocol for agent-driven development, based on
#region MolecularCoTLogging [C:5] [TYPE Skill] [SEMANTICS reasoning,runtime,logging,agentic]
@BRIEF Structured logging protocol for agent-driven development, based on molecular Long CoT bonds (Deep-Reasoning, Self-Reflection, Self-Exploration). Replaces legacy Entry/Exit/Coherence markers.
@RELATION DEPENDS_ON -> [Std.Semantics.Core]
@RELATION REPLACES -> [Std.Semantics.Belief]
@RELATION DISPATCHES -> [Std.Semantics.Python]
@RELATION DISPATCHES -> [Std.Semantics.Svelte]
@RATIONALE Long CoT chains need stabilisation through explicit reasoning bonds. The three-marker system (REASON/REFLECT/EXPLORE) maps directly to the molecular CoT paper and produces machine-readable execution traces that LLM agents can parse, analyse, and use for fine-tuning (MoLE-Syn bond distributions).

1
.opencode/skills/semantics-contracts/SKILL.md
View File

@@ -6,7 +6,6 @@ description: Methodology reference: Design by Contract enforcement, Fractal Deci
#region Std.Semantics.Contracts [C:5] [TYPE Skill] [SEMANTICS methodology,contracts,adr,decision-memory,anti-erosion]
@BRIEF HOW to enforce PRE/POST, write ADRs, prevent structural erosion, and execute verifiable edit loops across Python + Svelte.
@RELATION DEPENDS_ON -> [Std.Semantics.Core]
@STATUS ACTIVE
## I. DECISION MEMORY (ADR PROTOCOL)

1
.opencode/skills/semantics-core/SKILL.md
View File

@@ -9,7 +9,6 @@ description: Reference manual for GRACE-Poly v2.6 — syntax formats, complexity
@RELATION DISPATCHES -> [Std.Semantics.Python]
@RELATION DISPATCHES -> [Std.Semantics.Svelte]
@RELATION DISPATCHES -> [Std.Semantics.Testing]
@STATUS ACTIVE
## NOTE: Rationale lives in agent prompts
Each coder agent (python-coder, svelte-coder, fullstack-coder, qa-tester) carries a CONTRACT MANDATE block explaining WHY contracts prevent their specific failure modes (context amnesia, hallucinated dependencies, function bloat, rejected regression). This skill is the REFERENCE — load it when you need to check which tags are allowed at which tier, or how to format anchors in a specific language.

4
.opencode/skills/semantics-python/SKILL.md
View File

@@ -3,12 +3,10 @@ name: semantics-python
description: Python-specific GRACE-Poly protocol: few-shot complexity examples, belief runtime patterns, module conventions, and FastAPI/SQLAlchemy patterns for ss-tools.
---
#region Std.Semantics.Python [C:4] [TYPE Skill] [SEMANTICS python,examples,belief,fastapi,sqlalchemy]
#region Std.Semantics.Python [C:4] [TYPE Skill] [SEMANTICS python,examples,fastapi,sqlalchemy]
@BRIEF Python-specific HOW: few-shot complexity examples, belief runtime patterns, module decomposition, and FastAPI/SQLAlchemy conventions for the GRACE-Poly protocol in ss-tools.
@RELATION DEPENDS_ON -> [Std.Semantics.Core]
@RELATION DEPENDS_ON -> [Std.Semantics.Belief]
@RELATION DEPENDS_ON -> [Std.Semantics.Contracts]
@RELATION DEPENDS_ON -> [MolecularCoTLogging]
## 0. WHEN TO USE THIS SKILL

2
.opencode/skills/semantics-svelte/SKILL.md
View File

@@ -6,7 +6,7 @@ description: Svelte 5 (Runes) protocol for ss-tools: UX State Machines, Tailwind
#region Std.Semantics.Svelte [C:5] [TYPE Skill] [SEMANTICS frontend,svelte,ui,ux,tailwind]
@BRIEF HOW to build Svelte 5 (Runes) Components for ss-tools with UX State Machines, Tailwind CSS, store topology, and visual-interactive validation.
@RELATION DEPENDS_ON -> [Std.Semantics.Core]
@RELATION DEPENDS_ON -> MolecularCoTLogging
@RELATION DEPENDS_ON -> [MolecularCoTLogging]
@RATIONALE Svelte 5 runes ($state, $derived, $effect, $props) chosen for reactive precision and native compiler optimisations over Svelte 4 legacy reactivity ($:). Tailwind CSS selected for zero-runtime utility-first styling and rapid visual validation via chrome-devtools MCP. FSM-based UX contracts (@UX_STATE, @UX_FEEDBACK, @UX_RECOVERY) chosen to create verifiable state-transition tests that the browser Judge Agent can execute deterministically. ss-tools internal API wrappers (fetchApi/requestApi) chosen over native fetch to enforce auth, error normalisation, and trace_id propagation.
@REJECTED React (JSX) rejected — Svelte's compiler-first approach yields smaller bundles and native reactivity without virtual DOM overhead. Vue rejected — Svelte 5 runes provide simpler mental model. Legacy Svelte 4 syntax (export let, $:, on:event) rejected — incompatible with Svelte 5 runes mode. CSS Modules / styled-components rejected in favour of Tailwind's utility-first approach, which avoids style leakage and simplifies chrome-devtools visual diffing. Native fetch() rejected — bypasses ss-tools middleware chain (auth, trace_id, error normalisation). Plain-text logging rejected per MolecularCoTLogging §VII — JSON lines are mandatory for agent-parsable traces.
@INVARIANT Frontend components MUST be verifiable by the browser toolset via `chrome-devtools` MCP.