Skip to content

Latest commit

 

History

History
35 lines (27 loc) · 1.37 KB

File metadata and controls

35 lines (27 loc) · 1.37 KB

Repository Guidelines

Scope

Carapace owns the canonical OpenClaw web design contract:

  • framework-neutral CSS tokens and themes
  • a thin Tailwind 4 token adapter
  • shared base behavior proven across consumers
  • agent skills that explain how to use and audit the system

Consumer-specific components, routes, and layouts stay in their repositories until at least two consumers share the same interface and behavior.

Commands

  • Bun 1.3.0 is the supported minimum; use the exact packageManager pin for normal development and release work.
  • bun install --frozen-lockfile - install the committed dependency graph.
  • bun run test - parse CSS and verify token/theme contracts.
  • bun run skills:check - validate skill metadata and references.
  • bun run pack:check - verify package exports and packed contents.
  • bun run check - run all validation.
  • Keep the 48-hour dependency maturity window in bunfig.toml; add exclusions only for a named, reviewed dependency.
  • Use mutable bun install only for deliberate dependency changes, and review bun.lock as a security-sensitive generated artifact.

Release

  • Use Conventional Commits.
  • Release tags are stable semantic versions: vX.Y.Z.
  • The tag must match package.json.
  • Runtime assets release under semantic tags; agent skills update from main.
  • npm publication is not required; consumers install the Git tag.