← ClaudeAtlas

hldlisted

Write a high level design, the design of one system, service or stream of work that a tech strategy names. Use when asked to design a system or a service, to write an HLD or high level design, or to take a candidate from a strategy. Takes the strategy's path and the candidate, reads the strategy in full before asking anything, asks one round of questions in prose, and writes .ponderly/designs/<strategy-name>/<name>/hld-<name>.md from the plugin's HLD template, with a Mermaid diagram of the components. The document-reviewer agent reads the draft against the template and the strategy before the author sees it; the author approves the document from its path and a summary. Ends with the candidate low level designs, one per component, each written next with the lld skill. 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 high level design A high level design is the design of one system, service or stream of work that a tech strategy names: its scope, its boundary and context, its components and how a request moves through them, and the decisions that shape it. It is written from one candidate of a strategy, and it leads to low level designs, one per component that needs its own design. Turn the strategy 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/hld/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 or the author's words, ask the author. Do not fill a goal, a decision or a trade-off by guessing