feat: add recce-docs-guide local skill and update CLAUDE.md

[kentwelcome]

Summary

• Add .claude/skills/recce-docs-guide.md — a local skill that handles writing, editing, and reviewing documentation with MkDocs-specific conventions
• Update CLAUDE.md — refresh file structure table and add Plugin Dependency section for recce-team plugin
• Update .gitignore — ignore .claude/superpowers/ and .claude/settings.local.json
• Apply recce-team:writing-content standards to MCP Server and Claude Plugin pages (PR docs: Update MCP Server and Claude Plugin pages for new tools #93 review)

Resolves GTM-536

Design

The skill layers on top of the recce-team:writing-content plugin:

• Local skill owns: MkDocs conventions (image format, admonitions, page template, heading styles, nav updates, redirects)
• Plugin provides: Voice, formatting, terminology, QA, and AISEO reviews
• Local claude/ files kept: Writing principles (ICP definitions, audience strategy), terminology (confusion analysis, clarification patterns), and knowledge base (site map) contain unique docs-specific content not in the plugin

The skill auto-triggers on any work in docs/, mkdocs.yml, or claude/ and routes to:

• Lightweight path for small edits (1-2 pages, no nav changes)
• Full path for major changes (new pages, restructuring, 3+ pages)

PR #93 content review

Applied recce-team:writing-content skill as a test case for the new docs guide. Changes to mcp-server.md and claude-plugin.md:

Issue	Fix
"single-environment mode" uses "environment"	→ "single-source mode" (terminology guide)
Duplicated single-source mode note	Removed duplicate (state details once)
"Next Steps" heading	→ "Next steps" (sentence case for H2)
Long feature list in claude-plugin.md	Tightened for readability
"all modes" vague in mcp-server.md	Clarified tool grouping by function

Test plan

• Verify .claude/skills/recce-docs-guide.md is detected as a skill in Claude Code
• Verify the skill triggers when editing files under docs/
• Verify pre-flight check prompts plugin installation if recce-team is not installed
• Verify CLAUDE.md renders correctly with updated file structure table
• Verify mkdocs build passes with MCP/Claude Plugin page changes

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds a repo-local Claude Code skill to standardize documentation work for this MkDocs site, updates contributor guidance, and ignores local Claude config artifacts.

Changes:

• Add .claude/skills/recce-docs-guide.md to define MkDocs-specific documentation conventions and a plugin pre-flight check.
• Update CLAUDE.md file structure table and add a recce-team plugin dependency/install section.
• Update .gitignore to ignore local Claude Code state/config files.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
CLAUDE.md	Updates repo documentation guidance and adds plugin installation instructions.
.gitignore	Ignores local-only Claude Code files/directories to avoid repo churn.
.claude/skills/recce-docs-guide.md	Introduces a local skill defining docs workflows and MkDocs formatting conventions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ijac13]

I used to use recce-team to write the doc and then create a PR in recce-docs.
Do we need to have Claude here? I want to keep single source of truth about the voice, context, format..etc.

[ijac13]

Why do we need this here? It feel duplicated with https://github.com/DataRecce/recce-team/blob/main/recce-team/context/product/terminology.md and https://github.com/DataRecce/recce-team/blob/main/recce-team/context/product/recce-context.md