- Skills
- 230
- 仓库
- 1
- 职业覆盖
- 10
- 场景覆盖
- 7
- Stars
- ★ 67
Enow Dev. 的 Skills 230
demo-skill
Project-scope demo skill for tests.
writing
Writing words people read: the specific thing instead of claims, words to drop, sentences, interface copy (buttons, labels, errors, empty states, confirmations), page copy, notifications and emails, alt text and link text, numbers and dates, words that translate well, documentation and voice. Read before writing a page's copy, an interface's text or a document.
ui
Designing or restyling an interface: direction, layout, type, colour, icons, components, states, responsive behaviour. Read before building a page, a screen or a set of components.
ui-themes
Light and dark themes, and colour that holds in both: tokens with a value per theme, and what each kind of content needs to stay visible (icons, SVG drawings and line art, logos, photos, screenshots, charts, code, maps, borders, shadows, focus, form controls), switching without a flash, and checking both. Read before building a second theme or a theme toggle, and before any drawing, logo or chart on a page that has two themes.
ui-structure
Structure before styling: the blueprint written before any interface code (the screen's job, the regions its kind of page needs, their order and why, the layout skeleton in numbers, the components and their states), the anatomy and order of a homepage, a dashboard, a list, a detail page, settings, a form, sign-in, pricing, docs, an article and a checkout, and how to turn the blueprint into code (tokens, layout primitives, components, sections, page). Read first, before building or rebuilding any page or screen.
ui-stack-vue
Building interfaces in Vue 3 and Nuxt: project layout, script setup with typed defineProps, defineEmits and defineModel, attribute fallthrough, slots and scoped slots, template refs, ref, reactive and computed, watch versus watchEffect, composables and VueUse, provide and inject, Pinia, keyed v-for, transitions, Nuxt 4 (app directory, pages, layouts, useFetch and useAsyncData keys, $fetch in handlers, server routes, runtime config, useSeoMeta, NuxtImg, middleware), VeeValidate forms, Reka UI and Nuxt UI, testing, vue-tsc, and the traps. Read when the project uses Vue or Nuxt.
ui-stack-tailwind
Building with Tailwind CSS v4 (and v3) without the Tailwind-default look: setup per framework (Vite, Next.js, Astro, Laravel, monorepos), @theme tokens in OKLCH named by role, dark mode with @custom-variant, the layout system as tokens (one container, section spacing, a type scale, stretched rows) and how to fix each preview layout line with classes, state, aria, data, group, peer, has, motion and container-query variants, component recipes (button, field, card, navigation, table, dialog) with every state, motion with --animate-* and starting:, cn with tailwind-merge, cva, class order, @utility, arbitrary values, typography, v3 to v4 migration, and the generated look. Read when the project uses Tailwind.
ui-stack-svelte
Building interfaces in Svelte 5 and SvelteKit: project layout, runes ($state, $state.raw, $derived, $effect only for side effects, typed $props, $bindable, $props.id), snippets and render tags, event attributes, keyed each blocks, class and style directives, attachments, shared state in .svelte.ts modules and context, boundaries, transitions, SvelteKit routes, server and universal load functions, form actions with use:enhance, hooks for auth, env modules, Superforms, Bits UI and Melt UI, testing, svelte-check, and the traps. Read when the project uses Svelte or SvelteKit.
ui-stack-shadcn
Building with shadcn/ui without the shadcn-default look: owned source and components.json, the CLI (init, add, diff, info, docs, presets, migrations), the base library (Base UI, Radix or React Aria), theming its CSS variables in OKLCH for both themes, style, radius, fonts and density set from the direction, variants with cva and data-slot, composing the sidebar, data table, forms with Field, command palette, toasts and calendar, keeping the primitives accessible, the Tailwind v4 setup, registries, and the traps. Read when the project uses shadcn/ui (a components.json and components/ui).
ui-stack-react
Building interfaces in React 19: file layout by feature, typed function components, composition and slots, variants with cva, native props and refs passed through, where state lives and derived values, effects only for outside systems, keys, context split by concern, server data with TanStack Query, forms with actions or react-hook-form, Suspense and error boundaries, transitions and deferred values, portals and headless accessible primitives, the React Compiler and memo, Testing Library, and the traps (stale closures, racing effects, props copied into state, index keys, giant components). Read when the project uses React.
ui-stack-plain
Building with plain HTML, CSS and a little JavaScript, no framework and no build step: file layout, the document head, cascade layers, tokens as custom properties, modern CSS (grid, clamp, container queries, :has, nesting), a small reset, component classes, light and dark themes with color-scheme and a toggle, progressive enhancement with ES modules, native dialog, details and popover, forms that really submit, images with srcset, SVG icons, fonts, performance budgets, and when to move to Astro or a framework. Read when the project uses plain HTML and CSS, or a page of content needs nothing more.
ui-stack-next
Building interfaces with Next.js (App Router, 15 and 16): project layout, route groups, parallel and intercepting routes, server components with small client leaves and serialisable props, data fetching and the two caching models (fetch options, cache, use cache and Cache Components, dynamic triggers, Partial Prerendering), server actions with useActionState, loading, error and not-found files, streaming with Suspense, metadata, next/font, next/image, next/link, proxy and middleware redirects, public and server environment variables, reading next build, and Next's own traps. Read when the project uses Next.js.
ui-stack-astro
Building with Astro: when it fits, zero JavaScript by default, islands with client directives, content collections with schemas, layouts and components, images with astro:assets, view transitions, integrations for React, Vue or Svelte, server output and adapters, and build checks. Read when the project uses Astro or is a content site choosing a stack.
ui-stack-angular
Building interfaces in Angular: standalone components, signals and computed state, the built-in control flow, OnPush change detection, inject, typed reactive forms, the router with lazy routes and guards, HttpClient with interceptors, Angular CDK and Material, SSR with hydration, and testing. Read when the project uses Angular.
ui-reference-studio
A worked reference, measured from a hand-designed studio site: a small studio, consultancy or freelancer showing its work as decisions rather than thumbnails, then a way to get in touch. Its skeleton, wireframes, measures and component anatomy, and what to take from it. Read before building a studio, agency, consultant or project portfolio page.
ui-reference-saas
A worked reference, measured from a hand-designed product site: a professional tool with several features, proof, a team, pricing and a sign-up (a SaaS for lawyers). Its skeleton, wireframes, measures and component anatomy, and what to take from it. Read before building a product or SaaS marketing site with pricing.
ui-reference-marketplace
A worked reference, measured from a hand-designed marketplace: a store of many products from many sellers, organised in shelves, with search first, product cards that carry every buying fact, and a playful but systematic look. Its skeleton, wireframes, measures and component anatomy, and what to take from it. Read before building a store, marketplace or product catalogue.
ui-reference-launch
A worked reference, measured from a hand-designed launch page: a product before or at launch (early access, a waitlist, a developer tool) on one page. Its skeleton, wireframes, measures and component anatomy, and what to take from it. Read before building a launch, waitlist or single-product page.