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
maystudios/claude-skills/tech-product-landing Skill
31★ repoBuild production-grade landing pages for software/CLI tools, developer libraries, and technical products. Uses the "Maxsim-style" design system: dark theme, blue accent glows, framer-motion animations, geometric hero grid, marquee tech stack, tabbed docs, and timeline how-it-works sections. Trigger when user says "create a landing page for my software", "build a product site", "make a landing page like maxsim-flutter", "developer landing page", or "CLI tool website". Stack: Vite + React + TypeScript + Tailwind CSS v4 + Framer Motion + Lucide React.
waterfeet/DoroPet_V3/opendoro/src/skills/frontend-design Skill
31★ repoCreate distinctive, production-grade static sites with React, Tailwind CSS, and shadcn/ui — no mockups needed. Generates bold, memorable designs from plain text requirements with anti-AI-slop aesthetics, mobile-first responsive patterns, and single-file bundling. Use when building landing pages, marketing sites, portfolios, dashboards, or any static web UI. Supports both Vite (pure static) and Next.js (Vercel deploy) workflows.
The same file is in 1 other repository
eugenelim/agent-ready-repo/.agents/skills/frontend-engineering Skill
31★ repoLoad when a task's primary output is HTML, CSS, or JS. Provides design pre-flight, codified craft rules, and GATES verification commands for that surface.
eugenelim/agent-ready-repo/packs/core/.apm/skills/frontend-engineering Skill
31★ repoLoad when a task's primary output is HTML, CSS, or JS. Provides design pre-flight, codified craft rules, and GATES verification commands for that surface.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/analytical-design Skill
31★ repoUse when designing an analytical surface — a dashboard, a reporting view, a monitoring screen, or any surface whose primary purpose is to help a user understand a data set and act on it. Triggers on 'design the dashboard', 'structure the reporting view', 'what goes on the analytics screen', 'KPI layout', 'design a monitoring view'. Produces domain-model-first IA and widget hierarchy specifications. Scope boundary — individual chart encoding design is out of scope (use interaction-design for component state machines); this skill handles dashboard IA only. Do NOT use for marketing surfaces (use conversion-design) or workspace productivity surfaces (use workspace-design). Surface genre: analytical.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/content-design Skill
31★ repoUse when a designer or product person needs to decide what a surface should say, for whom, in what form, and to what objective — before any wireframe or screen flow is opened. Routes across two surface types: acquisition surfaces (marketing pages, landing pages, web onboarding flows) and product/reference surfaces (help pages, feature reference, in-product wayfinding). Triggers on "what should this landing page say", "write a content brief for our onboarding flow", "what's the narrative arc for this marketing page", "what does this feature page need to communicate", "help me decide the above-fold structure". Do NOT use to write final copy (use `tone-of-voice` for copy voice, then `voice-and-microcopy` for UI strings), to produce an analytics or CRO measurement framework, or to generate SEO keyword plans. Outputs `communication_mode: product-copy | technical-editorial | reference-documentation` in the content brief frontmatter so downstream skills apply the correct editorial register.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/conversion-design Skill
31★ repoUse when designing a marketing surface — a landing page, product homepage, pricing page, or acquisition flow — where the primary goal is to convert a visitor into a lead, trial user, or customer. Triggers on 'design the landing page', 'structure the homepage', 'what goes above the fold', 'convert visitors', 'design the pricing page', 'product marketing surface'. Produces IA and structural specifications for conversion surfaces. Do NOT use for product UI design (use user-flow + interaction-design), documentation surfaces (use documentation-design), or analytical dashboards (use analytical-design). Surface genre: marketing.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/creative-direction Skill
31★ repoUse when a designer or stakeholder has a felt "vibe" but no named direction — turning a vague mood into ranked emotional/brand goals and an creative-direction doc the rest of the build references. Triggers on "make it feel premium/calm/playful", "I want it to feel like X", "what's the vibe here", "we need a look and feel", "before we pick colors/type". Runs the interrogation that converges a mood into named goals, grounds each goal in a stable referent (persona, precedent, standards, platform conventions), then records which goal wins when two goals conflict. Do NOT use to derive a token or scale taxonomy (use `design-system`), to structure hierarchy and reading flow (use `information-architecture`), or to evaluate an existing screen (use `design-review`).
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/design-principles Skill
31★ repoUse when a design team needs shared, durable decision rules — converting journey-map insights and opportunity pains into 3–5 named principles that resolve design disputes and persist across sprints. Triggers on "what are our design principles", "how do we make design decisions consistently", "we keep relitigating the same tradeoffs", "write our design principles", "derive principles from this journey". Produces principles in the form [Imperative verb] + [what] + [why/for whom] with an arbitration test. Do NOT use to set visual direction (use `creative-direction`), to derive tokens or scales (use `design-system`), or to evaluate an existing screen (use `design-review`).
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/design-review Skill
31★ repoEvaluate an existing screen, flow, or mockup with a severity-rated findings list: quality-floor pass (states, a11y, motion), heuristic eval (Nielsen's 10), marketing clarity pass (tweet test, five-second scan, painkiller-first — fires on above-fold copy with a persuasion goal), and taste critique (grounded aesthetic reference + platform fit). Triggers on 'critique this design', 'review this screen', 'what is wrong with this mockup', 'do a heuristic eval', 'is this usable', 'does this fit our aesthetic', 'does this page convert', 'is this copy compelling', 'tweet test'. Do NOT use to name a felt direction (use creative-direction), to derive tokens (use design-system), or to structure hierarchy (use information-architecture).
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/design-system Skill
31★ repoUse when an aesthetic direction exists and the next move is a system — deriving a token/scale taxonomy and its rationale from intent. Triggers on "derive a scale", "set up design tokens", "name our tokens", "what's our spacing/type system", "turn the direction into a system". Names tokens by semantic role, organizes scales by a single ratio-as-concept, treats accessibility as a floor, and composes atomically (build systems, not pages). Do NOT use to set the vibe first (use `creative-direction`), to lay out a screen's hierarchy and flow (use `information-architecture`), or to evaluate an existing surface (use `design-review`).
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/documentation-design Skill
31★ repoUse when designing a documentation surface — a docs site, a help centre, an API reference, or a technical guide set. Decides what type of content belongs where, how navigation scales with content volume, and what the first-value-moment is for each content type. Triggers on 'design the docs site', 'structure the help centre', 'what goes on the docs landing page', 'how should we navigate the API reference', 'TTFV for this tutorial'. Produces IA and navigation specifications for documentation surfaces. Do NOT use for marketing surfaces (use conversion-design) or informational editorial pages (use informational-design). Surface genre: documentation.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/informational-design Skill
31★ repoUse when designing an informational surface — an article page, a news or editorial page, a long-form content page, or a content-rich page whose primary purpose is to inform, not to convert or enable tasks. Triggers on 'design the article page', 'structure the editorial page', 'how should the blog look', 'long-form content design', 'reading experience design'. Uses typography as the primary design tool. Do NOT use for documentation (use documentation-design), marketing (use conversion-design), or tool/app surfaces (use workspace-design). Surface genre: informational.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/interaction-design Skill
31★ repoUse when a screen or component needs its behavioral layer designed — how it responds to actions, validates input, transitions between states, and guides users through gesture and cognitive fit. Triggers on "design how this form behaves", "what happens when the user taps submit", "design the loading and error states", "map the state machine for this component", "design the micro-interactions", "how should this feel to use". Do NOT use to structure hierarchy or wayfinding (use `information-architecture`), to name aesthetic direction (use `creative-direction`), to map cross-screen navigation routes (use `user-flow`), or to enumerate which states exist (that enumeration belongs to the shared quality floor).
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/journey-mapping Skill
31★ repoUse when a product team needs to understand how a customer moves through an experience end-to-end — mapping the stages, actions, emotions, pains, and opportunities along the path. Triggers on "map the customer journey", "what does the user go through", "journey map this flow", "map out the experience stages", "what are the customer touchpoints", "where does the user feel pain". Carries a platform/surface axis (responsive-web, iOS, Android, cross-platform) that changes what the method asks at each stage. Scoped to customer/end-user journeys only — employee journeys are out of v1. Do NOT use to design screen interactions (use `user-flow`), to blueprint the backing services (use `service-blueprint`), or to map an internal business process (use `process-mapping`).
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/marketplace-design Skill
31★ repoUse when designing a marketplace surface — a catalogue, a listing grid, a product detail page, or a buying/transaction flow that connects buyers and sellers or producers and consumers. Triggers on 'design the marketplace', 'structure the listing page', 'how should the catalogue work', 'design the search and filter', 'buyer journey on the marketplace', 'product card design'. Produces IA specifications for catalogue, filter, comparison, and transaction bridge surfaces. Do NOT use for single-product marketing surfaces (use conversion-design) or workspace tool surfaces (use workspace-design). Surface genre: marketplace.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/tone-of-voice Skill
31★ repoUse when a designer, copywriter, or builder has a felt "copy vibe" but no named direction — turning a vague register sense into ranked copy goals grounded in stable referents (persona language, copy precedents, persuasion standards), and recording copy arbitration rules the rest of the build references. Triggers on "what voice should our copy have", "write a tone-of-voice doc", "how do we sound different from our competitors", "what should our hero headline feel like", "copy vibe check". Do NOT use for product UI copy states (error messages, empty states, button labels, form labels) — use `voice-and-microcopy` in the `product-engineering` pack for those. Do NOT use for SEO keyword targeting, advertising copy templates, or brand identity documentation.
eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/workspace-design Skill
31★ repoUse when designing a workspace surface — a productivity tool, a collaborative environment, an agentic UI, or any surface whose primary purpose is to support sustained professional work across sessions. Triggers on 'design the workspace', 'structure the tool UI', 'collaborative editing surface', 'agentic UI design', 'multi-agent coordination UI', 'task management surface', 'session arc design'. Covers context-persistence, collaboration state IA, ambient attention, agentic patterns, and interrupt design. Do NOT use for dashboards and monitoring views (use analytical-design) or marketplace surfaces (use marketplace-design). Surface genre: workspace.
eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/voice-and-microcopy Skill
31★ repoUse when shaping the actual words a user reads in a product's UI — characterizing the product's voice, writing the recurring UI-state microcopy (error, empty, button, label), or reviewing copy before it ships. Triggers on "what should this error say", "write the empty-state copy", "name this button", "characterize our product voice", "make this microcopy blame-free", "review this copy". Characterizes voice along a few axes, writes each UI state from a blame-free + actionable formula, and runs a content checklist. When a screen flow and per-screen state matrix are present (from `experience-design`'s `user-flow`), writes copy per screen × state keyed to the matrix; when absent, behaves as today. Do NOT use to frame the intent behind the feature (use `frame-intent`), to make visual or layout design decisions (this is words only), or to write documentation prose (that is `new-guide`'s clear-prose craft).
eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/define-ux-strategy Skill
31★ repoUse when a strategist needs to set the experience direction before design begins — the bridge between business goals and what the designed product must achieve. Triggers on "define the UX strategy", "I need to set the experience strategy before design", "what should our UX strategy be", "align design to business goals", "set the experience vision". Produces a committed ux-strategy.md. Do NOT use to produce a customer journey map — that belongs to journey-mapping in the experience-design pack.
soupandpsy/amazing-psycoder-skills/amazing-psycoder/psy-ana-designer Skill
31★ repoDesign a behavioral-psychology data analysis plan and produce a confirmed analysis config YAML. Use for scientific-question formulation, data-structure intake, statistical-method selection, analysis plans, cleaning/exclusion rules, effect sizes, assumption checks, sensitivity analyses, and figure choices, including “数据该怎么分析/用什么统计方法”. Compare viable methods before the user chooses. Do not generate or audit R/Python code; use psy-ana-coder or psy-ana-reviewer for those stages.
soupandpsy/amazing-psycoder-skills/amazing-psycoder/psy-exp-designer Skill
31★ repoDesign or revise a psychological experiment before implementation. Use when the user has an idea, partial protocol, trial/block structure, timing, randomization, response mapping, condition table, PsychoPy/jsPsych/ Psychtoolbox target, or a paradigm such as Stroop, IAT, N-back, priming, dot-probe, visual search, task switching, Go/No-go, or stop-signal, and needs a confirmed experiment config YAML. Do not use to implement/debug existing code or to audit readiness; use psy-exp-coder or psy-exp-reviewer instead.
NickCrew/Claude-Cortex/skills/accessibility-audit Skill
30★ repoFast, high-signal accessibility triage for pages, components, or PRs targeting WCAG 2.2 AA compliance.
NickCrew/Claude-Cortex/skills/canvas-design Skill
30★ repoCreate beautiful visual art in .png and .pdf documents using design philosophy. Use when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
NickCrew/Claude-Cortex/skills/chart-builder Skill
30★ repoUse this skill when creating data visualizations, selecting the right chart type, or generating chart code. Trigger phrases: 'build a chart', 'visualize this data', 'create a graph', 'plot these numbers', 'which chart should I use for'. Not for building interactive dashboards, designing UI components, or creating infographics with design tools like Figma.
NickCrew/Claude-Cortex/skills/color-palette Skill
30★ repoUse this skill when creating, evaluating, or documenting color palettes for brands, products, or design systems. Trigger phrases: 'create a color palette', 'what colors should I use', 'brand colors for', 'accessible color scheme'. Do NOT use for image editing, photo color correction, or print production color matching.
NickCrew/Claude-Cortex/skills/dashboard-designer Skill
30★ repoUse this skill when designing a data dashboard—choosing KPIs, structuring layout, applying visual hierarchy, or deciding which BI tool to use. Trigger phrases: 'design a dashboard', 'build a KPI dashboard', 'what should my dashboard show', 'help me layout a dashboard', 'dashboard for monitoring'. Not for building chart code from scratch (use chart-builder), writing SQL queries (use sql-analyst), or designing marketing landing pages.
NickCrew/Claude-Cortex/skills/design-critiquer Skill
30★ repoUse this skill when reviewing, evaluating, or giving structured feedback on UI designs, wireframes, mockups, or design systems. Trigger phrases: 'critique this design', 'give feedback on my UI', 'review this wireframe', 'what's wrong with this design'. Do NOT use for writing code, implementing designs, or marketing material critique.
NickCrew/Claude-Cortex/skills/design-journey-review Skill
30★ repoCombined visual design and user journey review: color systems, typography, spacing, information density, visual hierarchy, workflow stages, emotional curve, friction points, and daily-use optimization. Use when evaluating how an interface looks, how it serves its user over time, and whether the design earns its space.
NickCrew/Claude-Cortex/skills/design-system-architecture Skill
30★ repoBuild scalable design systems with design tokens, component APIs, and documentation. Use when creating or evolving component libraries.
NickCrew/Claude-Cortex/skills/eval-designer Skill
30★ repoUse this skill when building evaluation frameworks to measure LLM quality, safety, accuracy, or alignment including test suites, human eval rubrics, automated evals, and metrics design. Not for training or fine-tuning models. Not for dataset curation or benchmark comparison across publicly available models.
NickCrew/Claude-Cortex/skills/frontend-design Skill
30★ repoUse this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering, or writing server code.
NickCrew/Claude-Cortex/skills/interaction-design Skill
30★ repoUser flow design, micro-interactions, and interface behavior patterns with state management for all interaction conditions. Use when designing natural interactions, feedback systems, or handling error states.
NickCrew/Claude-Cortex/skills/market-researcher Skill
30★ repoUse this skill when sizing a market, analyzing competitors, designing customer surveys, segmenting audiences, or synthesizing research into market insights. Trigger phrases: 'size the market for', 'analyze our competitors', 'who is our target customer', 'design a survey to understand', 'TAM/SAM/SOM for'. Not for building financial models, writing pitch decks, or conducting UX usability research.
NickCrew/Claude-Cortex/skills/tutorial-design Skill
30★ repoDesign and write hands-on tutorials with progressive disclosure, exercises, and troubleshooting sections. Use when creating learning content, workshops, or step-by-step guides.
NickCrew/Claude-Cortex/skills/ui-design-aesthetics Skill
30★ repoGenerates high-quality, non-generic UI designs with a focus on performance, progressive disclosure, and distinctive aesthetics.
NickCrew/Claude-Cortex/skills/ui-ux-review-suite Skill
30★ repoUser-triggered orchestrator that runs a comprehensive UI/UX review by coaching the user through four sibling skills as distinct lenses against one shared target, then synthesizing their findings into a single prioritized report. Composes user-journey-mapping (flow/funnel lens), ui-design-aesthetics (visual critique lens), interaction-design (state-coverage lens), and ux-review (usability-heuristics + WCAG lens). Resolves the review target once at suite start — the app/URL, the screens or flows under review, the viewports, and the user persona/goal — so every lens inherits the same scope and captured screenshots. Coaches rather than auto-runs — at each step it presents the next lens with its reframing prompt and an approval gate; the user invokes the sibling and confirms before moving on. Because the lenses overlap (ux-review already touches interaction and a11y), the suite scopes each lens to its distinct concern so the synthesis does not double-count. Produces one authored synthesis report — deduped findings grouped by severity and lens — not a navigation shell. Trigger on "run a full UX review," "comprehensive UI/UX review," "review this screen across all lenses," "do a complete design review," or when the user names two-or-more UI/UX lenses to coordinate. Not for running a single lens in isolation (invoke it directly), not for generating new UI (the generative siblings are reframed as critique here), and not for bypassing approval gates (this skill coaches, never autoruns).
NickCrew/Claude-Cortex/skills/user-journey-mapping Skill
30★ repoCreate comprehensive user journey maps that identify pain points, opportunities, and emotional states across touchpoints. Use when mapping user experiences or analyzing conversion flows.
NickCrew/Claude-Cortex/skills/ux-interaction-review Skill
30★ repoCombined UX and interaction design review: usability heuristics, state coverage, feedback patterns, timing, keyboard behavior, error recovery, and progressive disclosure. Use when reviewing how an interface works mechanically and whether interactions are well-designed for use.
NickCrew/Claude-Cortex/skills/ux-researcher Skill
30★ repoUse this skill when planning or conducting user research, writing interview guides, designing surveys for UX insights, synthesizing qualitative findings, creating personas, or writing research reports. Trigger phrases: 'write a user interview guide', 'how do I conduct usability testing', 'synthesize research findings', 'create a user persona', 'design a UX survey'. Not for quantitative market sizing (use market-researcher), writing business requirements (use business-analyst), or product analytics.
NickCrew/Claude-Cortex/skills/ux-review Skill
30★ repoMulti-perspective UX review combining usability heuristics, WCAG accessibility checks, and interaction design analysis. Use when reviewing UI components before release, evaluating user flows for usability issues, conducting design critiques, or auditing accessibility compliance.
NickCrew/Claude-Cortex/skills/ux-writer Skill
30★ repoUse this skill when crafting microcopy, UI text, or in-product writing—error messages, tooltips, button labels, empty states, onboarding flows, and confirmation dialogs. Trigger phrases: 'write microcopy for', 'write UI copy', 'write error messages', 'write onboarding text', 'button label for'. Do NOT use for marketing copy (use copywriter) or long-form documentation (use technical-writer).
NickCrew/Claude-Cortex/skills/visual-modes Skill
30★ repoUse when activating visual showcase modes (supersaiyan, kamehameha, over9000) for UI or interaction design - provides mode-specific enhancement checklists.
NickCrew/Claude-Cortex/skills/webapp-testing Skill
30★ repoToolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Structured output contract designer
AnthonyAlcaraz/agentic-graph-rag-skills/skills/reasoning-planning/structured-output-contract-designer Skill
30★ repoDesign the OUTPUT CONTRACT for a graph-agent node's seam, per Ch5 "Structured Generation: The Keystone of Reliable Communication" (Outlines). Most graph-agent failures are internode COMMUNICATION breakdowns, not bad reasoning — a node that emits free text is unreliable exactly where its output feeds the next node or a graph write. The designer picks an enforcement level (FREE_TEXT / JSON_SCHEMA / GRAMMAR_CONSTRAINED), emits a minimal contract for common DevOps-investigation node types, and validates a payload against that contract deterministically — the primitive that makes a seam verifiable. Use when wiring a node's output into another node, a graph write, or a tool call and free text would make the seam fragile. NOT for choosing WHICH pipeline shape to run (that is pipeline selection), NOT for terminal human-facing prose with no downstream parser, NOT for picking a model or a graph model class.
tt-a1i/matt-skills-with-to-goal/skills/codebase-design Skill
30★ repoShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
The same file is in 19 other repositories
tt-a1i/matt-skills-with-to-goal/skills/prototype Skill
30★ repoBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
The same file is in 6 other repositories
saeed-vayghan/gemini-agent-skills/.gemini/skills/api-designer Skill
30★ repoAPI architecture expert designing scalable, developer-friendly interfaces. Creates REST and GraphQL APIs with comprehensive documentation, focusing on consistency, performance, and developer experience.
saeed-vayghan/gemini-agent-skills/.gemini/skills/cli-developer Skill
30★ repoExpert CLI developer specializing in command-line interface design, developer tools, and terminal applications. Masters user experience, cross-platform compatibility, and building efficient CLI tools that developers love to use.
saeed-vayghan/gemini-agent-skills/.gemini/skills/frontend-developer Skill
30★ repoExpert UI engineer focused on crafting robust, scalable frontend solutions. Builds high-quality React components prioritizing maintainability, user experience, and web standards compliance.
saeed-vayghan/gemini-agent-skills/.gemini/skills/powershell-ui-architect Skill
30★ repoPowerShell UI architect specializing in desktop and terminal interfaces using WinForms, WPF, TUIs, and Metro-style frameworks like MahApps.Metro and Elysium. Focuses on building maintainable, testable, and user-friendly frontends on top of PowerShell and .NET automation.
saeed-vayghan/gemini-agent-skills/.gemini/skills/ui-designer Skill
30★ repoExpert visual designer specializing in creating intuitive, beautiful, and accessible user interfaces. Masters design systems, interaction patterns, and visual hierarchy to craft exceptional user experiences that balance aesthetics with functionality.
saeed-vayghan/gemini-agent-skills/.gemini/skills/ux-researcher Skill
30★ repoExpert UX researcher specializing in user insights, usability testing, and data-driven design decisions. Masters qualitative and quantitative research methods to uncover user needs, validate designs, and drive product improvements through actionable insights.
shinpr/codex-workflows/.agents/skills/recipe-design Skill
30★ repoExecute from codebase-scoped analysis to design document creation.
shinpr/codex-workflows/.agents/skills/recipe-front-design Skill
30★ repoExecute from codebase-scoped analysis to frontend design document creation including UI Spec.
shinpr/codex-workflows/.agents/skills/recipe-front-plan Skill
30★ repoCreate frontend work plan from design document with test skeleton generation.
ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/design-creative/canvas-design Skill
30★ repoA curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.
ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/design-creative/claudekit-aesthetic-ui Skill
30★ repoA curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.
ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/design-creative/frontend-design Skill
30★ repoA curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.
ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/design-creative/premium-ui-builder Skill
30★ repoA curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.