Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From platform-engineering
The citation, test, and outcome discipline this repo enforces: every test cites a vendor/seed/rubric source via @cite, every commit ends with an outcome ID like (O7), every PR body declares Outcomes + Test plan + Citations sections, and TDD red/green/refactor is surfaced in commit titles. Use when bootstrapping a new repo that should adopt the same discipline, when writing a new test and unsure what @cite to point at, when composing a PR body, or when picking a @tdd stage tag.
npx claudepluginhub subagentceo/knowledge-engineering --plugin platform-engineeringHow this skill is triggered — by the user, by Claude, or both
Slash command
/platform-engineering:citations-tests-outcomesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Bootstrapping a new repo and want to adopt the same discipline
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Share bugs, ideas, or general feedback.
@cite should point at@tdd red/green/refactor)@cite)Every test file has a JSDoc header naming the source-of-truth the
test asserts against. Citation paths MUST start with vendor/,
seeds/, or rubrics/.
/**
* @tdd green
* @cite vendor/anthropics/platform.claude.com/docs/en/build-with-claude/embeddings.md
* @cite vendor/turbopuffer/turbopuffer.com/docs/performance.md
*/
Enforced by scripts/lib/citation-guard.ts.
Runs in npm run verify:citations. Citations not under those three
prefixes fail the verify chain.
Every commit subject ends with (O<N>) where O<N> is a stable
outcome ID declared in either the orchestrator prompt or the PR body.
feat(bridge): GREEN voyage client + turbopuffer-alloydb bridge (OPE3)
refactor(bridge): extract assertOAuthOnlyPosture (OPE3)
test(bridge): RED failing tests (OPE3)
Per docs/CONVENTIONS.md.
Enforced by src/lib/conventions.test.ts
for commits after 2026-05-15.
@tdd red|green|refactor)Every test file added under src/lib/, scripts/lib/, or
infra/cloudflare/src/ after 2026-05-15T13:00Z carries an @tdd
tag in its JSDoc header. Enforced by npm run verify:tdd.
Three-stage rhythm:
@tdd red — test exists, module under test doesn't yet@tdd green — module exists, all tests pass@tdd refactor — internal restructure, tests stay greenEach stage is its own atomic commit. PR #169 (routine schema) is a canonical example: 4 commits — RED → GREEN → REFACTOR → citation-fix.
.github/pull_request_template.md
enforces these sections:
Closes #N / Refs #NStrong PR bodies include an evaluation matrix mapping each outcome to a measure. Example from PR #169:
| Criterion | How it's measured | Result |
|---|---|---|
| Every documented option is enumerated | 6 closed-set enums | ✓ |
| Schedule one-of enforced | 3 tests | ✓ |
| Zod v4 idioms only | No deprecated string methods | ✓ |
| Coverage gate (≥70%) | npm run verify:coverage | ✓ 91% |
Outcome-driven development makes every change traceable to a declared end state. Citation discipline keeps tests anchored to ground truth (vendor docs, seed extracts, rubric criteria) rather than the test author's interpretation. TDD stages make the design pressure of "test before code" visible in the commit graph instead of being invisible process discipline.
docs/CONVENTIONS.md — outcome-driven Conventional Commitsscripts/lib/citation-guard.ts — @cite enforcerscripts/verify-tdd-stage.ts — @tdd tag enforcer.github/pull_request_template.md — PR shapevendor/anthropics/platform.claude.com/docs/en/managed-agents/define-outcomes.md — upstream "define outcomes" doctrineseeds/citations/define-outcomes.md — extract