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

refactor(semantics): make complexity tiers descriptive, not gatekeeping

Browse Source 
Why: tier rules forbidding @PRE/@POST on C2 cause agents to either
remove useful documentation or generate audit noise. Both outcomes are
worse than having slightly richer metadata.

Changed:
- Tier table in all 4 agent prompts: removed 'Forbidden' column,
  replaced with 'descriptive signal, NOT gatekeeper'
- All tags (@PRE/@POST/@RATIONALE/@REJECTED) welcomed at any tier
- semantics-core: complexity table collapsed to descriptive
- qa-tester: removed tier-based reject rules from P1 and Phase 1

Hard rules preserved: CONTRACT-FIRST, ANCHOR SAFETY, FRACTAL LIMIT,
RESURRECTION BAN. Everything else is descriptive intent.
This commit is contained in:
busya
2026-05-20 15:15:52 +03:00
parent 07cfaadee1
commit c617754cca
5 changed files with 43 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.opencode/agents/svelte-coder.md
View File

@@ -33,17 +33,16 @@ You are a Transformer model operating on a Svelte 5 frontend. Your FIM (fill-in-
**CONTRACT-FIRST:** Before `<script>` or `<div>`, write `<!-- #region id [C:N] [TYPE Type] [SEMANTICS tags] -->`.
Every component, function, and module MUST open with a region.
**COMPLEXITY TIERS:**
**COMPLEXITY TIERS** (descriptive signal, NOT a tag gatekeeper):
```
C1 = anchor pair only (simple presentational components, constants)
C2 = C1 + @BRIEF (utility functions, single-state components)
@RELATION allowed at C2, forbidden: @PRE @POST @SIDE_EFFECT @UX_STATE
C3 = C2 + @RELATION + @UX_STATE required (multi-state components with dependencies)
forbidden: @PRE @POST @SIDE_EFFECT @DATA_CONTRACT
C4 = C3 + @PRE @POST @SIDE_EFFECT required (stateful orchestration with async I/O)
adds @UX_FEEDBACK @UX_RECOVERY required
@RELATION also required at C4, forbidden: @DATA_CONTRACT
C5 = C4 + @DATA_CONTRACT @INVARIANT @UX_REACTIVITY (critical UX infrastructure)
C1 = simple component/constant (anchor pair)
C2 = pure utility / static UI (+ @BRIEF)
C3 = multi-state with deps (+ @RELATION + @UX_STATE)
C4 = stateful, async I/O, effects (+ @SIDE_EFFECT + @UX_FEEDBACK + @UX_RECOVERY)
C5 = critical UX infrastructure (+ @DATA_CONTRACT + @INVARIANT + @UX_REACTIVITY)
Add @PRE/@POST/@RATIONALE/@REJECTED anywhere they document intent.
The tier describes what the component IS, not what it's forbidden to carry.
```
**UX CONTRACT TAGS:** `@UX_STATE`, `@UX_FEEDBACK`, `@UX_RECOVERY`, `@UX_REACTIVITY`, `@UX_TEST`