repo standardisation

Author: MelbourneDeveloper

.claude/skills/ci-prep/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: ci-prep
+description: Prepares the current branch for CI by running lint, test, coverage, and build in sequence, fixing issues at each step. Use before pushing a branch or when the user wants to verify the branch will pass CI.
+---
+
+# CI Prep
+
+Prepare the current state for CI. Ensures the branch will pass CI before pushing.
+
+## Steps
+
+1. Run `make lint` — fix any issues before continuing
+2. Run `make test` — fix any failures before continuing
+3. Run `make coverage-check` — coverage must meet threshold
+4. Run `make build` — confirm build succeeds
+5. Report: all clear / what failed
+
+## Rules
+
+- Do not push if any step fails
+- Fix issues found in each step before moving to the next
+- Never skip steps or suppress errors
+
+## Success criteria
+
+- `make ci` exits with code 0
+- Coverage threshold met
+- Build artifacts produced successfully

.claude/skills/fmt/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: fmt
+description: Formats all code in this repo (C# with CSharpier, Rust with cargo fmt). Use when the user asks to format code, fix formatting, or before committing changes.
+---
+
+# Format
+
+Format all code in this repo.
+
+## Steps
+
+1. Run `make fmt`
+2. Run `make fmt-check` to confirm clean
+3. Report which files were modified
+
+## Success criteria
+
+- `make fmt-check` exits with code 0 after formatting

.claude/skills/format/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: lint
+description: Runs all linters and format checks across C#, Rust, and TypeScript, then fixes any issues found. Use when the user asks to lint, check code quality, or fix linting errors.
+---
+
+# Lint
+
+Run all linters and report issues.
+
+## Steps
+
+1. Run `make lint`
+2. Run `make fmt-check`
+3. Report all issues found (file, line, rule, message)
+4. If issues found, fix them and re-run to confirm clean
+
+## Rules
+
+- Never suppress a lint warning with an ignore comment
+- Fix the code to satisfy the linter
+- If a rule seems wrong for a specific case, document why in code comments
+
+## Success criteria
+
+- `make lint` exits with code 0
+- `make fmt-check` exits with code 0
+- Zero warnings or errors output

.claude/skills/lint/SKILL.md

@@ -0,0 +1,22 @@
+{
+  "name": "DataProvider (C#/.NET)",
+  "image": "mcr.microsoft.com/devcontainers/dotnet:1-9.0",
+  "remoteUser": "vscode",
+  "postCreateCommand": "bash .devcontainer/setup.sh",
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "ms-dotnettools.csharp",
+        "ms-dotnettools.csdevkit",
+        "usernamehw.errorlens",
+        "csharpier.csharpier-vscode"
+      ],
+      "settings": {
+        "editor.formatOnSave": true,
+        "[csharp]": {
+          "editor.defaultFormatter": "csharpier.csharpier-vscode"
+        }
+      }
+    }
+  }
+}

.devcontainer/devcontainer.json

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+echo "==> Setting up development environment..."
+
+# ---- .NET ----
+if command -v dotnet &>/dev/null; then
+  dotnet restore
+  dotnet tool restore
+fi
+
+# ---- Rust (for LQL LSP) ----
+if command -v cargo &>/dev/null; then
+  cd Lql/lql-lsp-rust && cargo build && cd ../..
+fi
+
+# ---- Node (for LQL Extension) ----
+if command -v npm &>/dev/null && [[ -f Lql/LqlExtension/package.json ]]; then
+  cd Lql/LqlExtension && npm install --no-audit --no-fund && cd ../..
+fi
+
+echo "==> Setup complete. Run 'make ci' to validate."