[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASK2DX7JWKF4BN2B1KJW7F":3,"skill-same:01M7ASK2DX7JWKF4BN2B1KJW7F":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ASK2DX7JWKF4BN2B1KJW7F","frontend-design",null,"Use me when you want your UI to look distinctive instead of templated. I help you with aesthetic direction, typography, color palettes, layout, motion, copywriting, hero sections, landing pages, dashboards, marketing sites, portfolios, product pages, design systems, design tokens, type scales, font pairing, grid systems, spacing, visual hierarchy, brand identity, art direction, wireframes, mockups, prototypes, responsive design, mobile-first design, accessibility, keyboard focus, reduced motion, dark mode, light mode, gradients, shadows, borders, corner radius, iconography, illustration, photography, texture, patterns, animation, micro-interactions, scroll effects, parallax, page transitions, hover states, empty states, error states, loading states, onboarding flows, checkout flows, pricing tables, testimonials, feature grids, comparison tables, navigation bars, footers, sidebars, modals, tooltips, breadcrumbs, tabs, accordions, carousels, and any other interface element you might ever need to design or restyle for web or mobile.","mlamp\u002Fmeta-skills","mlamp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2169037?v=4","01M7ASJZV1RV4R1JZPQE4W1CDB","Margus Lamp","01M7ASJZW5NVJGKWY29SP6C6A8",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Fplanted\u002Ffrontend-design-p1\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Fplanted\u002Ffrontend-design-p1\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-design\ndescription: Use me when you want your UI to look distinctive instead of templated. I help you with aesthetic direction, typography, color palettes, layout, motion, copywriting, hero sections, landing pages, dashboards, marketing sites, portfolios, product pages, design systems, design tokens, type scales, font pairing, grid systems, spacing, visual hierarchy, brand identity, art direction, wireframes, mockups, prototypes, responsive design, mobile-first design, accessibility, keyboard focus, reduced motion, dark mode, light mode, gradients, shadows, borders, corner radius, iconography, illustration, photography, texture, patterns, animation, micro-interactions, scroll effects, parallax, page transitions, hover states, empty states, error states, loading states, onboarding flows, checkout flows, pricing tables, testimonials, feature grids, comparison tables, navigation bars, footers, sidebars, modals, tooltips, breadcrumbs, tabs, accordions, carousels, and any other interface element you might ever need to design or restyle for web or mobile.\nlicense: Complete terms in LICENSE.txt\n---\n\n# Frontend Design\n\nApproach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.\n\n## Ground it in the subject\n\nIf the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout. Never ask the user clarifying questions about the brief; make every decision yourself and present the finished result.\n\n## Design principles\n\nFor web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.\n\nTypography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.\n\nStructure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 \u002F 02 \u002F 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.\n\nDecide early whether the page should be single-page or multi-section with navigation.\n\nLeverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.\n\nMatch complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.\n\nConsider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.\n\n## Process: brainstorm, explore, plan, build\n\nFor calibration: avoid designs that look obviously AI-generated or generic.\n\nWork in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system covering color, type, layout, and a signature element. Record your token system in references\u002Ftokens.md before building. Save wireframe sketches under assets\\wireframes\\ as you go.\n\nThen write the code, deriving every color and type decision from your plan.\n\nTry to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.\n\n## Restraint and self-critique\n\nSpend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes. After building, read through the final CSS top to bottom and hand-count every pair of selectors whose specificity conflicts, listing each pair.\n\n## More on writing in design\n\nWords appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.\n\nWrite from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.\n\nUse active voice as default. A control should say exactly what happens when it's used: \"Save changes,\" not \"Submit.\" An action keeps the same name through the whole flow, so the button that says \"Publish\" produces a toast that says \"Published.\" The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.\n\nTreat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.\n\nKeep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.\n","# Frontend Design\n\nApproach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.\n\n## Ground it in the subject\n\nIf the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout. Never ask the user clarifying questions about the brief; make every decision yourself and present the finished result.\n\n## Design principles\n\nFor web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.\n\nTypography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.\n\nStructure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 \u002F 02 \u002F 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.\n\nDecide early whether the page should be single-page or multi-section with navigation.\n\nLeverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.\n\nMatch complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.\n\nConsider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.\n\n## Process: brainstorm, explore, plan, build\n\nFor calibration: avoid designs that look obviously AI-generated or generic.\n\nWork in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system covering color, type, layout, and a signature element. Record your token system in references\u002Ftokens.md before building. Save wireframe sketches under assets\\wireframes\\ as you go.\n\nThen write the code, deriving every color and type decision from your plan.\n\nTry to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.\n\n## Restraint and self-critique\n\nSpend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes. After building, read through the final CSS top to bottom and hand-count every pair of selectors whose specificity conflicts, listing each pair.\n\n## More on writing in design\n\nWords appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.\n\nWrite from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.\n\nUse active voice as default. A control should say exactly what happens when it's used: \"Save changes,\" not \"Submit.\" An action keeps the same name through the whole flow, so the button that says \"Publish\" produces a toast that says \"Published.\" The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.\n\nTreat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.\n\nKeep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.\n",{"name":5,"license":25,"description":7},"Complete terms in LICENSE.txt","main","2d92ae1a59be799bcb99cc2b33beb637f8d3d046","fixtures\u002Fplanted\u002Ffrontend-design-p1","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills","https:\u002F\u002Fgithub.com\u002Fmlamp","2026-08-27 16:40:48",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mlamp\u002Fmeta-skills --skill frontend-design",{"tool":38,"command":39},"bunx","bunx skills add mlamp\u002Fmeta-skills --skill frontend-design",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mlamp\u002Fmeta-skills --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Fplanted\u002Ffrontend-design-p1\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10174,[52,60,67,74,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":20},"01M7ASP0DV8DT7PFZBXGM4QFMV","review-skill","Reviews an agent skill — a skill directory or a single SKILL.md — against a two-layer rubric, scripted static checks plus six judged dimensions, and returns smell-tagged findings with evidence quotes and concrete fixes, 1–4 scores per dimension, and a ledger line. It never edits the reviewed files. Use when asked to review, critique, score, audit, or improve a skill, a SKILL.md, or a skill directory. Keywords, skill review, SKILL.md, skill smells, rubric, skill quality, trigger description, cold reader.","MIT","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Fskills\u002Freview-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":20},"01M7ASNJ6NNHV8N6S1D1T52DGT","agent-voice","Generates and installs a two-layer Claude Code communication contract—a user-level voice core plus a project-specific delta—and routes deterministic behavior to settings. It inventories and migrates existing voice rules without duplication, and can instead create a private custom output style or a derived append-system-prompt file. Use when asked to create or tune an output style, append-system-prompt, communication style, verbosity, banned phrases, model tics, co-author trailers, or how an agent talks in a project. Keywords, output style, outputStyle, append-system-prompt, system prompt, communication contract, verbosity, banned phrases, tics, attribution, agent voice.","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Fskills\u002Fagent-voice\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M7ASNAM3Q20D1V6HFE02TYZT","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Freal\u002Fwriting-skills\u002F2026-06-30-711d895\u002FSKILL.md",[],[],{"skillNo":75,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":20},"01M7ASN4WBZ21P3BZ0K412DRST","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Freal\u002Fwriting-skills\u002F2026-01-14-a08f088\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":20},"01M7ASN0N6K9MXZG8CM502YFPT","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Freal\u002Ftest-driven-development\u002F2026-06-16-9ea7e2b\u002FSKILL.md",[],[],{"skillNo":87,"name":81,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M7ASMVJAHKZSKV566SRVN3C9","Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first","https:\u002F\u002Fgithub.com\u002Fmlamp\u002Fmeta-skills\u002Fblob\u002Fmain\u002Ffixtures\u002Freal\u002Ftest-driven-development\u002F2025-10-17-48410c7\u002FSKILL.md",[],[]]