juxt

juxt/claude-plugins

Skill Claude CodeCodex

Give your AI agents something more useful than a prompt. Velocity through clarity.

juxt/claude-plugins

Skill Claude CodeCodex

Extract 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 does in Allium…

juxt/claude-plugins

Skill Claude CodeCodex

Run 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 and needs help…

juxt/claude-plugins

Skill Claude CodeCodex

Generate 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 requires.

juxt/claude-plugins

Skill Claude CodeCodex

Tend 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 specs to a new…

juxt/claude-plugins

Skill Claude CodeCodex

Weed 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, or verify whether…

juxt/claude-plugins

Skill Claude CodeCodex

Independently 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, or check that an…

juxt/claude-plugins

Plugin Claude Code

Capture intent across issues, commits, and PRs — why, not just what.

juxt/claude-plugins

Agent

Mechanics layer for the chalk skills — manages GitHub state (issues, comments, PRs, issue relationships). Handles gh calls for creating/updating chalk comments, updating Progress sections, creating issues, creating PRs, reading and searching issue state, and managing sub-issue and blocked-by relationships. DO NOT…

juxt/claude-plugins

Agent

Deletes code comments that don't earn their place, from the files a change touched. Runs the triggers, the test and the level-of-detail check from chalk:code-comments against code it has never seen before, and applies the deletions. DO NOT invoke this agent directly from the main conversation, and DO NOT tell it what…

juxt/claude-plugins

Agent

Reviews a drafted commit body or PR description as the artefact's pinned reader would — cutting sentences answerable from what that reader already holds, and reporting where the why is missing. Deletion-only; it never rewrites. DO NOT invoke this agent directly from the main conversation, and DO NOT give it the…

juxt/claude-plugins

Skill Claude CodeCodex

The chalk writing voice applied to Allium specifications — a spec states the aim, and what it does not state, it excludes. Load before writing or editing any .allium file, any obligation, invariant, guarantee or guidance annotation, or any -- comment body within one. Use when the user says "edit the spec", "add an…

juxt/claude-plugins

Skill Claude CodeCodex

Track session intent and progress against GitHub Issues, and write chalk comments and Progress sections in the chalk voice. Use when the user says "chalk.

juxt/claude-plugins

Skill Claude CodeCodex

What earns a code comment, and what to delete — interface versus implementation comments, the pinned readers, the triggers and the test, and where rejected material goes instead. Load early in any session that touches code, before writing or editing any comment, docstring or kdoc, and again when reviewing a diff…

juxt/claude-plugins

Skill Claude CodeCodex

Create a commit with a contextual body explaining the why, in the chalk voice. Use when the user says "commit this", "commit", "make a commit", "/chalk:commit"; OR is about to compose, draft, write or amend any git commit message body (e.g. "write a commit message", "draft the commit body", "amend the commit…

juxt/claude-plugins

Skill Claude CodeCodex

Structure a goal as a tree whose children accomplish their parent rather than argue for it, and test each node for sufficiency. Load whenever writing something with a goal structure in it — the direction or target end state of a piece of work, an issue's Implementation or Future state section, the shape of a problem…

juxt/claude-plugins

Skill Claude CodeCodex

Create a GitHub issue, or update an existing issue's description, with a body that captures the problem and why it matters, in the chalk voice. Use when the user says "open an issue", "file a bug", "raise an issue", "create an issue", "file a ticket", "/chalk:issue"; OR is about to compose, draft, write or update any…

juxt/claude-plugins

Skill Claude CodeCodex

How to structure anything the reader has to follow — a mindmap of nested bullets whose parents are claims and whose children back them up. Load before drafting any commit body, issue, PR description, chalk comment, code comment or docs section with more than a couple of steps of reasoning in it; the chalk…

juxt/claude-plugins

Skill Claude CodeCodex

Create a pull request with a description that captures the intent and reasoning behind the change, in the chalk voice. Use when the user says "create a PR", "open a PR", "submit a PR", "raise a PR", "make a PR", "PR this", "/chalk:pr"; OR is about to compose, draft, write or update any pull request title or body (e.g.…

juxt/claude-plugins

Skill Claude CodeCodex

Report where the current session has got to as a mindmap — what has landed, what is still open as ID'd ideas, decisions and questions, and a tl;dr. Use when the user says "/sitrep", "where are we", "where were we", "recap the session", "what's still open", or is picking a session back up after a break, a compaction or…

juxt/claude-plugins

Skill Claude CodeCodex

Write or update a technical documentation page in the chalk voice, structured around Diataxis. Use when the user says "tend the docs", "update the docs", "write a docs page", "document this feature", "add a how-to for X", "/chalk:tend-docs", or references adding/editing an end-user-facing docs page in a technical…

juxt/claude-plugins

Skill Claude CodeCodex

Shared chalk writing voice — the universal principles, the explanation quadrant, and the line-format rule. The chalk, chalk:issue, chalk:commit, chalk:pr and chalk:tend-docs skills load this before drafting any GitHub-bound or docs prose; a human may run it to read the guide. Companion skills chalk:mindmap (the shape…

juxt/claude-plugins

Skill Claude CodeCodex

Audit technical documentation for drift against a code change. Produce a punch list of user-facing docs pages that probably need updating. Use when the user says "weed the docs", "check docs for drift", "audit docs against this diff", "which docs does this change affect", "/chalk:weed-docs", or is about to open a PR…

juxt/claude-plugins

Plugin Claude Code

Interrupt forward momentum and step back to reassess.