UI/UX, logos, slides, and image generation (7.3K skills)
Load when editing Blazor `.razor.css`, scoped selectors, `::deep`, BEM class names, RTL/logical CSS properties, or styling nested MudBlazor components; not for global design tokens or non-Blazor CSS.
The English summary is being prepared. Showing the original description.
Load for footer settings, templates, social/legal links, copyright, tenant customization, instance governance locks, footer HAL capabilities, or footer admin UI/API changes; not for generic page layout footers.
The English summary is being prepared. Showing the original description.
Load for authentication or authorization changes involving BFF cookies/tokens, JWT validation, claims/user ID extraction, policies, handler access checks, impersonation, or 401/403 bugs; not for UI affordance gating alone.
The English summary is being prepared. Showing the original description.
Load for global UI-system changes involving CSS `@layer`, primitive/semantic/component tokens, themes, reusable MudBlazor wrappers, or design-token governance; not for one component's isolated CSS.
The English summary is being prepared. Showing the original description.
Load when creating, editing, or debugging Lottie/Bodymovin JSON for the local Skia Skottie player: logo/type/SVG animation, loaders, icons, UI microinteractions, lower thirds, charts, diagrams, scene motion, effects, slots, or controls; not for static raster/SVG, CSS-only motion, or video editing.
The English summary is being prepared. Showing the original description.
Create a new App Store Connect app record via browser automation. Use when there is no public API for app creation and you need an agent to drive the New App form.
The English summary is being prepared. Showing the original description.
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.
The English summary is being prepared. Showing the original description.
Collapse meaningful ambiguity with contrastive examples. Use when a plan/design has several plausible meanings, requirements feel vague, examples would clarify intent faster than grilling, or the user asks to disambiguate, find ambiguity, use behavioral kernels, or ask contrastive questions.
The English summary is being prepared. Showing the original description.
Throwaway design probe for logic, state models, UI variations, and affordances before production work. Use when the user wants to prototype, sanity-check a model, make something playable, compare UI directions, or explore a design before ln-spec/ln-plan/ln-scope.
The English summary is being prepared. Showing the original description.
Explore radically different module shapes before committing to one. Use when choosing an API surface, deciding what a module hides vs exposes, or when the user says 'design it twice'.
The English summary is being prepared. Showing the original description.
Review someone else's PR through an architectural/strategic lens — does it shift design, raise complexity, or quietly change precedent? Drives a brief reflective discussion with the user, then posts a concise review comment via `gh`. Defers line-level and bug-hunting concerns to AI review bots and the PR author.
The English summary is being prepared. Showing the original description.
Use when starting/stopping the Remote Web UI on port 8901.
The English summary is being prepared. Showing the original description.
Throwaway HTML mockups: 2-3 design variants to compare.
The English summary is being prepared. Showing the original description.
Control TouchDesigner via twozero MCP.
The English summary is being prepared. Showing the original description.
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
The English summary is being prepared. Showing the original description.
Author/validate/export Google's DESIGN.md token spec files.
The English summary is being prepared. Showing the original description.
Design one-off HTML artifacts (landing, deck, prototype).
The English summary is being prepared. Showing the original description.
We need to find the structural connection between the two described situations. The user gave two bu GAP: OpenHands has a modular SDK design — our too
The English summary is being prepared. Showing the original description.
[TOOL_RESULT:web_search] {"results": "Why Most AI Systems Fail at Scale: Problem faced with … :: 12. GAP: OpenHands has a modular SDK design — our too
The English summary is being prepared. Showing the original description.
They re context management, tool design, policy gates, memory strategies and, if you want to run loc
The English summary is being prepared. Showing the original description.
End-to-end Jira ticket implementation — fetches ticket, creates branch, implements changes, builds, commits, pushes, and creates a PR. Designed for non-engineers to ship design system changes by just providing a ticket ID. Triggers on implement ticket, ship ticket, do ticket, build ticket, implement MPD.
The English summary is being prepared. Showing the original description.
Turn an authorized 2D logo into an approved visual treatment and animate a controlled brand reveal while preserving the mark.
The English summary is being prepared. Showing the original description.
Signpost (not a knowledge pack) for the systems-engineering standards landscape — ISO/IEC/IEEE 15288, 24748, 29148, 42010, 15026, 24765; INCOSE SE Handbook & Vision 2035; OMG SysML; SAE/EIA 1001/649/748; ECSS space standards; NATO AAP-48; CMMI; NIST SP 800-160; and more. Contains NO source content: it lists each standard's designation, title, purpose, owning SDO, whether it's redistributable, and where to get it. Use when you need to identify or locate an SE standard — most are paywalled/all-rights-reserved and cannot be packaged, so this points you to the owner (and to the open packs where one exists).
The English summary is being prepared. Showing the original description.
Knowledge base from the NASA Fault Management Handbook (NASA-HDBK-1002, Draft 2, April 2012). Use for the systems-engineering discipline of designing what a system does when it fails — the fault/failure/anomaly vocabulary, the five FM strategies (two prevention strategies — design-time fault avoidance and operational failure avoidance — plus three tolerance strategies — failure masking, failure recovery, and goal change), the six FM process activities across NASA mission phases Pre-A to E, response-latency-versus-time-to-criticality (TTC) design trades, fault/failure containment regions and FEPPs, the four redundancy approaches, top-down FM requirements development, FM verification vs. validation, the seven dedicated FM milestone reviews (FMCR/FMARR/FMPDR/FMCDR/FMTRR/FMLRR/FMCERR), FM organizational structure, and mined NASA Lessons Learned. Space-mission oriented (flight/ground/operations); spacecraft examples throughout. IMPORTANT: built from an UNAPPROVED DRAFT — several sections (detailed architecture building blocks, the Assessment & Analysis guidance, and Operations & Maintenance) are placeholders in the source and are thin here. Thin on detailed FDIR algorithms, terrestrial/IT fault management, and any approved-standard terminology that may have changed since Draft 2.
The English summary is being prepared. Showing the original description.