ecc-instincts

Registers ten L2 atomic instincts mapped to SUPREME rules and dispatch contracts.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill ecc-instincts-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-instincts
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/ecc-instincts
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill ecc-instincts-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a single source of truth for the ECC learning system's ten L2 atomic instincts, preventing redundant dispatcher implementations and schema drift when implementing ecc-07 through ecc-12 dev stories. ## Core Features & Use Cases - Instinct Registry: Maps 10 instincts (skill_invocation, hook_dispatch, cross_ref, depth_first, governance, parallel_isolation, capability_integration, pipeline_handshake, mcp_payload, encoding_discipline) to their SUPREME rules, state files, and responsible stories. - Contract Alignment: Enforces the IInstinctDispatcher input/output schema from ecc-haiku-dispatch so dispatchers never invent their own schemas. - Evolve Recommendation Layer: Governs track-alpha L2-to-L3 evolve candidate detection, HITL generation discipline, and candidate rejection governance with strict no-auto-write rules. - Use Case: Before implementing the ecc-08 dev story, consult this registry to confirm the hook_dispatch and cross_ref instinct mappings, check existing hook coverage, and avoid rebuilding already-aligned observation layers. ## Quick Start Ask the AI to look up the instinct registry mapping and existing hook alignment before implementing any ecc-07 through ecc-12 dispatcher story.

Frequently Asked Questions about ecc-instincts

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

FAQPage Schema
How do I implement an L2 instinct dispatcher for ecc-07 through ecc-12?

First read the instinct registry table to confirm the instinct-to-SUPREME-rule mapping and state file path, then glob existing hooks for prior alignment. Implement dispatchers against the ecc-haiku-dispatch IInstinctDispatcher contract rather than inventing new schemas.

What is the difference between track alpha and track beta instincts?

Track beta covers the ten SUPREME rule dispatchers writing state to .context-db/ecc-state JSON files. Track alpha is the dynamically emerged instincts table with confidence and decay scoring, whose schema was frozen and is orthogonal to track beta.

Can the evolve recommendation layer automatically generate new skills or hooks?

No. Automatic generation is strictly forbidden. The evolve layer only detects mature candidates read-only and displays them in the UI; users must manually invoke the Skill tool, and rejection governance only marks existing instincts as rejected.

Why should I not build a new dispatcher script for ecc-11 or ecc-12?

Those stories were finalized as evidence-only because existing rules and hooks already cover 60-95% of each instinct. Building new dispatchers would duplicate existing guards and create zombie mechanisms, violating the no-redundant-build discipline.

What input and output schema must an instinct dispatcher follow?

Dispatchers must accept instinct_name, payload, and timestamp, and return status, result, state_diff, and evidence fields as defined in the instinct-dispatch schema from ecc-haiku-dispatch. Custom schemas are forbidden.