Design & frontend
15,938 rows, by stacks then stars
1,697 of these skill files have been read, by 1,179 distinct authors, and what they tell an agent counted. What Design & frontend authors agree on, and what they forbid
rakibulism/agent-skills-os/skills/design-user-research Skill
2★ repoPlan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.
The same file is in 46 other repositories
rakibulism/agent-skills-os/skills/design-ux-copy Skill
2★ repoWrite or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.
The same file is in 3 other repositories
rakibulism/agent-skills-os/skills/elite-website-ux-ui-designer Skill
2★ repoBecome (or evaluate) an elite website UX/UI designer — the specific mindset, frameworks, and pixel-level standards that separate the top 1% from the rest, distilled into 14 reference files covering psychology, systems, visual craft, conversion, and deliberate practice. Use this skill whenever the user is designing, reviewing, or critiquing a website/landing-page/web-app UI; asks "what makes a great UX/UI designer"; needs a design-system, typography scale, grid, or color framework; is optimizing a page for conversion; is preparing a stakeholder pitch for a design change; or wants a structured practice regimen (deconstruction, storyboarding, personal challenges) to level up. Complements the design-engineer skill (which owns animation-as-code, GPU/rendering performance, and frontend architecture) by owning the design-decision layer — why a layout, palette, or copy choice is correct, not how to implement it in a render loop.
rakibulism/agent-skills-os/skills/figma-figma-design-to-code Skill
2★ repo**MANDATORY prerequisite** — you MUST invoke this skill BEFORE calling the `get_design_context` Figma MCP tool. You MUST trigger this skill whenever the user wants to implement, build, port, or code up a Figma design as code. Example prompts (not exhaustive) are 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'design to code'. This skill provides critical instructions and steps to the agent on how to correctly implement Figma designs in code and must NOT be skipped.
rakibulism/agent-skills-os/skills/figma-figma-generate-design Skill
2★ repoUse this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/figma-figma-generate-library Skill
2★ repoBuild or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, and design token bindings to be production-quality. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/figma-figma-implement-motion Skill
2★ repoTranslates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/figma-figma-use-motion Skill
2★ repoMotion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/frontend-design Skill
2★ repoGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/frontend-performance-engineer Skill
2★ repoProfiles and fixes frontend performance — frame drops, layout thrashing, memory leaks, Core Web Vitals, and asset/bundle budgets — for animation-heavy or visually rich sites. Use when a site feels slow or janky, before shipping an animation-heavy page, or when setting performance budgets and CI checks.
rakibulism/agent-skills-os/skills/interaction-designer Skill
2★ repoDesign micro-interactions, transitions, and animations — what moves, why, how long, with what easing. Produces an interaction spec with timing, easing, and triggers, plus the CSS/Framer/animation code if requested. Use when the user asks to design an animation, add micro-interactions, make something "feel alive," or improve perceived performance.
rakibulism/agent-skills-os/skills/interactive-web-engineer Skill
2★ repoPlans and reviews award-tier interactive web experiences — hero sections, portfolio sites, animation-heavy landing pages — balancing visual craft against real frame-budget constraints. Use as the entry point for any "make this feel premium / Awwwards-style / interactive" request; routes to motion-design-engineer, webgl-creative-coder, frontend-performance-engineer, or animated-component-architect for the deep technical work.
rakibulism/agent-skills-os/skills/motion-design-engineer Skill
2★ repoDesigns physically-feeling motion — spring-based animation, drag with momentum, flick-to-dismiss, rubber-banding, and custom easing curves. Use when an animation "feels robotic," when building draggable/swipeable interactions, or when translating a storyboard into concrete timing and physics parameters.
rakibulism/agent-skills-os/skills/motion-graphics Skill
2★ repoDesign titles, lower thirds, captions, and animated graphics for video — what moves, when, and why, with legibility and timing that respect the edit. Produces a graphics spec with hierarchy, animation timing/easing, safe-area and legibility notes. Use when the user asks to design titles, lower thirds, captions/subtitles, an intro/outro, kinetic typography, or animated overlays.
rakibulism/agent-skills-os/skills/premium-restraint-web-design Skill
2★ repoDesign (or critique) a "quiet luxury" premium-hardware/consumer-object web presence — the near-monochrome, single-typeface, generously-spaced visual language used by brands like Apple, Teenage Engineering, and Aesop, where color comes only from photography and restraint itself is the persuasion device. Also teaches the general method for turning a reference design (a screenshot, a competitor site, a mood board) into hard, enforceable design tokens instead of vague "inspiration." Use this skill whenever the user wants a landing page for a premium/luxury physical product, says a design "looks cheap" or "looks like a generic SaaS template," asks for an Apple/Rams/Teenage-Engineering-style aesthetic, wants to reproduce a specific reference site's exact taste level, or is choosing colors/type/spacing for anything positioned as a serious, adult, non-playful object rather than a wellness app or startup tool.
rakibulism/agent-skills-os/skills/product-designer Skill
2★ repoConnect user problems to product decisions — frame the problem, size the opportunity, define success metrics, scope an MVP, and map the solution space before any screen is drawn. Produces product-design artifacts (problem statements, opportunity maps, scoping cuts, success metrics, design rationale) that align design, product, and engineering. Use this skill whenever the user is deciding WHAT to build or WHY, prioritizing features, scoping an MVP, defining metrics or success criteria, writing a design or product brief, running discovery, or asking "is this worth building," "what should we build first," or "how do we measure if this worked" — distinct from pure UI/visual work.
rakibulism/agent-skills-os/skills/seo-sxo Skill
2★ repoSearch Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/shadcn-ui Skill
2★ reposhadcn/ui component patterns with Radix primitives and Tailwind styling. Use when building UI components, using CVA variants, implementing compound components, or styling with data-slot attributes. Triggers on shadcn, cva, cn(), data-slot, Radix, Button, Card, Dialog, VariantProps.
rakibulism/agent-skills-os/skills/sound-design Skill
2★ repoDesign and mix the audio for video — dialogue, music, ambience, and effects — into a clean, leveled mix. Produces a layered audio plan with level targets (LUFS/dBFS), EQ/processing notes, and a mix order. Use when the user asks to mix audio, fix muddy or quiet sound, add music or sound effects, design a soundscape, or master a video for a platform.
rakibulism/agent-skills-os/skills/theme-factory Skill
2★ repoToolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
The same file is in 46 other repositories
rakibulism/agent-skills-os/skills/ux-copywriter Skill
2★ repoWrites and reviews UX copy — microcopy, error messages, empty states, buttons, and confirmation dialogs. Use when naming a CTA, wording an error message, filling an empty state, or writing onboarding text.
rakibulism/agent-skills-os/skills/ux-designer Skill
2★ repoExpert UX design thinking, user psychology, and experience strategy. Activates when building, reviewing, or discussing any user-facing interface -- websites, apps, dashboards, forms, onboarding, checkout, sign-up, settings, landing pages, modals, navigation. Triggers on: user flows, wireframes, prototypes, usability, information architecture, content strategy, error handling, accessibility, interaction design, user testing, conversion. Also activates on: 'how should this flow', 'user experience', 'make it easier', 'onboarding', 'conversion', 'drop-off', 'friction', 'confusing', 'intuitive', 'usability', 'user journey'. Applies whenever a human uses an interface, even without saying 'UX'. Hands off to ux-copywriter for detailed microcopy work and to ui-designer for visual styling. Do NOT activate for purely visual styling, backend logic, database schemas, API design without UI, or DevOps.
rakibulism/agent-skills-os/skills/ux-expert-rakibulism Skill
2★ repoReview UI screens, dashboards, modals, tables, and flows as a UX expert speaking in "rakibulism" — Rakibul's curated professional communication style for client-facing design feedback. Use this skill whenever the user uploads a UI screenshot or design and asks to find UX issues, review a screen, critique a design, comment on a file, or give client-facing feedback. Also trigger when the user says "review this", "find issues", "comment on this", "tell it like me", "rakibulism", or wants feedback written as designer-to-client comments that will be fixed later in a design pass.
rakibulism/agent-skills-os/skills/ux-ui-designer Skill
2★ repoDesign and critique end-to-end user experiences and interfaces — flows, information architecture, layout, visual hierarchy, and interaction patterns. Produces concrete artifacts (flows, wireframe specs, UI critiques) an engineer or designer can act on. Use this skill whenever the user is designing or reviewing a screen, app, website, dashboard, form, onboarding, checkout, navigation, modal, or settings page, or says things like "how should this flow," "make it more intuitive," "reduce friction," "improve the UX," "review this UI," or "design the interface" — even if they don't say "UX" or "UI" explicitly.
rakibulism/agent-skills-os/skills/visual-polish-reviewer Skill
2★ repoReview UI screenshots or code for visual polish — alignment, spacing rhythm, typography, color contrast, shadows, borders, and micro-details that separate "fine" from "feels great". Produces a prioritized punch list of fixes with concrete CSS/token changes. Use when the user says the UI "feels off", asks for a polish pass, or wants a design QA before shipping.
rakibulism/agent-skills-os/skills/web-artifacts-builder Skill
2★ repoSuite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
The same file is in 33 other repositories
rakibulism/agent-skills-os/skills/webgl-creative-animator Skill
2★ repoBecome an elite creative WebGL thinker — the mental framework, mathematical grounding, and technique library behind world-class generative/interactive graphics (Awwwards-tier sites, Shadertoy demos, GPU art installations). Covers systems-based thinking over keyframe animation, the five signature technique families (raymarched SDFs, GPGPU particle simulation, vertex noise displacement, post-processing, fluid dynamics), the required tech stack (GLSL, Three.js/R3F, vanilla WebGL2), and a daily training regimen. Use whenever the user wants to design an original WebGL/shader animation, is stuck thinking in DOM/CSS-keyframe terms instead of GPU-system terms, wants to build a creative-coding portfolio, or asks "how do I get good at this" for shader/particle/fluid work. Complements the design-engineer skill's Track 3 (de3-glsl-shaders) and Track 9 (webgl-motion-stack/wgl-*) reference files by supplying the conceptual model and the specific formulas those references assume.
rakibulism/agent-skills-os/skills/x-design-captions Skill
2★ repoWrite X (Twitter) captions for design work — SaaS dashboards, websites, mobile app UI, logos, components, data viz. Use whenever the user is about to post a design to X and needs a caption, mentions "caption for", "posting this on X", "write a caption", or shares a design shot and asks what to say. Always asks which style (Provocation / Education / Proof) before writing, then returns exactly 5 options.
IamK77/Skill/skills/atelier/graphics Skill
2★ repoThe advanced visual layer for a frontend build — where icons, imagery, Canvas, WebGL, GPU, and generative technique live, and "three.js because it looks cool" gets decided. Use after the core visual language is set, when auditing the graphics layer, or when a UI has mismatched icons, layout-shifting images, or GPU surfaces that drain the budget. The one shift: the DOM is the default and the budget — you drop to Canvas / SVG / WebGL / GPU only where the DOM genuinely cannot go, always with a fallback and a budget, and icons come from ONE coherent set — the agent reaches for the GPU as a reflex, mixes icon families, and lazy-loads the LCP hero, feeling no wrongness, so these are gated. Triggers on "icon / icon set / SVG icon / aria-hidden", "image / hero / LCP / CLS / srcset / lazy load / AVIF / WebP / blurhash / illustration", "canvas / WebGL / WebGPU / three.js / shader / GLSL / SDF / raymarching / GPU / generative / procedural / data visualization / retina / devicePixelRatio / blurry canvas".
IamK77/Skill/skills/atelier/layout Skill
2★ repoThe composition lens for a frontend build — where hierarchy, grid, measure, and spatial rhythm are decided, and "looks amateur" / "won't scale to real data" are determined. Use after the build works (seaworthy) and alongside canon's gates, when auditing a surface's composition. The one shift: hierarchy and the grid are DECISIONS, not accidents — the page is *composed*, the empty/loading/edge states have a designed form, and the surface is built for reality's long tail — the agent stacks boxes that "work" and leaves the rest to chance, so it must be gated. CSS mechanism stays in surface:keel; this owns the composition *judgment*. Triggers on "layout / grid / composition / hierarchy / measure / line length / reading column", "spacing / rhythm / density / proximity", "empty state / blank slate / loading state / skeleton / placeholder", "form layout / validation visual", "overflow / truncation / long text / huge numbers", "RTL / i18n layout", "state machine / hover / focus / active / disabled".
IamK77/Skill/skills/atelier/motion Skill
2★ repoThe motion, gesture & feel lens for a frontend build — where every animation earns its place and the feel IS the product. Use after the build works, when adding interaction physics, when a UI feels sluggish / janky or the gesture fights the scroll, or auditing animations. The one shift: every animation maps to a PURPOSE and its dynamics come from physics (spring vs easing, never confused); the feel is the product; compositor- only properties + a real reduced-motion path are non-negotiable — the agent animates because it can, feeling none of the jank, so motion must be gated. Triggers on "animation / transition / motion / spring / damping / bounce / easing / physics", "gesture / drag / scroll / swipe / scroll-vs-drag", "feels laggy / disconnected / jank / stiff / floaty", "prefers-reduced-motion / a11y", "FLIP / View Transitions / scroll-driven", "60fps / compositor / layout thrashing / will-change", "feels native / hand-feel / touch / stagger / orchestration / shared element / morph".
IamK77/Skill/skills/atelier/pilot Skill
2★ repoNavigate the atelier design-craft suite: given a visual-design task, route to the right lens — and the right ENTRY lens — or to a sibling suite, or say plainly when none fits. The un-gated front door to the eight atelier lenses: canon, color, type, layout, form, graphics, motion, systems. Use when starting or part-way through visual design, unsure which lens fits or whether the suite is needed. The shift: "make it look good" is not one decision — it is a small SYSTEM of quantified choices, and the highest-value routing names WHERE to enter the layered system, not always canon. Triggers on "make this look premium / high-end", "feels cheap / generic / AI-default", "which design skill / where do I start", "redesign this UI". Also redirects ACROSS suites: CSS/Grid mechanics → surface:keel; what to build / mental model / dark pattern → surface:bearings; state & data → surface:wellspring; a11y / perf → surface:seaworthy; code craft / testing / security → engineering; realtime → distributed; library → quarry.
IamK77/Skill/skills/atelier/systems Skill
2★ repoThe design-system lens for an atelier build — where tokens, components, and patterns become one coherent, non-drifting artifact, and "design says one thing, code does the other" is decided. Use after the other atelier lenses have produced their tokens, when auditing a token architecture, or when a component library rots. The one shift: the design system is itself STATE, so it gets ONE source of truth — tokens cross the CSS↔JS boundary from one source, the library is a living artifact, design→code does not drift — the agent re-types tokens per file and lets the system rot, so this is gated. Hands the boundary-enforcement contract to surface:bulwark at 1→N. Triggers on "design system / token architecture / token source of truth / @layer tokens / CSS↔JS / Style Dictionary / vanilla-extract", "component library / Storybook / visual regression / pattern library / living documentation / stability tier", "design→code drift / Figma handoff / design sync / tokens in two languages / two sources of truth".
IamK77/Skill/skills/atelier/type Skill
2★ repoThe type & text lens for a frontend build — where the scale, rhythm, and language-resilience of every string are decided. Use when establishing or auditing a type system, when text looks off, or when the UI has never been tested outside English. The one shift: a modular type SCALE + a spacing SCALE on the same rhythm (never magic px), AND text that survives EVERY language (i18n/BiDi/CJK/locale) — the agent nudges font-sizes until they "look right" and tests only in English, so the scale and the i18n robustness must be gated. Triggers on "type scale / modular scale / font size / font pairing", "spacing / padding / margin / gap / vertical rhythm", "line height / measure / line length / text wrap", "tabular numbers / numerics / data table typography", "RTL / BiDi / CJK / i18n / locale / pluralization / internationalization", "webfont / CLS / font-display / fallback stack", "letter-spacing / tracking / kerning / OpenType", "text looks off / spacing by eye / magic px".
IamK77/Skill/skills/surface/bearings Skill
2★ repoThe before-the-first-line lens for a frontend build: fix what is expensive to reverse before sunk cost exists. Use when starting a frontend product or major feature, or stress-testing a plan that jumped straight to a framework. The three ruling principles: BOUNDARIES > FRAMEWORKS (frameworks get swapped; the network/trust line and state classification fossilize into bedrock); ALLOCATE CAUTION BY REVERSIBILITY (one-way doors earn slow human judgment, two-way doors get a default for agents); and THE SOURCE OF TRUTH LIVES IN THE USER'S MIND, not the database. The one shift: frontend is the one discipline whose correctness spec lives in a brain, so taste is load-bearing and cannot be outsourced. Triggers on "starting a frontend / from scratch", "which framework", "how should I architect this UI".
IamK77/Skill/skills/surface/bulwark Skill
2★ repoThe 1-to-N lens for a frontend system that is already alive: the enemy is no longer building, it is ENTROPY — boundaries eroded by one "just this once" cross-import at a time, and the two graphs (component tree vs data dependency) drifting apart. Use when a frontend is in maintenance/scaling, onboarding more people, or showing rot (every change touches everything, the global store keeps growing, only one person dares touch the core). The one move: make the architecture SELF-ENFORCING, so it doesn't depend on everyone remembering the rules — because at scale they won't. Triggers on "the codebase is getting hard to change", "enforce architecture / module boundaries", "lint rules for imports / layering", "circular dependency", "this abstraction is everywhere / should I delete it", "dead code / unused exports / stale feature flags", "Conway's law / team structure", "design system / Storybook / component library", "onboarding / how long until a new hire ships". There is no exit; it is a steady state.
IamK77/Skill/skills/surface/livery Skill
2★ repoThe visual-craft lens for a frontend build — where the surface gets its color, type, depth, and motion. Use after seaworthy's build works, when establishing or auditing a visual language, or when a UI "looks off". The one shift: a polished interface is not a pile of hand-picked values — every visual value is a TOKEN derived from a small SYSTEM, and ad-hoc values are the entropy that makes a UI look amateur and impossible to re-theme. Taste picks the system; the system enforces it. Triggers on "color / theme / dark mode", "typography / type scale / spacing", "design system / design tokens", "make it look good / it looks off / cheap". The benchmark is a human nervous system, not a document, so taste is load-bearing and cannot be outsourced; the agent picks plausible-but-incoherent values and feels none of the wrongness.
IamK77/Skill/skills/surface/pilot Skill
2★ repoNavigate the surface frontend suite: route a frontend task to the right skill — and, because the suite is a lifecycle, to the right ENTRY STAGE — or to a sibling suite, or say plainly when none is warranted. The un-gated front door to the seven surface skills (bearings, keel, wellspring, seaworthy, trials, lookout, bulwark). Use when starting or mid-way through frontend work, unsure which stage fits or whether the suite is needed. The shift it leans on: most frontend work is NOT greenfield, so the best routing names WHERE IN THE PIPELINE TO ENTER, not stage 0. Triggers on "which frontend skill / where do I start", "how should I build this UI / app", "my state is a mess / it's out of sync", "it feels janky / slow", "my component tests break on every refactor", "dark pattern / which metric", "the frontend is rotting as it grows". It also redirects ACROSS suites: code craft / architecture / testing / process / security → engineering; realtime / offline / CRDT → distributed; library choice → quarry.
IamK77/Skill/skills/surface/seaworthy Skill
2★ repoThe build-it lens for a frontend feature, with one inverted discipline: the happy path is ~40% done, not 90%, so you design the UNHAPPY paths first, not as a polish pass that never gets time. Use when building feature slices (after wellspring's state map), or auditing whether a feature is production-grade. The one shift: what you ship is not "a correct program" but a maintained ILLUSION of direct manipulation over a real, asynchronous, failing system — so loading / error / empty / edge states aren't afterthoughts, they ARE the product, and accessibility and a performance budget are built in from the first slice, not bolted on. Triggers on "build this component / feature", "loading / error / empty states", "optimistic update", "skeleton screen", "animation / transition", "accessibility / a11y / keyboard / screen reader / focus", "performance / Web Vitals / INP / LCP / CLS / bundle size", "it feels janky / slow", "race condition / stale response".
IamK77/Skill/skills/surface/trials Skill
2★ repoThe correctness lens for a frontend build, organized around one question that decides whether your test suite is a safety net or a straitjacket: does this test go red when BEHAVIOR changes (a net — it warns on real regressions) or when the IMPLEMENTATION changes (a shackle — it reddens on every refactor, so you fix tests instead of code, and learn to ignore red). Use after seaworthy's slices exist, when writing or auditing frontend tests, or when a suite is brittle. The one shift: test BEHAVIOR, not internal structure — and put the test budget where frontend bugs actually cluster (integration: the seams, the two-graph drift, state out of sync), which makes the right shape a TESTING TROPHY, not the classic pyramid. Triggers on "what / how should I test this UI", "unit vs integration vs E2E", "testing-library / Playwright / Cypress / Vitest / Jest", "my tests break on every refactor", "snapshot tests", "should I mock this", "test coverage / 100%", "is this test worth keeping", "flaky tests".
React native unistyles conventions
AlshehriAli0/agent-skills/skills/react-native-unistyles-conventions Skill
no license2★ repoOpinionated production conventions for react-native-unistyles v3 (React Native / Expo): Tailwind-style theme scales, dynamic-function styling over conditional arrays, gap-over-margin, theme-only values. Use when styling or theming React Native / Expo components, writing or refactoring StyleSheet.create, converting RN StyleSheet to unistyles, or setting up unistyles. Bundles the upstream unistyles v3 skill (jpudysz) for foundational API and setup.
almasumdev/awesome-mobile-security-agent-skills/.github/skills/privacy/privacy-by-design Skill
no license2★ repoPrivacy-by-design principles on mobile — data minimization, purpose binding, consent. Use when introducing new data collection or third-party SDKs.
F-e-u-e-r/opus-pack/design-pack/skills/ui-design-craft Skill
2★ repoStatic visual judgment for generated or restyled UI. Load when you are about to produce or modify any user-facing surface - a landing/marketing page, product screen, mockup, or component styling - when a brief says "make it look good/premium/modern" with no design system attached, or when you notice generated UI converging on default AI aesthetics. NOT for motion decisions (motion-craft), for running a measured design review (design-review-gate), for charts (the environment's dataviz tooling), or for native mobile idiom questions (Apple HIG / Material directly).
alexvtejeda/elenchus/skills/elenchus-tui Skill
no license2★ repoUse when the user wants a terminal-UI (TUI) mockup designed and then proven to actually render — pure-ASCII, no framework — before building the real thing. Triggers: "mock up a terminal UI for X", "design a TUI / CLI dashboard I can show someone", "make an ASCII wireframe of this terminal app and make sure it renders", "prototype these terminal screens and verify the alignment". Generates one runnable stdlib script with named, navigable breakpoint-states + a `.txt` snapshot per state, then verifies each in an isolated tmux session. NOT the browser/web mockups of visual-companion, NOT stress-testing a build premise (elenchus-build), NOT verifying a finished web feature (finishing-implementation-elenchus).
alexvtejeda/elenchus/skills/visual-companion Skill
no license2★ repoUse to SHOW the user something in their browser during an Elenchus or brainstorming flow — UI mockups, wireframes, architecture diagrams, side-by-side visual comparisons, design polish — when the content itself is visual and the user would grasp it better by seeing than by reading. The user always ANSWERS in the terminal; the browser is display-only (no clicking, no selections recorded). Typically dispatched by elenchus-build for a visual frontend-design question, paired with ui-ux-pro-max for the design intelligence. NOT for text/tabular questions (requirements, tradeoff lists, A/B/C described in words) — those stay in the terminal.
carinyaparc/skills/skills/code-review-fix Skill
2★ repoUse when the user wants to address, action, or fix findings from a code review — their own working diff reviewed by code-review, a reviewer's comments on a PR or MR, or a pasted list of issues. Triggers on "fix the review findings", "address the review feedback", "action the blocking issues", "apply the review comments". Optionally scoped to an action tier (blocking, warning, all). Makes targeted, behaviour-preserving changes, runs the project's validation suite, and commits in logical units. Do NOT use to perform a review (code-review), to implement new work or features (implement), to address UX or design-fidelity findings (ux-design-review), or to open a PR/MR (merge-request).
carinyaparc/skills/skills/code-review Skill
2★ repoCarinya Parc Agent Skills
carinyaparc/skills/skills/design Skill
2★ repoUse when the user wants epic-level technical design at docs/work/{epic}/design.md, walking-skeleton or TDD design. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Triggers on "design CHK01", "write the epic design", "how should we build this epic". For reviewing an existing design.md, use docs-review instead. Do NOT use for epics or stories (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), or code implementation (implement).
carinyaparc/skills/skills/docs-review Skill
2★ repoUse when the user wants a set of documents reviewed — a docs folder, a wiki, a handbook, a repo's markdown, or any collection of written material. Checks that each document is well written and well structured, that boundaries between documents are clear with no duplication, and that the set is consistent and cohesive. Triggers on "review the docs", "are these docs any good", "is our documentation consistent", "do these docs overlap", "audit the documentation". Works on any doc set in any format or tool. Read-only: produces a report and changes nothing. Do NOT use to write or amend a document, to review code (code-review), or to review rendered UI (ux-design-review).
carinyaparc/skills/skills/implement Skill
2★ repoUse when the user wants to implement a task in code against an approved design.md and docs/work/{epic}/tasks.md. Triggers on "implement CHK01-01", "build this task", "write the code for this story". Reads the design and acceptance criteria, writes code and tests, runs the project's full validation suite, and commits in logical units. Do NOT use for code review (code-review), addressing review feedback (code-review-fix), changing how existing UI looks or behaves (ux-design-fix), writing tasks (tasks), or writing a design (design).
carinyaparc/skills/skills/ux-design-fix Skill
2★ repoUse when the user wants to change how existing UI looks or behaves — fix spacing, colour, layout, states, responsiveness, or accessibility on a component, page, or flow. Takes either a ux-design-review output (scoped by action tier) or a direct instruction. Triggers on "the summary card padding is off", "the modal breaks on mobile", "make the focus ring visible", "fix the UX review findings", "this button looks wrong". Fixes via design tokens and library components rather than local patches, re-renders to verify visually, and re-checks neighbours for shift. Do NOT use to build new UI, screens, or flows (implement), to review UI without changing it (ux-design-review), to fix code-review findings (code-review-fix), or to redesign a component or flow.
carinyaparc/skills/skills/ux-design-review Skill
2★ repoCarinya Parc Agent Skills
bogdanbaciu21/skills/bogdan-baciu-design Skill
2★ repoApply Bogdan Baciu's personal editorial design system to websites, static HTML, prototypes, documents, slide decks, and financial-model artifacts. Use when the user asks for "Bogdan brand", "my brand", "personal branding", "brand this", "apply the design system", "rebrand this", "make this look like bogdanbaciu.com", or when building/reviewing bogdanbaciu.com-facing interfaces. Includes the Puddles sky-blue on warm-cream palette, Instrument Serif + Geist + JetBrains Mono typography, flat editorial layout rules, and the scoped .db-scope financial-artifact styling.
Context engineering memory design
jukrap/ai-agent-playbook/skills/ai-harness/context-engineering-memory-design Skill
2★ repoUse when designing or reviewing agent instructions, context surfaces, prompt/cache budget, project memory, compaction behavior, durable memory promotion, or stale fact handling.
jukrap/ai-agent-playbook/skills/ai-harness/mcp-server-design Skill
2★ repoUse when designing or changing MCP tools, resources, prompts, permission tiers, write gates, cache/index surfaces, or agent harness integrations.
jukrap/ai-agent-playbook/skills/ai-harness/runtime-index-cache-design Skill
2★ repoUse when designing or reviewing runtime reports, indexes, graphs, caches, artifact schemas, invalidation, canon promotion, generated evidence, or local-only runtime storage.
jukrap/ai-agent-playbook/skills/delivery/eval-harness-design Skill
2★ repoUse when agent evals need graders, pass@k, regression gates, or reliability evidence.
jukrap/ai-agent-playbook/skills/delivery/test-fixture-data-design Skill
2★ repoUse when designing, reviewing, or repairing test fixtures, factories, mocks, seeds, snapshots, golden files, sample payloads, test databases, or fixture maintenance boundaries.
jukrap/ai-agent-playbook/skills/design/design-brief-direction Skill
2★ repoUse when turning a vague product, page, brand, or UI request into a design direction, visual language, constraints, and decision-ready brief before implementation.
jukrap/ai-agent-playbook/skills/design/design-reference-analysis Skill
2★ repoUse when analyzing screenshots, competitor sites, reference apps, visual samples, or design boards before implementing or refactoring UI.