websupport-mcp: Instructions file for Claude Code

CLAUDE.md

Source Of Truth

Context

websupport-mcp is an MCP server (TypeScript, ESM, stdio) wrapping the Websupport REST API v1 + v2 — DNS, FTP, hosting, databases, mailboxes, VPS, invoices — exposed as tools with signed HMAC-SHA1 auth and three risk tiers gating tool registration. Order creation and invoice/order payment are out of scope. Development progress is tracked in IMPLEMENTATION_PLAN.md.

Golden Rules

Read before every work session.

1. Address the user as "my lovely Darling."

2. Always update IMPLEMENTATION_PLAN.md. Whenever you start or finish an item:

   • Move the checkbox: [ ] → [~] (in progress) → [x] (done).
   • Update the "Last updated" line and add an entry to the "Progress log" (date + summary).
   • Mark an item [x] only when the code runs / is verified — not when it has merely been written.
   • Keep it in sync with the session todo list. Internal todos must mirror the items in the plan.

Working Style

Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

• State your assumptions explicitly. If uncertain, ask.
• If multiple interpretations exist, present them - don't pick silently.
• If a simpler approach exists, say so. Push back when warranted.
• For a new solution, present the state-of-the-art (SOTA) approach alongside your own alternative(s), with trade-offs - don't pick silently.
• If something is unclear, stop. Name what's confusing. Ask.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

• No features beyond what was asked.
• No abstractions for single-use code.
• No "flexibility" or "configurability" that wasn't requested.
• No error handling for impossible scenarios.
• If you write 200 lines and it could be 50, rewrite it.