Find the best CLAUDE.md, AGENTS.md and Claude skills

autonomous-aiAGENTS.md

openharness

autonomous-ai/openharness/AGENTS.md

Follow CONTRIBUTING.md and the component's instructions. For validation and shipping, use docs/validation-and-release.md. For product names, terminology, and visible copy, follow the Naming System. - Measure the user's request through completion. Record implementation, validation, merge, publication, and waiting separately; an Actions duration is not the total. - Choose the necessary checks before starting them. Run affected tests and relevant integration checks; use full suites for broad changes. Start independent checks together within the machine's capacity. Do not add a second full…

No other project uses it yet

autonomous-aiCLAUDE.md

openharness

autonomous-ai/openharness/CLAUDE.md

No summary in the file. Open it to read it.

autonomous-aiAGENTS.md

openharness / cli

autonomous-ai/openharness/cli/AGENTS.md

Read this before changing anything under cli/. The repository-wide process rules (validation, merging, releases) are in ../AGENTS.md. The design, and why, is in ../docs/design/2026-10-03-harnessd.md. The one-page picture for new contributors is ../docs/design/2026-10-04-harnessd-before-after.md. The master runs the core and every service process (SERVICE_HOSTS in src/harnessd/services.ts). Each service process runs one or more services, each on its own link to the core. In Activity Monitor and ps they show as harnessd, harnessd-core and harnessd-<process> (src/harnessd/processName.ts). HARNESSDSERVICES names a subset to run in…

No other project uses it yet

autonomous-aiAGENTS.md

openharness / desktop

autonomous-ai/openharness/desktop/AGENTS.md

Use CLAUDE.md for architecture, build commands, and testing. For DSH dashboards, follow the DSH workspace contract: 70% viewer on the left, 30% real agent chat on the right, including loading, missing dependencies, failures, retries, and restoration. Reserve the chat slot before startup; never let an unavailable conversation become a full-width viewer. The Swarm's Your devices is a dashboard-only exception: fill its center pane, keep the sidebars visible, and do not start or reserve a Devices conversation. Standalone Devices retains its…

No other project uses it yet

autonomous-aiReads credentialsCLAUDE.md

openharness / desktop

autonomous-ai/openharness/desktop/CLAUDE.md

Harness Desktop — a Flutter app that lists Harness machines and attaches xterm terminals to the agents running on them. macOS and Linux (Ubuntu) are both real, released targets — first-run provisioning (lib/bootstrap/environmentprovisioner.dart), self-update (lib/update/desktopupdater.dart), and packaging (scripts/upload-desktop.sh / scripts/upload-desktop-linux.sh, see RELEASE.md) all branch per-OS internally rather than being separate code paths. Windows is a local desktop too, not a viewer (lib/core/viewermode.dart): homeDir() (lib/core/homedir.dart) reads USERPROFILE there even when Git Bash set HOME, console children start through lib/core/hiddenprocess.dart so no…

No other project uses it yet

autonomous-aiAGENTS.md

openharness / store

autonomous-ai/openharness/store/AGENTS.md

Before creating or changing a DSH, read the authoring guide and the DSH workspace contract. A DSH dashboard always has the real agent chat to its right, initially 70% viewer and 30% chat. Loading or failed setup must keep that chat slot and show recovery there. Verify the whole workspace, including failures, rather than only the viewer. Package AGENTS.md files describe the materialized agent's job; they do not replace this desktop integration contract.

autonomous-aiAGENTS.md

autonomous-harness

autonomous-ai/autonomous-harness/AGENTS.md

Follow CONTRIBUTING.md and the component's instructions. For validation and shipping, use docs/validation-and-release.md. For product names, terminology, and visible copy, follow the Naming System. - Measure the user's request through completion. Record implementation, validation, merge, publication, and waiting separately; an Actions duration is not the total. - Choose the necessary checks before starting them. Run affected tests and relevant integration checks; use full suites for broad changes. Start independent checks together within the machine's capacity. Do not add a second full…

autonomous-aiAGENTS.md

autonomous-harness / cli

autonomous-ai/autonomous-harness/cli/AGENTS.md

Read this before changing anything under cli/. The repository-wide process rules (validation, merging, releases) are in ../AGENTS.md. The design, and why, is in ../docs/design/2026-10-03-harnessd.md. The one-page picture for new contributors is ../docs/design/2026-10-04-harnessd-before-after.md. The master runs the core and every service process (SERVICE_HOSTS in src/harnessd/services.ts). Each service process runs one or more services, each on its own link to the core. In Activity Monitor and ps they show as harnessd, harnessd-core and harnessd-<process> (src/harnessd/processName.ts). HARNESSDSERVICES names a subset to run in…

