# Contributing

This is an unofficial contribution candidate, not official OpenClaw guidance.

1. Define one real user need and the surface where it occurs.
2. Preserve the approved logo SVG paths and fixed wordmark spacing.
3. Prefer semantic tokens and existing accessible primitives.
4. Include before/after screenshots, keyboard and mobile evidence, and an explanation of the behavior change.
5. Record source and licence for new assets. Keep future concepts clearly labelled.
6. Propose focused adoption to upstream maintainers through their published contribution process. This site does not send a contribution or claim upstream approval.

## Review gates

- Accurate task, input and connection states; no fabricated completion.
- Concrete approval with target, content and cancellation.
- Usable keyboard focus, 320px reflow, 200% text, both themes and reduced motion.
- Correct typography at real size; fallback scripts remain readable.
- Test voice capture, interruption and device handoff with real implementations before describing them as supported behavior.
- Family feedback on the character and actual native-device validation before wider adoption.

## Develop

Use Node 22.13+ and Python 3. Run npm ci and npm run dev. Before release: npm run resources; npm run check; npm run build. Start one production preview with npm run preview, then run npm run verify:site against its URL. See MAINTAINER-GUIDE.md for full-resource hash checks and adoption details.

Font files, measurements, proof evidence and editable sources must be updated together. Current guides and resource indexes are generated from root documents. Keep original art, historical references and rollback history recoverable. Never add credentials, local runtime state or environment files to public downloads.