Claude Coding Rules
## Overview
This document contains coding standards and best practices that must be followed for all code development. These rules prioritize maintainability, simplicity, and modern Python development practices
provider auth model (Azure CLI +
MSAL), the error reference, and known issues are documented in `references/` —
see `definition-reference.md`, `connection-patterns.md`, and
`error-troubleshooting.md`. Read those before building or editing flows.
This file
extra instances - they are internal (`ollama2:11434`); `caddy-addon/site-*.conf` is the documented extension point
- The generator is invoked unconditionally from `05_configure_services.sh`, which covers install and `make update
function parameters across `pipelex/` source must be **keyword-only**, so call sites are self-documenting: `do_thing(retries=3, timeout=30)` over the opaque `do_thing(3, 30)`. The compliant
Documentation Site Architecture
This file documents non-obvious architectural decisions for the docs site (`docs.pipelex.com`). Read this before modifying anything under `docs/`.
## Site Architecture Overview
- MkDocs Material with `mike` versioning
agents must be able to use mcpc without any external agent skills, prompts, or documentation: `--help` output and error messages must provide all the context an agent needs to discover
plugins/ # Example plugins (fully standalone, NOT in npm workspaces)
├── e2e/ # Playwright E2E tests
└── docs/ # Documentation site (Next.js)
```
Each subdirectory has its own `CLAUDE.md` with package-specific details.
### Key Concepts
**Tool
Docs Project Instructions
## Overview
The OpenTabs documentation site is built with Next.js 16, content-collections for MDX, and a neo-brutalist design system. Content is authored in MDX under `content
Installed Documentation (llmstxt)
When working with these technologies, read the corresponding skill for detailed reference:
- Stripe: .agents/skills/stripe/SKILL.md
- AI SDK: .agents/skills/ai-sdk/SKILL.md
measured 2026-09-11 at 39 specs on an M-series mac; it was documented as "~20 min" for months and then as "~70s", and both numbers stopped anybody from
revdiff
TUI for reviewing diffs, files, and documents with inline annotations, built with bubbletea.
**Architecture**: see [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for system design, data flows, interfaces, and design decisions.
## Commands
- Build: `make
CLAUDE.md - MicrosoftFabricMgmt Module Development Guide
## Overview
This document provides comprehensive instructions for AI-assisted development of the **MicrosoftFabricMgmt** PowerShell module located in `tools/MicrosoftFabricMgmt/`. This module provides a robust interface
separate (unauthenticated) auth context.
- **`invoke_fabric_ps`** has no input sanitisation by design — document this clearly and
only use it in trusted AI-agent environments.
---
## Testing
### Unit tests (no pwsh
README
and one deliberate exception: shape colours are literal OKLCH values stored
in the document, not tokens — a token would repaint when the _viewer_
switches theme and change someone else
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.