autonomous-aiAGENTS.md

autonomous-harness / desktop

autonomous-ai/autonomous-harness/desktop/AGENTS.md

Use CLAUDE.md for architecture, build commands, and testing. For every DSH dashboard, follow the DSH workspace contract: 70% viewer on the left, 30% real agent chat on the right, including loading, missing dependencies, failures, retries, and restoration. Reserve the chat slot before startup; never let an unavailable conversation become a full-width viewer. For all UI outside terminal panes, follow the desktop design system. The user's current Mac-friendly direction supersedes earlier BIOS, fixed-cell, bracket-button, and all-monospace presentation rules. Every app icon…

autonomous-aiReads credentialsCLAUDE.md

autonomous-harness / desktop

autonomous-ai/autonomous-harness/desktop/CLAUDE.md

Harness Desktop — a Flutter app that lists Harness machines and attaches xterm terminals to the agents running on them. macOS and Linux (Ubuntu) are both real, released targets — first-run provisioning (lib/bootstrap/environmentprovisioner.dart), self-update (lib/update/desktopupdater.dart), and packaging (scripts/upload-desktop.sh / scripts/upload-desktop-linux.sh, see RELEASE.md) all branch per-OS internally rather than being separate code paths. The Windows runner exists but is unexercised. Package name is harness (import 'package:harness/...'). It lives under desktop/ in the autonomous-harness repo, beside the CLI (../cli) and the backend…

autonomous-aiAGENTS.md

autonomous-os

autonomous-ai/autonomous-os/AGENTS.md

This file provides guidance to Codex and other coding agents when working in this repository. Treat CLAUDE.md as the upstream source of truth; this file is the Codex-compatible mirror of those project rules. This repo is developed across multiple AI-assisted environments. The following rules apply to all code changes: 1. Update docs on code change - When changing behavior, architecture, or APIs, update both the English and Vietnamese docs. Keep numbers, flows, endpoints, and states accurate with the code. Platform…

autonomous-aiCLAUDE.md

autonomous-os

autonomous-ai/autonomous-os/CLAUDE.md

This repo is developed in both Cursor and Claude Code. The following rules (from .cursor/rules/) apply to all code changes: Platform docs (docs/ + docs/vi/): Lamp-specific docs (robots/lamp/docs/ + robots/lamp/docs/vi/):

autonomous-aiCursor rule

autonomous-os / rules

autonomous-ai/autonomous-os/.cursor/rules/architecture.mdc

Architecture and coding conventions for AI Lamp OpenClaw

autonomous-aiCursor rule

autonomous-os / rules

autonomous-ai/autonomous-os/.cursor/rules/docs-on-code-change.mdc

Update docs (markdown) when code changes

autonomous-aiCursor rule

autonomous-os / rules

autonomous-ai/autonomous-os/.cursor/rules/multi-ide.mdc

Multi-IDE (Cursor + Claude Code) conventions

autonomous-aiCursor rule

autonomous-os / rules

autonomous-ai/autonomous-os/.cursor/rules/testing.mdc

Testing conventions

autonomous-aiSkill

agent-management

autonomous-ai/autonomous-os/skills/agent-management/SKILL.md

Legacy Autonomous Buddy control for explicitly requested Buddy coding sessions. When the user asks a coding or research agent on their paired Harness computer to work, use harness-use instead. This manages explicit Buddy desktop CLI sessions; clicking apps and screenshots use computer-use.

autonomous-aiSkill

audio

autonomous-ai/autonomous-os/skills/audio/SKILL.md

Low-level speaker and microphone hardware control — adjust volume, play test tones, record raw audio. Do NOT use for TTS/speech (that is the Voice skill).

autonomous-aiSkill

camera

autonomous-ai/autonomous-os/skills/camera/SKILL.md

Camera control — snapshot, stream, and privacy toggle. Trigger on "what do you see", "look at this", "take a photo", "don't look", "stop looking", "stop watching", "stop staring", "camera off", "camera on", "give me privacy". MUST call [HW:/camera/disable:{}] or [HW:/camera/enable:{}] when toggling — never just reply with text.

autonomous-aiSkill

claude-buddy

autonomous-ai/autonomous-os/skills/claude-buddy/SKILL.md

Coordinate with the Claude Buddy companion (Claude Desktop + Claude Code on the user's Mac) — voice-approve tool permission prompts and stay aware of Claude activity.