creedants
10 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
creedantscorrect
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantslanding
Let many agents write to one repository at once without collisions: a per-repository landing contract, path leases claimed before work starts, one queue that is the only writer to trunk, and a machine-wide slot governor for builds and tests. Use for 'landing', 'land this', 'merge queue', 'many agents on one repo', 'where does this work land', or before any coordinator (brigade, Orchestrate, Autopilot, swarm) delegates writing work in parallel.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-foundational-thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-minimize-reader-load
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-never-block-on-the-human
Apply when tempted to ask 'should I do X?' on reversible work.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsprinciple-sequence-verifiable-units
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11
creedantsshow-me-your-work
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
- installs
- 1
- GitHub stars
- 5
- Updated
- Oct 11