home-v1-skills-code-agent/corp-v1-channel-scope
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(scope): require borderless relationship links

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-19 10:04:00 +00:00
parent 26962d3c33
commit e66391ee65
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+4 -2
View File
@@ -1,7 +1,7 @@
---
name: corp-v1-channel-scope
description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all six same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
version: 1.3.5
version: 1.3.6
author: Hermes Agent
license: MIT
metadata:
@@ -133,7 +133,9 @@ Ideas are early opportunities not yet accepted as Epics or Features. Record stab
Questions are governed product decisions, separate from delivery status and approval. Keep a Questions parent page and one sidebar-visible child page per canonical Question. Show the question, why it matters, affected scope, owner, status, answer when available, and original source without using tables.
Render affected or resulting governed records as sharp clickable tags, sorted deterministically by entity type and canonical ID. Every governed record is a separate list item containing exactly one full-surface anchor to that record's canonical documentation URL; never combine multiple IDs or links into one visual tag, and never synthesize a URL from the ID. Give each tag its own visible border and spacing, pointer cursor, enabled pointer events, keyboard focus treatment, entity type, canonical ID, directional cue, and accessible label. Validate every generated Idea page by counting separate anchors, requiring one unique valid target per tag, and proving every target route exists. Label reader-facing source sections **Original source**, not Evidence. For Discord sources, render each link as `Discord – <Channel name> – <Author>` while retaining the exact source-message URL.
Render affected or resulting governed records as a borderless vertical list of ordinary links, sorted deterministically by entity type and canonical ID. Every governed record is a separate list row containing exactly one full-surface anchor to that record's canonical documentation URL; never combine multiple IDs or links into one visual item, synthesize a URL from the ID, or surround the relationship section/link with card or tag borders. Each link shows entity type, canonical ID, title, and a directional cue, with underlining, row spacing, pointer cursor, enabled pointer events, keyboard focus treatment, and an accessible label. Validate every generated Idea page by counting separate anchors, requiring one unique valid target per row, proving every target route exists, and checking deployed HTML and CSS together. Label reader-facing source sections **Original source**, not Evidence. For Discord sources, render each link as `Discord – <Channel name> – <Author>` while retaining the exact source-message URL.
Published stylesheet URLs must be derived from the actual CSS byte-content hash so changed reader CSS cannot reuse an immutable cached URL. Stage the complete Pages site, verify the staged stylesheet bytes and filename hash, and atomically replace the deployed directory; never publish by deleting the live directory and copying files into it incrementally.
The Epic registry graph must not expose a `View accessible data table` disclosure. Keep Epic nodes keyboard-accessible, labelled, and linked to canonical records; use the detailed Epic and Feature pages as the reader surface.