synapse

Name: synapse
Availability: InStock
Author: elevaria-bia

Manage and troubleshoot the SYNAPSE context engine with an 8-layer pipeline.

Updated May 8, 2026

Search Tags:#debugging #domain management #synapse #context engine #prompt injection rules #context brackets #star-commands

Ready to run

npx skills add https://github.com/Elevaria-bia/elevaria-bia.github.io --skill synapse-elevaria-bia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: synapse
Source: https://github.com/Elevaria-bia/elevaria-bia.github.io/tree/main/meu-projeto/.claude/skills/synapse
Command: npx skills add https://github.com/Elevaria-bia/elevaria-bia.github.io --skill synapse-elevaria-bia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

SYNAPSE helps you understand, manage, and troubleshoot the context injection system that adapts what the AI sees per prompt using an 8-layer pipeline and bracket-aware rule filtering.

Core Features & Use Cases

Explain SYNAPSE architecture and how rules inject into prompts with an 8-layer processing pipeline (L0–L7) that outputs a <synapse-rules> block.
Manage domains and context rules by listing, creating, toggling, editing, and adding domain rules tied to layers and triggers.
Troubleshoot rule injection and activation by checking engine state, debug details, bracket behavior (FRESH/MODERATE/DEPLETED/CRITICAL), and loaded domain summaries.

Quick Start

Ask the assistant to run the command *synapse debug to inspect manifest parsing, domain load results, bracket state, and rule counts for the current session.

Frequently Asked Questions about synapse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug context rules that are not injecting into my prompts correctly?▼

To debug context rule injection failures, run the `*synapse debug` command to inspect manifest parsing, domain load results, context brackets, and rule counts. This diagnostic reveals why specific layers or rules did or did not activate during the 8-layer pipeline processing.

What are context brackets and how do they affect domain trigger activation?▼

Context brackets are tracked states (FRESH, MODERATE, DEPLETED, CRITICAL) that determine how domain triggers activate within the context engine. They influence which bracket-aware rules are injected into the `<synapse-rules>` XML block for each prompt.

How does the 8-layer processing pipeline format injected prompt rules?▼

The 8-layer processing pipeline (L0–L7) formats injected rules by reading domain files from the manifest, applying bracket-aware filtering, and outputting a `<synapse-rules>` XML block. This structure ensures the AI receives the correct domain-specific rules per prompt.

Can I manage domain CRUD operations and star-command configurations without external dependencies?▼

Yes, you can manage domain creation, listing, toggling, and editing along with star-command configurations directly through the context engine. It supports operational commands like status, domains, debug, and reload without requiring external dependencies.

Why does my domain file load but fail to trigger rules during a session?▼

Domain files may load successfully but fail to trigger rules due to context bracket states or layer misconfiguration. Use the `*synapse debug` command to inspect loaded domain summaries, verify trigger conditions, and check why specific pipeline layers did not activate.

What is the best way to reload domains and check engine status after editing context rules?▼

The best way to reload domains and check engine status after editing context rules is to use operational commands like `*synapse reload` to refresh the manifest and `*synapse status` to verify the current context bracket states and active rule counts.