openclaw - 💡(How to fix) Fix Docs: Create developer onboarding guide separate from user documentation [1 participants]

## Before You PR

- Test locally with your OpenClaw instance
- Run tests: `pnpm build && pnpm check && pnpm test`
- For extension/plugin changes, run the fast local lane first:
  - `pnpm test:extension <extension-name>`

docs/development/
├── README.md              # Developer onboarding start page
├── architecture/
│   ├── README.md         # High-level system diagram
│   ├── gateway.md        # Gateway protocol and WebSocket details
│   ├── plugins.md        # Plugin/extension architecture
│   └── channels.md       # Channel implementation patterns
├── setup.md              # Development environment setup
├── testing.md            # Testing philosophy and patterns
├── debugging.md          # Common debugging techniques
└── contributing/
    ├── code-review.md    # What to expect in review
    └── conventions.md    # Coding conventions beyond linting

# OpenClaw Development Guide

Welcome to OpenClaw development! This guide is for contributors working on
the core codebase, plugins, extensions, or tooling.

## Quick Start

1. **Environment**: Node 22+, pnpm, macOS/Linux/WSL2
2. **Clone**: `git clone https://github.com/openclaw/openclaw.git`
3. **Install**: `pnpm install`
4. **Build**: `pnpm build`
5. **Test**: `pnpm test:fast`

## Architecture Overview

## Key Code Locations

| Component | Location | Entry Point |
|-----------|----------|-------------|
| Gateway | `src/gateway/` | `src/gateway/server.ts` |
| Channels | `src/channels/` | `src/channels/channel-web.ts` |
| Plugin SDK | `src/plugin-sdk/` | `src/plugin-sdk/index.ts` |
| Extensions | `extensions/` | `extensions/<name>/index.ts` |
| CLI | `src/cli/` | `src/cli/*.ts` |

## Development Workflow

1. Check existing issues or discuss in Discord
2. Fork and branch
3. Make changes
4. Run relevant tests (see Testing Guide)
5. Submit PR (see Contributing Guide)

## Resources

- [Architecture](architecture/)
- [Testing Guide](testing.md)
- [Debugging Tips](debugging.md)

# Plugin/Extension Architecture

## Extension vs Plugin

- **Extensions**: Bundled with OpenClaw, in `extensions/` directory
- **Plugins**: Third-party, installed from npm or ClawHub

## Plugin SDK Boundary

Extensions must import only from `openclaw/plugin-sdk/*`:

```typescript
// ✅ Good
import { defineChannel } from "openclaw/plugin-sdk/channel-setup";

// ❌ Bad - internal implementation detail
import { something } from "../../src/channels/internal";

extensions/<name>/
├── index.ts              # Entry point
├── package.json          # Extension metadata
├── manifest.json           # OpenClaw-specific config
└── src/
    └── ...

## Content to Migrate/Create

From existing docs:
- `AGENTS.md` → `docs/development/contributing/agents-guide.md`
- Testing patterns from `CONTRIBUTING.md` → `docs/development/testing.md`
- Architecture info from Discord/wiki → `docs/development/architecture/`

New content needed:
- Gateway protocol deep dive
- Plugin SDK reference
- Channel implementation walkthrough
- Debugging common issues

## Acceptance Criteria

- [ ] `docs/development/` directory created
- [ ] `README.md` with quick start and architecture overview
- [ ] `architecture/` with high-level diagrams
- [ ] `testing.md` with test selection guide
- [ ] `setup.md` with platform-specific notes
- [ ] Links added from `CONTRIBUTING.md` and main `README.md`

## References

- Current: `CONTRIBUTING.md`, `AGENTS.md`
- Related: Plugin SDK in `src/plugin-sdk/`
- Discord: #dev channel for architecture discussions

---

**Priority:** Medium
**Effort:** Medium (2-3 days)
**Labels:** docs, dx, good first issue