claudecodex

code-desk

Set a project's starting conditions and run the work through them: interview the owner into a written quality contract, build and red-prove the one gate command that enforces it, then keep the release loop honest — the review findings a green check hides, recurring status comms and authored presentations with portable PptxGenJS packages, existing-deck editing and rendered verification, READMEs backed by live screenshots, and the project-memory taxonomy. The in-repo _meta planning system that used to ship here now lives in the mise-en-place plugin. Release history: https://github.com/hsb3/dotfiles-agents/releases.

0 on GitHubby Henry S. Burden IIIv0.16.0MITupdated 29 days ago
/

Plugin code-desk from marketplace dotfiles-agents in hsb3/dotfiles-agents. Commands read from the repo's manifest — 28 days ago.

What it installs

Skills (6)

  • comms

    Produce your recurring communication deliverables - a morning status briefing, end-of-day wrap-up, weekly planning briefing, advisor board status readout, or client product overview - as a deck (plus optional spoken companion) to a consistent standard. Use when you ask for any of those by name, or f

  • presentations

    Create, inspect, edit and review PowerPoint decks and templates (.pptx/.potx). Use semantic palettes, deliberate typography, portable PptxGenJS source packages and rendered visual verification. Recurring briefing content goes through comms, which calls this skill for external decks.

  • project-memory

    The agent-memory taxonomy (layers, loading modes, memory vs rule vs skill, the birth rule) and the scripts that wire a repo for it or migrate it after a move. Use for "where does this memory go", "promote a memory", "run a curation pass", "memory vs rule vs skill", "set up project memory", "opt this

  • pull-request

    Work a pull request's review findings after the checks go green — collect the inline review comments, the review and summary-level comments, and the gate statuses; classify each finding as actionable (it sits on a line this PR changed, or it is a failing hard gate) or as pre-existing rot; then repor

  • readme-value-and-proof

    Turn a README into a user-centric pitch backed by real visual proof. Use when asked to write/refresh a README with a value proposition, capture app screenshots for docs, add "visual proof" of a UI/feature, or explain "what someone gets" from a project. Captures live screenshots from the running app

  • starting-conditions

    Set a project's starting conditions before the code exists — the conversation that decides what is being built, in what language, and which quality checks are machine-enforced, ending in a `RULES.md` contract plus one gate command that proves it. Use when starting a new repo or project, adding rigor

Slash commands (1)

  • /code-desk:pr-findings

    Triage a pull request's review findings — read the inline comments, the review and summary bodies, and the gate status, then report what is actionable and what is deferred as pre-existing, with nothing dropped.

Subagents (1)

  • rig-builder

    Build and prove a repo's quality gate from a written contract — scaffolds the runner, config, and any custom checker, proves the gate green AND red, and reports a measured baseline. Dispatch once a RULES.md exists and the stack is decided; it is mechanical work with a machine-checkable definition of

View source on GitHub

More from hsb3/dotfiles-agents

All 12 plugins →

atelier

claudecodex

Delegate work to model-tiered agents instead of doing it all in one session: size the task, pick a delegation architecture, and dispatch scoped slices to scouts, builders, reviewers, and managers. Skills cover orchestration, session handoff, backlog waves, and a review cycle that runs before work lands. Hooks watch the context watermark, keep the handoff fresh and surface it on cold start, isolate writing workers in their own git worktrees, hold protected config in custody, and refuse a worker git call that would sweep away a sibling's uncommitted work or land on a protected branch. Enforcement follows the main checkout into a linked worktree, so an isolated worker is no longer an unguarded one. Run /atelier:activate to arm it in a project and see what each hook resolved. Release history: https://github.com/hsb3/dotfiles-agents/releases.

9 skills · 2 commands · 5 agents · hooks

0

The home for every skill that stands on its own and has no topical plugin of its own, in one install instead of a shelf of one-skill plugins: harness and environment config, test quality, research and decision tooling, chart design, API and TUI craft, repo and project setup, and sandboxed opencode instances. Membership is derived, not curated — a gate re-reads the skill bodies every run and keeps out anything that needs a companion agent or hook, anything a topical plugin already owns, plus a documented exemption class for skills that prescribe an opt-in system the consumer chooses deliberately, in-repo or external. Release history: https://github.com/hsb3/dotfiles-agents/releases.

14 skills

0

An in-repo _meta/ planning system: a documented directory standard, a read-only compliance audit against it, an additive-only scaffolder that fills exactly the gaps the audit found, and a planning desk under _meta/plans/ holding one build plan per unit of work. The supporting standards ship with it: the project-memory taxonomy whose checklist rows the audit and the scaffold both read, and the item-body form the desk writes tracker items to, carried as a dependency from its topical home in board-desk. The standard, the audit, and the scaffold assume the repo tree is the system of record, so install them only where that is true. The desk is the exception: it reads work items from a tracker through a pluggable adapter, and a Kata adapter ships. Release history: https://github.com/hsb3/dotfiles-agents/releases.

6 skills

0

pocketbase

claudecodex

Build and operate PocketBase backends: an operational skill for driving a running instance (collection and record CRUD, auth, backups, migration generation, Go hooks and custom routes), a design skill of 63 prioritized rules for schema, API rules, auth flows, query performance, realtime, files, and deployment, and three subject-matter agents that carry the backend laws into a delegated brief: a builder, an adversarial reviewer, and a security auditor, each proving its claims from its own clean-room server. Release history: https://github.com/hsb3/dotfiles-agents/releases.

3 skills · 3 agents

0

diagrams

claude

Structural diagrams for repo docs, decks, and briefings, with consistent SVG and PNG output: Mermaid for GitHub-rendered markdown, Python diagrams for cloud architecture with provider icons, draw.io reading and headless export, Excalidraw sketches, and raw Graphviz. Data charts belong to the dataviz skill, deck theming to presentations. Release history: https://github.com/hsb3/dotfiles-agents/releases.

4 skills

0

Build Obsidian plugins against the real API — lifecycle, settings, vault operations, commands, chat and copilot sidebar UIs, in-plugin MCP servers over Streamable HTTP — and automate vaults from the terminal with the official Obsidian CLI. Release history: https://github.com/hsb3/dotfiles-agents/releases.

4 skills

0

Maintain code-desk?

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.

claude & codex plugins12 plugins