hld
Skill0 starsChanged 30 days agoNo licenceView on GitHub
Write a High-Level Design (Technical Design) end to end, from epic to a reviewed Confluence page with Excalidraw diagrams and linked Jira tickets. Follows the team's Technical Design template section for section and orchestrates the epic-breakdown, excalidraw-diagrams, confluence and ticket-enricher skills. Trigger on "write the HLD for <epic>", "technical design for this epic", "start an HLD", "design doc for <feature>", or when an epic plus PRD/Figma is given and a design is needed before implementation. Skip for a single small ticket that needs no design (use ticket-enricher for a per-ticket HLD comment instead).
In this repository25 other files it gives its agents.
- backend-pythonSkill
- bug-triageSkill
- codepilot-be-nestjsSkill
- codepilot-be-nextjsSkill
- codepilot-be-pythonSkill
- codepilot-beSkill
- codepilot-ui-angularSkill
- codepilot-ui-reactSkill
- codepilot-uiSkill
- code-review-defaultSkill
- confluenceSkill
- devloopSkill
- epic-breakdownSkill
- excalidraw-diagramsSkill
- feature-composerSkill
- first-daySkill
- frontend-patternsSkill
- last-daySkill
- output-validatorSkill
- pr-radarSkill
- sprint-pulseSkill
- ticket-enricherSkill
- unit-testingSkill
- vibe-coderSkill
- webcodeSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.