Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
Assume readers are at least as smart as you, so do not over-explain. State information once and move on.
Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.
Always use relative file paths: docs/testing.md, not /Users/name/project/docs/testing.md.
Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer