Starlight-Intelligence-System / hooks
CLAUDE.md10 starsChanged 2 months agoMITView on GitHub
Portable / multi-harness hooks system (claude/codex/gemini/agy/grok). Source it: source "$(dirname "$0")/lib/hook-env.sh" Override: export AI_GLOBAL_SESSIONS=/path/to/log.md God 99. Use gstack for UI verification.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Arcanea-Labs/Starlight-Intelligence-Systemword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Arcanea-Labs/Starlight-Intelligence-System★ 10100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- site/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/editorial.mdcCursor rule
- .cursor/rules/starlight-agents.mdcCursor rule
- .cursor/rules/starlight-core.mdcCursor rule
- .cursor/rules/starlight-memory.mdcCursor rule
- .cursor/rules/starlight-voice.mdcCursor rule
- frank-brand-editorSkill
- agent-hygieneSkill
- estate-guardSkill
- SKILL.mdSkill
- crypto-intelligenceSkill
- agent-forgeSkill
- skill-forgeSkill
- system-forgeSkill
- taste-engineSkill
- integration/ecosystem-syncSkill
- integration/repo-bridgeSkill
- integration/transmission-protocolSkill
- integration/universal-adapterSkill
- intelligence/decision-frameworkSkill
- intelligence/hermes-searchSkill
- intelligence/pattern-recognitionSkill
- intelligence/strategic-reasoningSkill
- intelligence/systems-thinkingSkill
- heartSkill
- storageSkill
- memory/capture-disciplineSkill
- memory/context-preservationSkill
- memory/insight-distillationSkill
- memory/knowledge-synthesisSkill
- memory/memory-consolidationSkill
- sis-memory-orchestratorSkill
- memory/vault-managementSkill
- agent-creatorSkill
- orchestration/context-engineeringSkill
- orchestration/gencreator-stackSkill
- orchestration/hermes-swarmSkill
- orchestration/multi-agent-coordinationSkill
- orchestration/parallel-executionSkill
- orchestration/workflow-designSkill
- workflow-skill-creatorSkill
- safety/mutation-approvalSkill
- safety/permission-gateSkill
- safety/private-public-splitSkill
- safety/secret-detectorSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 56
All hooks call log_hook_activation which invokes excellence-hook.sh (Frank DNA, read CLAUDE/AGENTS, verification/santa/qa/cso gates, …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code Hooks Configuration (Upgraded)
Portable / multi-harness hooks system (claude/codex/gemini/agy/grok).
lib/hook-env.sh
Central portable env:
detect_harness()→ HARNESS=claude|codex|gemini|agy|grok|unknown- Portable PROJECT_ROOT (git/env/cwd), AI_SESSIONS_LOG (auto WSL /mnt/c or $HOME/docs)
- GLOBAL_*_DIR per-harness (with .claude compat)
log_hook_activation,handle_precompact,handle_notification- Excellence wiring (calls excellence-hook.sh)
Source it: source "$(dirname "$0")/lib/hook-env.sh"
Available Hooks (agnostic + ACOS ports)
| Hook | Purpose | Trigger(s) | Notes |
| session-logger.sh | Global sessions to AI_GLOBAL_SESSIONS.md | UserPromptSubmit | Uses $AI_SESSIONS_LOG + $HARNESS |
| skill-activation-prompt.sh | Auto skill/agent activation from rules | UserPromptSubmit | Updated paths via env; .js/.ts |
| file-link-tracker.sh | Track edits to ~/LINKS_TODAY.md + github links | PostToolUse | Json+env input, portable open on WSL |
| pre-commit.sh | Lint staged (eslint/prettier) + quality | Pre-commit / manual | Wires quality-gate |
| pre-compact.sh | PreCompact stub + delegate to gsd/ACOS | PreCompact | |
| notification.sh | Notification stub | Notification | |
| quality-gate.sh | ACOS ported quality (biome/prettier/gofmt/ruff) | Pre/PostToolUse (Edit) | Shim + .js |
| gsd-*.sh (context-monitor, workflow-guard, statusline) | ACOS GSD context/guard/status | PostToolUse/Status | Shims + .js |
| mcp-health-check.sh | ACOS MCP health | PostToolUse | Shim |
| excellence-hook.sh | Wires Frank DNA, gates, gstack note | Any (internal) | Called by env |
Global Log Location (portable)
AI_GLOBAL_SESSIONS env or auto:
- WSL:
/mnt/c/Users/$WINUSER/docs/AI_GLOBAL_SESSIONS.md - Else:
$HOME/docs/AI_GLOBAL_SESSIONS.md
Override: export AI_GLOBAL_SESSIONS=/path/to/log.md
Multi-Harness Support
- Detection prioritizes runtime env vars then dirs/cmds.
- .claude/ paths used as compat layer for skills/hooks across harnesses.
- For Grok: also seed .grok/hooks/ + GROK.md (see ACOS install).
- Register in
~/.claude/settings.json(or equiv .grok / .codex config).
Settings Example (excerpt)
See claude-code-hooks/settings-example.json for full with PreCompact/Notification + ACOS ports.
Usage
# Manual
~/.claude/hooks/session-logger.sh
# Install portable to project
cd claude-code-hooks && ./install.sh --portableExcellence
All hooks call log_hook_activation which invokes excellence-hook.sh (Frank DNA, read CLAUDE/AGENTS, verification/santa/qa/cso gates, repo-mastery, gstack for any UI).
God 99. Use gstack for UI verification.
Updated 2026-06-02 via hook upgrade task.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

