All authors
Claude Skills by zakyrion
github.com/zakyrion11 skills0 installs10 views
- Sdd Algorithm LiftLift the algorithm out of existing code that does not read — machine-generated, tangled or simply foreign — into one Clojure document a person can take in — the algorithm as the code performs it, in the words of the task, with bugs, inaccuracies and dangling tails flagged; bound to the code by a code map, or clean without it. Use when the user invokes sdd-algorithm-lift or /sdd-lift, or asks outright to recover, extract or explain the algorithm of code that already exists.Votes: 0GitHub stars: 2
- Sdd Algorithm SketchWork out an algorithm in Clojure instruction notation — a spine of one-phrase steps and its data as one document, amended in discussion until the owner agrees, then one question about what happens next — keep it, write the code, continue as a cascade, or derive another form. Standalone, and the cascade's algorithm step. Use when the user invokes sdd-algorithm-sketch or /sdd-sketch, when the cascade reaches its algorithm step, or when the user asks outright to sketch, draft or think through an...Votes: 0GitHub stars: 2
- Sdd CascadeCarry a large refactoring, or a new system whose algorithm must be invented, through a short chain of standalone skills — survey the code with the project's tools, optionally source the rules, agree the algorithm, agree the structure, translate it into code in a fresh agent, review by running the project's checks. Three gates are the owner's word; decisions live in one register. Use when the lifecycle marks a task :path :cascade, when the user invokes sdd-cascade or /sdd-cascade, or when a ca...Votes: 0GitHub stars: 2
- Sdd Clojure FlowNormalize prose or Clojure engineering requests into canonical Clojure instruction IR and enforce the persistent Research → Plan → Execute lifecycle. Use for engineering tasks, implementation requests, architecture or documentation changes, FLOW creation, resuming interrupted work, acceptance checks, or whenever the user invokes sdd-clojure-flow.Votes: 0GitHub stars: 2
- Sdd Deep ResearchRun a source-verified research pass on questions with no fast right answer — trade-off spaces such as terrain generation, netcode synchronization, or service architecture. Search real sources, establish the conditions each solution holds under, weigh claims by verified evidence instead of the agent's priors, and deliver a trade-off map. A light sources mode finds the primary source of every rule a design leans on and whether a ready solution exists. Use when the user invokes sdd-deep-research...Votes: 0GitHub stars: 2
- Sdd Project InitSurvey a project that already has its own documents, tools, ceremonies and rules, then integrate sdd-flow with them instead of replacing them. Writes the project-owned adapter, proposes at most one removable pointer into a document the project owns, and never edits an agent doc without the owner's confirmation. Use when adopting sdd-flow in an existing project, when the project's ceremonies should drive the lifecycle, or when a project carries a hand-maintained copy of the framework canon.Votes: 0GitHub stars: 2
- Sdd Code ReviewCheck that a change does what the task asked by running the project's own meters and checks — build, tests, the checks the project registers — and reading each row of the task's acceptance, then give the behavior verdict with the level every failure returns to. Works on any code, not only after the cascade. Use when the user invokes sdd-code-review or /sdd-review, or as the last step of the cascade after the translation reports.Votes: 0GitHub stars: 2
- Sdd Code StructureTurn an agreed algorithm into the structure of the code — the entry point as a table of contents, the methods, the data with its lifetime and real types — written as the one document another agent translates into code, with the build facts and traps it needs. Use when the user invokes sdd-code-structure or /sdd-structure, or as the structure step of the cascade after the algorithm is agreed.Votes: 0GitHub stars: 2
- Sdd Code SurveySurvey what the code and the project already say about a task — with the project's own tools first, through the tool skills generated for this project (graphs, language servers, MCP servers, CLIs), grep and file reading last and only with a reason — and stop when every question of the task has an answer or has become a question for the owner. Use when the user invokes sdd-code-survey or /sdd-survey, as the first step of the cascade, or as the first leg of the lifecycle's research.Votes: 0GitHub stars: 2
- Sdd Code TranslationWrite the code from an agreed structure document alone, in a fresh agent in another session than the discussion — one agent, or several for parts that write disjoint files — and return a short report of what was written, what ran, and what the code added beyond the structure. Use when the user invokes sdd-code-translation or /sdd-translate with a structure document, or as the translation step of the cascade after the structure is agreed.Votes: 0GitHub stars: 2
- Sdd Tool SkillsTurn a project's own search tools into small generated skills, one per kind of question — "who calls this symbol", "who writes this component", "where is this asset used" — each an order with its reason and a verified call, so the agent reaches for the tool at the moment it chooses instead of grepping. Scans what the session and the project offer, or asks the owner directly; keeps a registry of the generated skills to change, re-check or delete them. Use when the user invokes sdd-tool-skills ...Votes: 0GitHub stars: 2