设计与前端
4,640 个结果
- Design Taste Frontendadamramadhntasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots.
- Diagnosing React CodebostonaholicRuns the react-doctor scanner on a React package, fixes its error diagnostics, and re-runs until none remain. Use when React components or hooks changed, when finishing a React feature or bug fix, or when asked to health-check React code.
- Enterprise Designrhawk117Turns business intent into a caller-facing Python contract before implementation: outcomes, a rule table, the architecture boundary, and the exact public types, signatures and error classes, shown to the user as declarations. Keeps partial success, duplicates, expected rejection and dependency failure distinct. Writes no project files and hands the contract packet to design-persistence.
- Explaining ArchitecturebostonaholicExplains how a subsystem, feature flow, or runtime path works (architecture, data flow, file map, gotchas), with an optional critique by fresh-context critics. Read-only. Use when asked how a subsystem or flow works or where logic belongs. Not for why code is shaped as it is; use investigating-design-rationale. Not for explaining a PR or diff; use explaining-code.
- Extension Http OutcallscaffeinelabsHTTP outcalls performed by the backend canister (not in the frontend), including mandatory local verification of external REST API requests. Canister → internet only. For inbound webhooks / curl endpoints served by the canister, use extension-http-endpoints instead.
- Extractits-magdyGets a design out of Figma and onto disk as JSON + assets, using the local "Design Twin" plugin (free Figma plan, no Figma API, no network egress). Use this whenever the user wants design data pulled, exported, refreshed or re-pulled from Figma — "pull the login screen", "export this frame", "get the design system", "get me the colors", "set up my theme from Figma", "grab the components from…
- Fnos Fpk Devjianyun8023Use when developing fnOS FPK packages, writing lifecycle scripts, or configuring manifest, privilege, resource, wizard, and desktop UI files. Covers package structure, environment variables, packaging, and common platform constraints.
- Frame DesignANVEAIArt-direct every frame of a video before it is built - a tone cell and motion personality, a palette measured for WCAG contrast, a free OFL type pairing, grid and platform safe zones, one hero per frame, the look and grain, and the special frames (title cards, lower thirds, end cards, covers and thumbnails) in 16:9, 9:16 and 1:1.
- Frontend Designcustomware-aiStrict frontend design guardrails for building modern, minimal-visual-noise, airy, non-generic app UIs. Use whenever creating or changing frontend UI, React components, shadcn/ui themes, Tailwind styles, app layouts, or first-version product screens.
- Frontend Dev GuidelinesmedorionFrontend development guidelines for Angular 19/TypeScript applications. Covers NG-ZORRO components, RxJS state management, auto-generated API clients, LESS styling with themes, feature-based organization, decorators, and performance optimization. Use when creating components, services, features, styling, routing, or working with frontend code.
- Functional DesignyutnaUse when starting design or review, deciding how much design a task warrants, from a throwaway script to a subsystem, unsure which skill fits, or the requirement is undecided.
- Functional Designing Deep ModulesyutnaUse when designing a module interface, when it exports nearly as much as it hides or is as complicated as its implementation, or when tiny one-function modules multiply.
- Functional Designing Workflow PipelinesyutnaUse when implementing a use case, command handler, or business process, or when logic for one operation is scattered across services and layers.
- Functional ElixiryutnaUse when designing Elixir structs, ok and error tuples, or `with` pipelines, and whether a GenServer, a supervision tree, or letting a process crash is the right answer.
- Functional Elixir PhoenixyutnaUse when designing a Phoenix context, an Ecto schema or changeset, a LiveView's assigns, or deciding what belongs in the domain rather than in the web layer.
- Functional JavascriptyutnaUse when applying functional design in plain JavaScript, without a type checker, including immutability, tagged unions, and Result-style error handling.
- Functional Modeling With Algebraic TypesyutnaUse when designing domain types, when a record has many optional fields, or when choosing between a record, a union, and a bare primitive.
- Functional Refactoring Toward Functional DesignyutnaUse when moving imperative or object-oriented code to functional design, when a code smell needs a move, or when a shape cannot absorb new requirements.
- Functional Reviewing Functional DesignyutnaUse when asked to review a design, diff, component or module, before merging, judging a design standard, or when a flagged pattern may be a stated project convention.
- Functional TypescriptyutnaUse when applying functional design in TypeScript without a functional library, including branded types, discriminated unions, and hand-rolled Result.
- Functional Typescript EffectyutnaUse when applying functional design in a TypeScript project built on the Effect library, including services, layers, schema boundaries, and tagged errors.
- Functional Typescript ReactyutnaUse when a React component's props grow, when an effect computes state that render could derive, or when deciding what belongs in a global store and what a selector should.
- Functional Typescript React NextjsyutnaUse when placing logic across the server and client boundary in Next.js, writing a Server Action, invalidating a cache after a mutation, or deciding what may cross.
- Game PlanThiagoFdaSLopesPlan a game or a game feature through dependency-ordered decisions - player promise, core loop, systems, architecture, production scope, risks - and end with a blueprint. Use for new games, new features, vague requirements, "X or Y" design choices, scope decisions, and when the user asks to plan, compare or decide before building. Planning-only - does not change code.