codex/skills/algebra-driven-design/SKILL.md
Apply Algebra-Driven Design from `codex/algebra-driven-design`. Use for ADD, denotational design, combinator models, law-driven architecture, domain algebra, property tests, codebase modeling, event sourcing, workflow design, or agentic skill design.
npx skillsauth add tkersey/dotfiles algebra-driven-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This loadable skill wrapper exists so local Codex skill discovery can find algebra-driven-design under codex/skills/ while the canonical knowledge-rich bundle remains at:
codex/algebra-driven-design
Before using the skill, read:
codex/algebra-driven-design/SKILL.md
Then load deeper references from the canonical bundle as directed there.
Use ADD for domain algebra: carriers, operations, observations, laws/non-laws, effects, interpreters, law-derived architecture, and law tests.
Use kan instead when the central problem is a boundary equation: extension across K, lift through P, defunctionalized boundary IR, Yoneda/Coyoneda representation, or categorical witness tests.
tools
Convert markdown plans into beads with dependencies using br CLI. Use when creating task graphs, polishing beads before implementation, or bridging planning to agent swarm execution.
development
Orchestrate Codex skill optimization during active sessions through $cas goal control, $shadow single-session evidence, $tune diagnosis/refinement briefs, and the skill-optimizer custom subagent. Trigger for $opt, skill optimization loops, session-driven skill tuning, meta-skill audits, or explicit validated skill edits. Do not use for general code optimization, product optimization, or performance tuning.
development
Run a targeted fresh-eyes blunder pass over code, specs, plans, adjudications, closure gates, skill edits, or negative-evidence ledgers. Trigger when asked to reread with fresh eyes, find obvious bugs, catch mistakes/oversights/omissions, check for embarrassing misses, or perform a second independent blunder pass before closure. Do not use as a substitute for implementation, adjudication, or verification; use it as the final falsification/check pass for those workflows.
development
Explicitly shadow, tail, watch, follow, monitor, supervise, or companion exactly one Codex session id/path through `$seq`, then apply a named target skill as an interpretation/reporting/proposal/action lens until the watched session stops.