Omar SobhandClaude Opus 4.7
7b23f61632
Hand-authored skill catalog anchored to real 2026-07 versions:
- Rust 1.97.1 (stable), edition 2024
- React 19.2.7, Server Components + Actions
- TailwindCSS 4.3.3 (CSS-first config, Oxide engine)
- three.js r185 (WebGPURenderer stable, BatchedMesh matured)
- React Native 0.86 / Expo SDK 54+ (New Architecture default)
- cargo-nextest 0.9.140, gitleaks 8.20+, cargo-audit 0.21+
- Postgres 17 (18 in beta, don't rely on)
- CUDA Blackwell, Metal Apple7+, ROCm CDNA3
Ships 15 skills across the categories:
foundation/ workspace-repo-commit-protocol
small-focused-commits
tdd-red-green-refactor
code-review-checklist
int-xx-marker-protocol
decompose-int-items
rust/ write-rust-current-edition
rust-error-handling
cargo-test-driven-development
rust-async-tokio-idioms
backend/ postgres-migrations-forward-only
postgres-index-selection
api-pagination-day-1
frontend/ react-19-server-components
tailwind-v4-idioms
component-4-state-model
mobile/ expo-managed-vs-bare
rn-flashlist-perf
gpu/ gpu-coalescing-and-occupancy
roofline-model
threejs/ threejs-perf-and-teardown
security/ cargo-audit-workflow
secret-scanning-gitleaks
skills_loader.rs walks skills/**/*.md, parses YAML frontmatter
(name, description, when_to_use, tags), upserts via
skills_catalog::upsert_builtin. Idempotent per boot — bumps version
+ appends skill_versions row ONLY when body changes. Deterministic
sha256-derived ids so builtins are stable across boots.
Dockerfile copies skills/ to /etc/clawmates/skills. Server boot
task spawns loader alongside team_template_loader.
Follow-ups (Slice 3.5c continuation, future PRs):
- 20-30 more skills (duckdb, shadcn composition, a11y, WebGPU
migration, metal frame capture, rocprof, deep gitea forge
integration, semgrep rulepacks)
- Bind skills to team template roles (add [role.skills] refs to
templates/teams/*.toml + wire template_role_skills population
in team_template_loader)
Co-Authored-By: Claude Opus 4.7 <[email protected]>
2.5 KiB
2.5 KiB
name, description, when_to_use, tags
| name | description | when_to_use | tags | |||
|---|---|---|---|---|---|---|
| tdd-red-green-refactor | Strict test-driven development — write the failing test first, make it pass minimally, then refactor. Prevents overbuilt code and pinpoints regressions. | Before writing any behavior-adding code. Applies to Rust, TypeScript, Python, anywhere tests can run cheap. |
|
TDD: red → green → refactor
The loop
- RED — Write the test that fails because the behavior doesn't exist yet. Run it. Confirm it fails for the RIGHT reason (missing symbol, wrong output — not a syntax error).
- GREEN — Write the simplest possible code that makes the test pass. Not the "correct" version — the SIMPLEST one. Hardcoded return value is legal.
- REFACTOR — Now that you have a passing safety net, restructure. Extract, rename, tighten types. Every intermediate state must still be green.
- Commit the RED-to-GREEN pair as one commit. The refactor is its own commit.
Why this order
- Writing the test first forces you to design the API from the caller's perspective. The API you wish existed usually beats the API you accidentally get.
- Watching the test fail proves the test can fail — a test that has never failed is a test you don't trust.
- Refactoring under a green bar means every step is safe. Refactoring in the dark means every step could silently break behavior.
What counts as "a test"
- Rust:
#[test]unit test,#[tokio::test]async, or an integration test undertests/. Not aprintln!. - TypeScript: Vitest / Jest / Playwright. Storybook + a visual snapshot counts for component work.
- Any language: it exits non-zero when the behavior is broken, without a human interpreting the output.
Coverage discipline
- Target: ≥90% line coverage on files you touched in this INT-XX item. Measured by
cargo llvm-covfor Rust,vitest --coveragefor TS. - Coverage regressions on changed files block merge — enforce via the mission's
commit_policy(Slice 4). - 100% coverage is a smell — usually means testing implementation details. Aim for behavior coverage.
Anti-patterns
- Writing the impl first "because it's obvious" and adding tests after — you already lost the design feedback and the tests will inevitably shape to what the impl happens to do.
- Testing multiple behaviors in one
#[test]— a failure now hides what actually broke. - Snapshot-only test suites — snapshots catch NOTHING structural. Pair with at least one assertion per behavior.