chalk
claudecodexCapture intent across issues, commits, and PRs — why, not just what.
11 skills · 3 agents
Velocity through clarity.
Plugin allium from marketplace juxt-plugins in juxt/claude-plugins. Commands read from the repo's manifest — 3 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
alliumGive your AI agents something more useful than a prompt. Velocity through clarity.
distillExtract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase
elicitRun a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality an
propagateGenerate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification re
tendTend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating spe
weedWeed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, o
witnessIndependently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal,
distillExtract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase
propagateGenerate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification re
tendTend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating spe
weedWeed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, o
witnessIndependently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal,
node "${CLAUDE_PLUGIN_ROOT}/hooks/loop-trace.mjs" pre
node "${CLAUDE_PLUGIN_ROOT}/hooks/allium-check.mjs"
node "${CLAUDE_PLUGIN_ROOT}/hooks/loop-trace.mjs" post
Capture intent across issues, commits, and PRs — why, not just what.
11 skills · 3 agents
Agentic coding harness for complex domains: a cheap agent finds the route to the goal end-to-end, then each change lands small and simple enough for a human to review and put down.
5 skills · 2 agents
Interrupt forward momentum and step back to reassess. A circuit-breaker for when Claude is spinning or scope-creeping.
1 skill
Build and query a code-only LSP-based symbol and call-graph map of the current project. A navigation accelerator for multi-file code reasoning.
1 skill
Pipe long command output through glance for token-efficient summaries instead of reading all tokens.
1 skill
Clojure / ClojureScript language server (clojure-lsp + clj-kondo) for code intelligence, refactoring, and analysis.
Easily create custom hooks to prevent unwanted behaviors by analyzing conversation patterns or from explicit instructions. Define rules via simple markdown files.
1 skill · 4 commands · 1 agent · hooks
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
6 skills
SPARC methodology — Specification, Pseudocode, Architecture, Refinement, Completion phases with quality gates
3 skills · 1 command · 1 agent
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Connect Claude to Fullstory to query behavioral analytics, session replays, and customer experience insights.
5 skills · 1 agent · 1 MCP server
OpenAPI specification generation, Mermaid diagram creation, tutorial writing, API reference documentation
3 skills · 1 command · 5 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.