Merge branch 'master' into docs/data-retention

Author: marcel-rbro

.claude/README.md

@@ -0,0 +1,115 @@
+# Claude Code configuration for Apify docs
+
+This directory contains Claude Code configuration for the Apify documentation repository.
+
+## Structure
+
+```text
+.claude/
+├── README.md              # This file - Quick start guide
+├── instructions.md        # Main instructions for Claude Code
+├── rules/                 # Canonical standards (auto-loaded)
+│   ├── writing-style.md   # Prose voice and tone
+│   ├── content-standards.md  # Formatting and structure
+│   ├── terminology.md     # Product names and capitalization
+│   ├── file-organization.md  # Naming conventions
+│   ├── grammar-rules.md      # Grammar mechanics, punctuation, numbers, brand spelling
+│   └── quality-standards.md  # Quality checklist
+└── skills/                # Reusable skills for common tasks
+    ├── doc-write/         # Documentation writing skill
+    ├── api-doc/           # API documentation skill
+    ├── tutorial/          # Tutorial creation skill
+    └── review-docs/       # Documentation review skill
+```
+
+## How to use
+
+### For Claude Code users
+
+1. **Start a new session**: Claude Code will automatically read `instructions.md`
+2. **Use skills**: Type `/doc-write`, `/api-doc`, `/tutorial`, or `/review-docs` to use specific skills
+3. **Reference standards**: Always refer to `AGENTS.md` in the repo root for core standards
+
+### Available skills
+
+#### /doc-write
+Documentation writing - Create or edit pages following style guide
+
+#### /api-doc
+API documentation - Work with OpenAPI specifications and endpoints
+
+#### /tutorial
+Tutorial creation - Build structured, educational tutorials
+
+#### /review-docs
+Documentation review - Check quality and compliance before submission
+
+## Quick start
+
+### Writing new documentation
+
+```text
+Use /doc-write skill to create a new documentation page about [topic]
+```
+
+### Creating a tutorial
+
+```text
+Use /tutorial skill to create a tutorial on [topic]
+```
+
+### Adding API endpoint
+
+```text
+Use /api-doc skill to document the new [endpoint-name] endpoint
+```
+
+### Reviewing documentation
+
+```text
+Use /review-docs skill to review sources/platform/[file-name].md
+```
+
+## Documentation standards
+
+All documentation standards are in `.claude/rules/` (auto-loaded):
+
+1. **`writing-style.md`** - Prose voice and tone
+1. **`content-standards.md`** - Formatting and structure
+1. **`terminology.md`** - Product names and capitalization
+1. **`grammar-rules.md`** - Grammar mechanics, punctuation, numbers, brand spelling
+1. **`file-organization.md`** - File naming and directory structure
+1. **`quality-standards.md`** - Complete quality checklist
+
+Also reference:
+
+- **`AGENTS.md`** - Vendor-agnostic documentation standards (in repo root)
+- **`CONTRIBUTING.md`** - Setup, workflows, contribution process
+- **`instructions.md`** - Full Claude Code instructions (in this directory)
+
+## Testing
+
+Before submitting:
+
+```bash
+npm run lint:md      # Check markdown
+npm run lint:code    # Check code
+vale "path/to/file.md" --minAlertLevel=error  # Check prose style
+npm run openapi:lint # Validate OpenAPI specs
+npm start            # Preview changes
+```
+
+## Best practices
+
+1. **Read `CLAUDE.md` first**
+2. **Check `.claude/rules/`** - Auto-loaded standards for writing, formatting, terminology
+3. **Use the appropriate skill** - Designed for specific documentation tasks
+4. **Run linters before committing** - `npm run lint:md`, `npm run lint:code`, and `vale`
+5. **Review before submit** - Use `/review-docs` skill for final checks
+
+## Need help?
+
+- Questions about style: Check `AGENTS.md`
+- Setup issues: See `CONTRIBUTING.md`
+- Skill usage: Read the specific skill file
+- Claude Code general: Visit [Claude Code docs](https://github.com/anthropics/claude-code)

.claude/claude.json

@@ -0,0 +1,6 @@
+{
+  "instructions": "instructions.md",
+  "context": [
+    "../CONTRIBUTING.md"
+  ]
+}

.claude/instructions.md

@@ -0,0 +1,28 @@
+# Claude Code instructions for Apify documentation
+
+`CLAUDE.md` (symlink to `AGENTS.md`) covers project architecture, commands, and common pitfalls. Documentation standards are auto-loaded from `.claude/rules/` - those are the canonical source for all writing, formatting, and terminology rules.
+
+## Available skills
+
+| Skill | When to use |
+|---|---|
+| `/doc-write` | Creating or editing documentation pages |
+| `/api-doc` | Working with OpenAPI specifications |
+| `/tutorial` | Creating step-by-step tutorials |
+| `/review-docs` | Reviewing documentation before submission |
+
+## PR title format
+
+Use [Conventional Commits](https://www.conventionalcommits.org/) - enforced by CI:
+
+- `docs: <description>` - Documentation changes (most common)
+- `fix: <description>` - Bug fixes
+- `feat: <description>` - New features
+- `chore: <description>` - Maintenance tasks
+
+## Key reminders
+
+- Never make assumptions about product features - ask if unsure
+- For code review: check comments and obvious mistakes only (not full code review)
+- Prioritize clarity and usefulness over strict rule adherence
+- See `CONTRIBUTING.md` for development setup and contribution workflow