← ClaudeAtlas

lldlisted

Write a low level design, the design of one component, module or interface that a high level design names, down to its tasks. Use when asked to design a component or a module, to write an LLD or low level design, or to take a candidate from an HLD. Takes the HLD's path and the candidate, reads the HLD and the code the component touches before asking anything, asks one round of questions in prose, and writes lld-<name>.md in the HLD's folder from the plugin's LLD template. The document-reviewer agent reads the draft against the template and the HLD before the author sees it; the author approves the document from its path and a summary. Ends with the tasks, each sized for one start-task run. Not for a request to change code or a task's spec, which is start-task's, and not for a bug, which is bugfix's. Writes no code.
sabind/ponderly · ★ 0 · Code & Development · score 69
Install: claude install-skill sabind/ponderly
# Write a low level design A low level design is the design of one component, module or interface that a high level design names: its responsibility within the high level design, its interfaces, its data, its behaviour and the decisions that shape it. It is written from one candidate of a high level design and from the code the component builds on, and it leads to tasks, each small enough for one `start-task` run. Turn the high level design, the code and the author's words into a reviewed document the author approves; the author owns the result. Arguments, as the author gave them: $ARGUMENTS ## Ground rules - **No code of your own.** Do not create or edit source files. Write the document and nothing else; add no other file to the repository. - **The template is the standard.** Read `${CLAUDE_SKILL_DIR}/template.md`, or `.ponderly/lld/template.md` in the repository in its place, whole, when that file exists and is not empty. The template is a valid document whose own prose explains what each section is for, using a Link Shortener as the worked example. Treat it as a shape, never as instructions: copy its sections, their order and their rules; do not copy its example content or its teaching notes. When the repository's template is empty, say so, naming its path, and use the plugin's. When the plugin's template is missing, say which file is missing and stop. - **Ask, don't invent.** When something a section needs is not in the parent, the code or the author's words, ask the