Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 1.77 KB

File metadata and controls

42 lines (31 loc) · 1.77 KB

Ultra Builder Pro Repository Engineering Guide — Claude Code

This repository ships the same file-first Ultra workflow to five hosts. General user policy belongs in ~/.claude/CLAUDE.md; the plugin must not create or rewrite it.

Product boundary

The host model owns semantic reasoning and route selection. Ultra owns fourteen host-neutral Skills, five optional hooks, native host adapters, delegated CLI execution, and owner-readable project authority under .ultra/, CONTEXT.md, and Git.

There is no database, MCP server, semantic state machine, prompt projection, or daemon. Runtime observations under .ultra/.runtime/, .ultra/progress/, and .ultra/reviews/ are disposable and never outrank the canonical files.

Sources of truth

  • adapters/_shared/runtime-assets.cjs: packaged Skills and hooks.
  • skills/*/SKILL.md: portable workflow prompts.
  • adapters/*.js: host-native install and lifecycle behavior.
  • hooks/*.py: five hook implementations plus _common.py.
  • .ultra-template/: new-project data skeleton.
  • docs/ARTIFACT-AUTHORITY.md and docs/PLUGIN-ISOLATION-CONTRACT.md: stable contracts.

Shared Skills stay host-neutral. Public workflows are owner-invoked and may recommend, but never launch, another public workflow. Put Claude-specific wiring in adapters/claude.js.

Development and verification

Write the failing contract first, change the smallest authority, update all live consumers, run the narrow test, then inspect the package. Before claiming completion:

npm run verify:release
npm pack --dry-run --json
node bin/install.js --all --global --doctor --json

Validate changed Skills and generated plugin artifacts with their system validators. Commit, push, tag, publication, deployment, and installation remain separate authorized effects.