Skip to content

Latest commit

 

History

History
63 lines (45 loc) · 2.33 KB

File metadata and controls

63 lines (45 loc) · 2.33 KB

Contributing to the ALIVE Context System

Thanks for your interest in contributing. The ALIVE Context System is open source and we welcome contributions -- bug fixes, new skills, documentation, and ideas.

Getting Started

  1. Fork the repository
  2. Clone your fork locally
  3. Install the plugin from your local copy for testing:
    claude plugin install /path/to/your/clone

Project Structure

plugins/alive/
  skills/         15 skill folders, each with a SKILL.md
  rules/          6 rule files defining caretaker behavior
  hooks/          hooks.json + scripts/ for session lifecycle
  templates/      file templates for walnuts, bundles, manifests
  onboarding/     first-run experience
  statusline/     terminal status bar integration
  scripts/        utility scripts (world index, context graph)
  CLAUDE.md       the core runtime definition

Making Changes

Skills

Each skill lives in plugins/alive/skills/{name}/SKILL.md. Skills define what the squirrel can do -- invoked via /alive:{name}.

Rules

Rules live in plugins/alive/rules/. They define how the squirrel behaves -- always loaded, always followed.

Hooks

Hook scripts live in plugins/alive/hooks/scripts/. They fire on session lifecycle events and tool use events. Registry: plugins/alive/hooks/hooks.json.

Templates

Templates in plugins/alive/templates/ define the schema for system files. The squirrel reads these before writing any system file.

Guidelines

  • Read before writing. Understand the existing code before modifying it.
  • Frontmatter on everything. Every .md file has YAML frontmatter. No exceptions.
  • Don't break backward compatibility. Existing walnuts must keep working.
  • Test with a real world. Create a test walnut and exercise your changes.
  • Keep skills focused. One skill, one purpose.
  • Cross-platform. Hooks must work on Mac, Linux, and Windows (Git Bash). No hardcoded Unicode in hook script strings. Use platform detection from alive-common.sh.

Pull Requests

  • Keep PRs focused on a single change
  • Describe what changed and why
  • Reference any related issues

Reporting Issues

Use GitHub Issues for bugs and feature requests.

License

By contributing, you agree that your contributions will be licensed under the MIT License.