design-principles
Design principles for manifest-dev: how its maintainer wants the visual and interaction design guidance the plugin ships, and the surfaces it builds for people to look at, done, and why. Use before planning, writing, building or reviewing the design skills, their guides and instruments, or a page, canvas or draft a skill renders for a person.
How do I install this agent skill?
npx skills add https://github.com/doodledood/manifest-dev --skill design-principlesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a set of design principles and guidelines for creating user interfaces. It contains no executable code, network requests, or sensitive data access.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Edit rule: each line is a principle with its reason and when it yields. Decisions go to the decision records, rules a check can hold go to the check, and a line is added only on a person's yes, after sharpening an existing line is ruled out.
- Design guidance takes its direction from the artifact's subject and the person's moment — who is there, what they came to do, how long they stay, written down where the work shows it with their most pressing question first — and lets that set the structure and how strong the feeling is, and the result is judged against that note; it ships no house style, and a guide describes how a kind of work is used or what a feeling is made of, never a look to apply by kind — catalogs pulled unrelated subjects to one look, guidance blind to the work produced well-made artifacts arranged wrongly for it, and a surface made before anyone wrote down its person's questions ends up answering its maker's. Yields to explicit requirements, an existing design system, and a strength the request names.
- Each screen is led by one thing — what its person came for, or what the project wants from them where that serves the same moment — and where two things compete at the same weight, one is chosen to lead — with no clear place to look first, a person takes in neither. Yields when the screen exists to compare two equal things side by side.
- Each element on a surface stays only for what it does for its person or for what the project wants from them at that moment; anything that serves neither comes off, or moves below what they came for — what is merely present crowds the person and reads as pushing them. Yields for what law, a contract or the person's safety requires to be shown.
- The purpose of a surface is visible before anything is pressed, and whatever the person will ask next about what is in front of them is answered right there; pressing reveals detail, not the purpose itself — someone who scrolls by a collapsed section goes away without the thing they came for. Yields when the point is too large for the space and a summary stands in for it.
- Nothing a person does or meets passes without an answer: each press is done, visibly under way, or declined with its reason, and a state that is empty, loading, failed, out of date or partly saved says so, and why, where it appears — not as blank space, a lone dash or zero, or a control that has vanished — a result that shows nothing looks broken, and a zero asserts something. Holds without a yield.
- On one screen and those next to it, each quantity is counted one way, and every figure states its unit and what it counts — a person faced with two answers spends their attention working out which to believe. Yields when two figures really measure different things; each then gets a label of its own.
- The point of a section is drawn — a figure, a comparison, something to try — before it is written out, so the section is grasped at a glance — people scan, and long paragraphs get skipped. Yields when the drawing itself needs careful study to understand.
- An action a person repeats many times answers at once, with any motion short enough never to hold up the next input, while a moment met now and then may take longer to arrive and leave — motion that delays a repeated action charges a small wait on every use. Yields where longer motion carries meaning the person needs, such as where a moved item went.
- A surface that needs an interaction the product already handles well — or that the best products of its kind do — starts from that version and is raised to its level — people compare new work with the best they have used, and a second version drifts from the first. Yields where the new surface's purpose needs the interaction to differ; then the difference is named.
- A surface people are meant to return to is not done once it is correct: it gives them a reason to want to come back, felt before it is thought — a surface that is correct but flat offers nothing to return for. Yields where that pull would take attention the person's task needs.
- Every control can be reached and worked from the keyboard, carries a name a screen reader announces, and has text contrast and a target size people can read and hit, with what no automatic checker covers checked by hand and that check shown with the change — a surface some people cannot operate fails them entirely. Yields for a throwaway draft made only to get a reaction.
- A surface is designed and checked against the worst real content it will hold — long, empty, numerous, translated, missing — rather than a tidy sample, and that check is shown with the change — real content is what breaks a layout. Yields where the content is fixed and known in full.
Before calling design work done, check it against these principles from a fresh start — a new session, or a reviewer who did not do the work. Fix what departs unless the person chose the departure, and check again only after a fix, until a check finds none. Name each departure kept, with the principle and why.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/doodledood/manifest-dev/design-principles">View design-principles on skillZs</a>