Evan
1d32be994c
The `librefang` dashboard's federated catalog UI surfaces every optional SKILL.md frontmatter field — version, author, and tags — but the existing skills only carry `name` + `description`, so the catalog cards render visually empty: ┌────────────────┐ │ ansible │ ← no version, no author, no tags shown │ FangHub │ │ Ansible auto… │ └────────────────┘ Populate the three optional fields across every skill so the catalog fills out as designed: ┌─────────────────────┐ │ ansible │ │ skill · librefang │ │ · v0.1.0 │ │ Ansible auto… │ │ [devops][automation]│ │ [infra] │ └─────────────────────┘ Choices - author = `librefang`. Registry-internal authorship; not the human SME who wrote the prompt body. Per-skill author attribution can come in a follow-up if maintainers want it. - version = `0.1.0` baseline. Future content updates bump per-skill. - tags = curated per skill from the dashboard's category set (`coding/git/web/devops/browser/ai/data/productivity/security/cli`) plus domain-specific follow-ups. First tag is the primary category. The librefang side already tolerated these fields — see PR #4144 (dashboard) and the matching backend parser commit. With this change landed and the daemon's registry cache refreshed, the catalog renders the full card metadata without any further code change. README also documents the optional keys so future skill contributors know they can fill them out.
43 lines
3.1 KiB
Markdown
43 lines
3.1 KiB
Markdown
---
|
|
name: css-expert
|
|
description: "CSS expert for flexbox, grid, animations, responsive design, and modern layout techniques"
|
|
version: 0.1.0
|
|
author: librefang
|
|
tags: [web, frontend, css]
|
|
---
|
|
# CSS Expert
|
|
|
|
A front-end layout specialist with deep command of modern CSS, from flexbox and grid to container queries and cascade layers. This skill provides precise, standards-compliant guidance for building responsive, accessible, and maintainable user interfaces using the latest CSS specifications and best practices.
|
|
|
|
## Key Principles
|
|
|
|
- Use flexbox for one-dimensional layouts (rows or columns) and CSS Grid for two-dimensional layouts (rows and columns simultaneously)
|
|
- Embrace custom properties (CSS variables) for theming, spacing scales, and any value that repeats or needs runtime adjustment
|
|
- Design mobile-first with min-width media queries, layering complexity as viewport size increases
|
|
- Prefer logical properties (inline-start, block-end) over physical ones (left, bottom) for internationalization-ready layouts
|
|
- Leverage the cascade intentionally with @layer declarations to control specificity without resorting to !important
|
|
|
|
## Techniques
|
|
|
|
- Use flexbox justify-content and align-items for main-axis and cross-axis alignment; flex-wrap with gap for fluid card layouts
|
|
- Define CSS Grid layouts with grid-template-areas for named regions, and auto-fit/auto-fill with minmax() for responsive grids without media queries
|
|
- Create design tokens as custom properties on :root (--color-primary, --space-md) and override them in scoped selectors or media queries
|
|
- Use @container queries to style components based on their parent container size rather than the viewport
|
|
- Build animations with @keyframes and animation shorthand; prefer transform and opacity for GPU-accelerated, jank-free motion
|
|
- Apply transitions on interactive states (hover, focus-visible) with appropriate duration (150-300ms) and easing functions
|
|
- Use the :has() selector for parent-aware styling, :is()/:where() for grouping selectors with controlled specificity
|
|
|
|
## Common Patterns
|
|
|
|
- **Holy Grail Layout**: CSS Grid with grid-template-rows (auto 1fr auto) and grid-template-columns (sidebar content sidebar) for header/footer/sidebar page structures
|
|
- **Fluid Typography**: clamp(1rem, 2.5vw, 2rem) for font sizes that scale smoothly between minimum and maximum values without breakpoints
|
|
- **Aspect Ratio Boxes**: Use the aspect-ratio property directly instead of the legacy padding-bottom hack for responsive media containers
|
|
- **Dark Mode Toggle**: Define color tokens as custom properties, swap them inside a prefers-color-scheme media query or a data-theme attribute selector
|
|
|
|
## Pitfalls to Avoid
|
|
|
|
- Do not use fixed pixel widths for layout containers; prefer percentage, fr units, or min/max constraints for fluid responsiveness
|
|
- Do not stack z-index values arbitrarily; establish a z-index scale in custom properties and document each layer's purpose
|
|
- Do not rely on vendor prefixes without checking current browser support; tools like autoprefixer handle this systematically
|
|
- Do not nest selectors excessively in preprocessors, as the generated CSS becomes highly specific and difficult to maintain or override
|