bestax-layout-scaffold
Skill14 starsChanged 8 days agoMITView on GitHub
Scaffold a complete, responsive page layout with @allxsmith/bestax-bulma — app shells/dashboards, marketing/landing pages, centered auth/settings pages, and card-grid catalogs. Use when building a full page or overall app layout (not a single component).
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- allxsmith/bestax-skillsedited, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- allxsmith/bestax-skills★ 396% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bulma-ui/AGENTS.mdAGENTS.md
- bestax-mcp/CLAUDE.mdCLAUDE.md
- bestax-migrate/CLAUDE.mdCLAUDE.md
- bulma-ui/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- create-bestax/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- eslint-plugin/CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- bulma-ui/llms.txtllms.txt
- bestax-custom-componentSkill
- bestax-formSkill
- bestax-iconsSkill
- bestax-migrateSkill
- bestax-optimizeSkill
- bestax-themingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask at most one clarifying question, and only for a high-level fork the request genuinely does not imply: whether the page is public-facing …
- Distinctive: line 32
Default when ambiguous: internal tool → App shell.
- Distinctive: line 318
Look up the declaration you were about to inline.
- Very specific: line 339
No helper matches (e.g. maxWidth, a one-off gradient)?
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scaffolding a page layout with @allxsmith/bestax-bulma
Turn a high-level request ("admin dashboard", "landing page", "login screen", "product catalog") into a complete responsive page built from bestax-bulma layout components.
Behavioral rule
Select an archetype from the request and build it in one shot. Do not ask layout questions ("how many columns?", "where should the nav go?", "what width?") — infer the structure from the request and proceed. The archetype determines the structure; fill it with the requested content.
Ask at most one clarifying question, and only for a high-level fork the request genuinely does not imply: whether the page is public-facing (marketing) or an internal tool (authenticated app). When the request already signals this ("dashboard", "admin", "landing", "login", "pricing"), skip the question and default.
Select an archetype
| Request signals | Archetype |
| dashboard, admin, console, internal tool, authenticated app, "sidebar" | App shell |
| landing, marketing, homepage, product/pricing page, public site | Landing |
| login, sign up, auth, settings, checkout, a single focused form | Centered |
| catalog, gallery, products, listing, "grid of cards", search results | Card grid |
Default when ambiguous: internal tool → App shell; public-facing → Landing; one focused task → Centered; a collection of items → Card grid. For mixed requests, pick the dominant intent (e.g. "admin dashboard with a product list" → App shell whose main column holds a Card grid).
Approach
- Compose pages from the shipped layout components —
Container,Section,Hero,Footer,Level,Columns/Column,Grid/Cell,Navbar,Menu,Card. There is noTilecomponent. For uniform grids (card grids, galleries — same-shaped items) preferGrid/Cell: CSS Grid gives equal-height cells for free (per row — each row's cells match its tallest, same row-level behavior as the flex recipe). UseColumns/Columnfor proportional or per-breakpoint column layouts — and when cards there must be equal height, apply the flex recipe (Column display="flex" flexDirection="column"+Card flexGrow="1";height: 100%on the card doesn't help — the column's height is auto). - Rely on Bulma's responsive defaults:
Columnssit side by side on tablet and up and stack on mobile. Add responsivesize*props only to tune the breakpoints. - Interactive extras don't share a state API — never transfer one by analogy:
Collapse trigger={node} open/defaultOpen onOpenChange(onOpenChange(open)reports every trigger;onOpen/onClosefire only when the Collapse holds its own state), an accordion isCollapses value/defaultValue/onChangearound plainCollapsechildren indexed from 0 by position (number | null, ornumber[]withmultiple; hide an item withvisibility="hidden", never{cond && …}, or the open state shifts to its neighbour) rather than hand-rolled open-index state,Tabs value={i}/onChange(eachTabs.Tab/Tabs.Content.Itemrequiresindex={i}, andTabs.Contentmust be a child of<Tabs>— the active-tab context lives on it; a sibling panel never switches. The arrow keys, Home/End, Enter/Space, the single tab stop and thearia-controls/aria-labelledbylinks come built in, so add noonKeyDownor ARIA of your own;onChangefires when a tab is activated, never on arrow-key focus),Dropdown active/onActiveChange,ToggleButton pressed/defaultPressed onPressedChangefor a button that stays on or off (notButton isActive, which sets noaria-pressed; the label stays the same in both states; a set goes inButtons hasAddons role="group"with anaria-label, where it's alsoButtons.ToggleButton, and a row where only one can be on isSegmentedControl),SegmentedControl aria-label="…" value/defaultValue onChangefor a row of buttons where only one can be on, such as a list or grid view (oneSegmentedControl.Segment value="…"per option; a radio group with the single tab stop and the arrow keys built in, so add noonKeyDownof your own; an icon-only segment needs its ownaria-label; the arrows check as they move, soonChange(value)fires on each, and it can't be cleared; it carries no form value, so a choice a form submits isRadios),Popover trigger={<Button>…</Button>} open/defaultOpen onOpenChange(triggeris one element, not a node: Popover clones it to add the click and ARIA, so never wrap it in a clickable of your own; build the panel fromPopover.Header/Body/Footer/Close, and a panel without aPopover.HeaderneedsariaLabel),HoverCard trigger={<Link href="…">…</Link>}for a preview on hover or keyboard focus (triggeris one link or button, cloned the same way; the card's content goes straight in as children with no sub-components; a trigger inside aParagraphneedsappendToBody; hover and focus only unlessopenOnTapis set, which suits only a trigger with no tap action of its own, such as aButtonwith noonClick; on touch a link trigger just follows the link, so what the card shows must be on that page too, and a form is aPopover),ContextMenu aria-label="…" trigger={<Table.Tr>…</Table.Tr>}for actions on a right-click or a long press (triggeris one element, a row or a card, cloned rather than wrapped; the items areContextMenu.Item/ContextMenu.Divider, which areDropdown's; noopenprop,onOpenChangereports it; always put the same items in a visibleDropdownon the row too, since a context menu is only a shortcut),Steps value={i}/onStepClick items={[{label, icon?}]}for a journey the user moves through, such as a wizard or a checkout (child form isSteps.Step, notSteps.Item; a record of what happened isTimeline; in another language, setcompletedLabelandupcomingLabel, the words read after each completed or upcoming step).Reveal cascadestaggers only its direct children — to stagger a grid, put<Reveal delay={i * 80}>inside eachCell, not around the container. - An empty list, table or search with no results is
EmptyState, not a hand-builtBoxofIcon,TitleandButtons isCentered:<EmptyState icon="folder-open" title="No projects yet" titleAs="h3" description="…">with its one<Button>as a child (two or more go inEmptyState.Actions). Itstitleis always a heading, so settitleAsto the level under the list's own heading. It has no live region: after a search or a filter, keep aParagraphwithrole="status",aria-atomic="true"andvisibility="sr-only"beside the search field the whole time, saying the count, and have "Clear search" put focus back in the field. While data loads show aSkeletonor aLoader, and a failed load is aMessageor aNotification, never an EmptyState. The archetypes reference has the full pattern under Card grid. - A table people sort, search, page through or pick rows from is
DataTable, not aTablewith sort state,aria-sort, checkboxes and aPaginationwired by hand:<DataTable caption="Users" columns={[{ id: 'name', header: 'Name', sortable: true, isRowHeader: true }, …]} data={rows} selectionMode="multiple" pageSize={10} hasSearch />. A column is{ id, header }, readingrow[id], plusaccessor(the raw value, which sorts),format(its text, which the cell shows and the search matches) andcell(rich content). It needs acaption,aria-labeloraria-labelledby, and it shows its ownEmptyStateand says the match count itself.toolbar={table => …}holds buttons that act ontable.state.selectedor calltable.setFilter;useDataTable({ columns, data, … })returns the same table for<DataTable table={table} />or for markup of your own through itsget…Propsgetters;manualwithrowCounthands sorting, filtering and paging to a server.table.toCSV()writes what's shown as CSV, escaping formulas, for a download button; there's no Excel export. A table with nothing to sort, search or pick staysTable. - An order's history, a ticket's activity, a changelog or an activity feed is
Timeline, not a hand-built list with a border down the side:<Timeline titleAs="h3">with a<Timeline.Item title="Shipped" time="14 October 2026" dateTime="2026-10-14">per event, any detail as its children, and the whole date intime.titleAsis the level under the section's heading, or"p"in a busy feed. For something that moves along on its own, like a parcel or a deployment,active={i}marks progress andpending="Out for delivery"ends it on what's under way, oldest first. A journey the user moves through, like a wizard or a checkout, staysSteps. - Facts about one thing, each a label and its value (an order summary, a profile, a file's
details), are
DescriptionList, notColumnsof label and value or a two-columnTable:<DescriptionList aria-labelledby="order-heading">under aTitle id="order-heading", with a<DescriptionList.Item label="Order" value="#1234" />per fact. It stacks on a phone and puts the labels beside their values from tablet up, so add no breakpoint code;orientationpins it. Several values, or a label with an info tip, go in asDescriptionList.LabelandDescriptionList.Valuechildren. Several records with the same fields stay aTable, and so do facts a screen reader must announce with their labels, as aTablewithscope="row"headers. - A number shown to the reader (a price, a total, a count, a percentage, a dashboard figure) is
NumberFormatter, nottoLocaleString()or anIntl.NumberFormatbuilt by hand:<NumberFormatter value={8456.4} format={{ style: 'currency', currency: 'USD' }} />, with anyIntl.NumberFormatoptions informat(style: 'percent'takes a fraction,0.125for 12.5%). It writes in its ownlocale, else theLocaleProvider's, else the runtime's, so a server-rendered app sets alocaleon aLocaleProviderat the root. Its text is the number alone, so words go around it:Total: <NumberFormatter … />. Text that can't hold an element, anaria-labelor aplaceholder, gets the same fromconst format = useNumberFormat();andformat(1500, { style: 'currency', currency: 'EUR' }). - A dashboard's row of key figures (revenue, new customers, churn) is
StatsofStats, notLevelitems,ColumnsofTitles or aCardper figure. Put<Stats aria-labelledby="kpis" minCol={8} gap={4}>under aTitle id="kpis", with aStatper figure:label, a numbervaluewithformat(Intl.NumberFormatoptions, asNumberFormattertakes),changeanddescription, as in<Stat label="Revenue" value={8456.4} change={0.12} description="since last month" />.changeis a fraction written with its sign ("+12%"), green up and red down, andchangeColor="danger"marks a rise that's bad news, such as churn. The row wraps on its own, so add no breakpoint code, and it holds onlyStats (aLocaleProvidergoes around it, and on a page rendered on the server it's what keeps the server and the browser writing the numbers alike, unless eachStatgets alocale).loadingshows aSkeletonin place of a figure that isn't there yet. One figure on its own is a loneStat. For a card look, aBoxgoes around a loneStator the wholeStatsrow, never around oneStatinside a row, which would break the row's list. - A file browser, a checkbox tree (permissions, filters) or an outline you browse is
TreeView, with<TreeView.Item value="…" label="…" icon="folder">items nested inside each other:<TreeView aria-label="Files" selectionMode="single">withselected/onSelectedChangepicks one, andselectionMode="checkbox"withchecked/onCheckedChangedraws boxes with mixed parents, where a parent's value checks its whole branch. For categories, where checking a parent means only the parent,selectionMode="checkbox-independent"draws a box per item that checks that item alone, with no mixed parents. Map the data with a recursive function, and render an item's children whether it's open or not. A folder that loads when it opens takeshasChildren,isLoadingwhile its children are on their way, andloadError="Couldn't load src"withonRetrywhen the load fails, settingisLoadingagain while the retry runs: the tree draws the Loading… and Retry rows and announces them, so don't hand-write a placeholder item. Its items aren't links, so the app's sidebar and any list of pages stay onMenuwithMenu.Item href. - A sidebar whose groups of links open and close is
Menu.Section, one per group, directly inMenu(never inside aMenu.ItemorMenu.List):<Menu.Section label="Components" defaultOpen>around that group'sMenu.List, withdefaultOpenon the group holding the current page (oropen/onOpenChangeto hold the state). Its heading is a real button witharia-expanded, and its links stay links, each a tab stop. NotTreeView, and not aCollapseinside a hand-written<li>. - A long page's "On this page" list of its sections is
TableOfContents, not aMenuwith a scroll listener of your own: give each section's heading anidand pass the sections in page order,<TableOfContents isSticky items={[{ id: 'install', label: 'Install' }, { id: 'usage', label: 'Usage', children: […] }]} />, in a sideColumn. Its links are plain#idlinks that the browser follows itself, and it marks the section being read witharia-current="location". Offset a sticky header withscroll-padding-toponhtmlin the page's CSS (which the highlight reads too), not withscroll-margin-topon the headings, and put any smooth scrolling in that CSS underprefers-reduced-motion: no-preference. To mark the section in view in the app's own navMenu,useScrollSpy({ ids })returns its id. - An app's frame, a header across the top with a navigation column down the side, is
AppFrame, not afixedNavbaroverColumns:<AppFrame>withAppFrame.Header(aNavbarwith<AppFrame.Burger />in itsNavbar.Brand),AppFrame.Nav(theMenu) andAppFrame.Main(the page), plusAppFrame.AsideandAppFrame.Footerwhen there are any. The header and the column stick on their own, so nofixedand nohas-navbar-fixed-top; below desktop the column is a drawer the burger opens, and from desktop up the burger collapses it. For a column that collapses to its icons,<AppFrame.Nav rail>with aniconon each top-levelMenu.ItemandMenu.Section; the frame puts each label in a tooltip. It renders the page's<main>, so it goes at the top of the app, never inside a<main>. - Panes the user resizes are
Splitter(a file tree beside an editor, a list beside its detail, a query above its results), not hand-written drag code or fixedColumns:<Splitter height={480}>with a<Splitter.Pane label="Files" defaultSize={25} minSize="12rem">per pane. The handles go in on their own, each named by its pane'slabel, so give every pane one. Sizes are percentages, limits also takepxorrem,orientation="vertical"stacks them (and needs aheight), andcollapsiblewithcollapsed/onCollapsedChangelets a button hide a pane. Put scrolling content in aScrollAreainside the pane. - Content taller or wider than its space is
ScrollArea(release notes in a Card, a sidebar longer than the screen, a feed that grows then scrolls, a wide table on a phone), not aBoxwithoverflowY="auto"and a height in a style:<ScrollArea height={240} aria-label="…">, ormaxHeight="20rem"to grow with its content first. It needsaria-labeloraria-labelledby, since while it overflows it's a region a keyboard user tabs to. The helper props andclassNamego on its frame and therefon the element that scrolls.hasFadefades the edges that have more,orientation="horizontal"suits a wide table, andonEdgeReach={edge => …}loads more at an edge. - Something that stays in a corner of the screen (a floating button, a chat or help launcher,
a feedback tab, a consent notice) is
Affix, notpos="fixed"with offsets in a style:<Affix position="bottom-left"><Button color="primary">Feedback</Button></Affix>.positionis one of the four corners,'bottom-right'by default, and stays physical in right-to-left text. The spacing helpers nudge one further in (mb="6"lifts it over a bottom bar), andportalmoves it out of an ancestor with atransform. Two in one corner overlap, so put what shares a corner in one Affix. Tab reaches it where it is in the markup, whatever corner it shows in, so write it after the main content. For an element pinned once the page scrolls past it, usepos="sticky"with atopinstead. - A command palette (⌘K or Ctrl+K) is
Command.Dialog, not aModalwith anInputand a hand-writtenkeydownlistener:<Command.Dialog shortcut="mod+k" placeholder="…" actions={[…]} />, each action{ id, label, onSelect }withgroup,keywords,description,iconandhint(aKbd.Group) as it needs them. Typing filters the actions by label, keywords and description, Enter runs the top match, and running one closes the dialog.shortcutis off unless given, and it does nothing while the user types in a field. A button that opens it too usesopenandonOpenChange, witharia-keyshortcutson the button. The same list inline, in a page or a Popover, isCommand. For server results, build it from parts:Command.Input, thenCommand.ListofCommand.Items, orCommand.Empty, filtered fromonQueryChange. - A first-visit walkthrough, a "what's new" pass or a "Take the tour" button is
Tour, not aModalper step or aPopovermoved by hand:<Tour open={open} onOpenChange={setOpen} onFinish={…}>with a<Tour.Step target={ref} title="Filters">per step, its body as children. A target is a ref, an element or a selector, and a step without one sits in the middle. By default a step is modal over a dimmed page, so its body says what the target is; giveoverlay={false}(on the tour or one step) when the user should try the control. The app opens it and stores whatonFinishandonOpenChangesay: it doesn't remember who's seen it. - Link lists (footer nav, sidebars): a bare
UnorderedListofListItems is already marker-less and flush — Bulma's reset unstylesul— so no prop or CSS is needed; bullets appear only insideContent. Navbar.Burger/Navbar.Menuare controlled — wire the sameactivestate to both:activeonNavbar.Menushows/hides the mobile menu, whileactive+onClickonNavbar.Burgermake the burger toggle it and animate. Left unwired, clicking the burger does nothing (no error, silent failure). For afixed="top"Navbar, add thehas-navbar-fixed-topclass to<html>so content is not hidden behind it — the library does not do this automatically, and an inline padding offset is not a substitute.- Style with helper props — no inline
style, no raw BulmaclassNames. Before writingstyle={{ … }}anywhere, translate each declaration with the mapping table below — the helper props cover the common cases. Bare markup has wrapper elements that take all helper props:<Span textSize="7" textColor="grey">,Paragraph,Strong— never a raw<span className="is-size-7 has-text-grey">. Table cells:Th/TdtaketextAlign="right",textWeight,textSizedirectly (theircolorprop colors the cell; for muted cell text wrap content inSpan textColor="grey"). Set the app-wide icon library once with<ConfigProvider iconLibrary="…">at the root rather thanlibraryon every<Icon>. An app in another language, or a right-to-left one, also getslanganddiron<html>and a<LocaleProvider locale="…">at the root, so overlays and date pickers follow it. Words a component reads to assistive tech stay English until its label props set them (Steps'completedLabelandupcomingLabel, for one). - Alternating section bands are a prop, not CSS:
bgColor="scheme-main-bis"on every otherSection(next bandscheme-main-ter). The scheme values render as a dark-mode-safe inlinebackground-color: var(--bulma-scheme-*)— zero custom CSS — and still neverbgColor="light"/"white": those are fixed colors that stay light when dark mode flips the text. Decorative CSS is budgeted: two compact rules, ≤10 lines per app — comments count: at most one short inline note, never a file-header comment block — every value derived from
--bulma-*. A marketing page gets at most one hero wash and one featured-card ring, applied viaclassName— no resets (Bulma ships one; body/list margins are already zero) and no grid textures, masks, or multi-layer backdrops; the components carry the design:.hero-wash { background-image: radial-gradient( 60rem 30rem at 20% -10%, hsl(var(--bulma-primary-h) var(--bulma-primary-s) 50% / 0.2), transparent 60% ); } .featured-ring { --bulma-shadow: 0 0 0 2px var(--bulma-primary); }The ring works by overriding the upstream token, not the component's own var:
.cardand.boxre-declare--bulma-card-shadow/--bulma-box-shadowfrom--bulma-shadowon their own selector, so setting those from an ancestor never wins (same for--bulma-box-radius;--bulma-card-radiusis a literal with no ancestor route at all). A class-scoped CSS rule keeps the ring on just the one featured card without wrapping it in its ownTheme;<Theme bulmaVars={{ '--bulma-shadow': … }}>also compiles and is the better fit when the override already applies to a whole scoped subtree. Either way the subtree stays theme- and dark-mode-aware.- CTAs on a colored hero must stay legible in both schemes. On a fixed-color surface
(
Hero color="primary", a dark banner), use filled buttons —color="light"orcolor="primary" isInverted— never a thinisOutlinedsecondary: a light outline + light label on a dark surface is low-contrast and gets worse under OS dark mode. And when the page's design is single-mode (a fixed light or dark look), pin it on the<html>inindex.html,<html lang="en" data-theme="light">, so a visitor's OS dark mode can't flip Bulma's text colors out from under the fixed palette, from the first paint on (details: thebestax-themingskill's contrast rules).
Three components core Bulma will talk you out of
Most of this library's additions get found on their own, because nothing in Bulma does the
job. These three do not: each has a Bulma near-miss close enough to stop the search. Across
44 cold-start builds, Dialog was used zero times and LinkButton in two thirds — and
every miss shipped the "not this" column instead.
| You need | Use | Not this |
| A brief confirmation after an action, self-dismissing | Toast — mount <ToastContainer position="top-right" /> once at the app root, then toast.success('Saved') (also .danger/.warning/.info) from anywhere | Notification/Message |
| A confirm or alert the user must answer before anything | Dialog — mount <DialogContainer /> at the root, then if (await dialog.confirm({ title, message })) … | Modal — an empty shell; the title, message, button row and confirm/cancel wiring are all yours to rebuild |
| A control that reads as text or a link but does something | LinkButton (variant="text" | "ghost" | "underline", optional color) | <a href="#">/<div onClick> (no keyboard or screen-reader support) or Button color="text" (still button-shaped) |
Mounting a container without ever calling toast.*/dialog.* is not usage — the container is
the mount point, the imperative call is the thing that shows something. Both also work as
ordinary controlled components when you would rather hold the state yourself —
<Toast message … duration onClose>, <Dialog isOpen title message type onConfirm onCancel> —
but in an app with more than one call site the root container plus the imperative helper is
less wiring, not more.
Inline style → helper prop mapping
Look up the declaration you were about to inline. The spacing, typography, and flex helpers
below are on every component; textColor/bgColor are on the content components you'll
target (Box, Block, Title, Content, Hero, Card, …) — the ones with a semantic
color variant (Tag, Tabs, Panel) take color instead; wrap content in a Block if
you need a text color there. Notification is the mixed case: it takes textColor, but its
background comes from the semantic color prop, not bgColor.
| Inline style you're about to write | Helper props instead |
marginTop: '1rem' (any margin/padding) | mt="4" — m/mt/mx/p/py/… scale: 1=0.25rem, 2=0.5rem, 3=0.75rem, 4=1rem, 5=1.5rem, 6=3rem (nearest step) |
textAlign: 'center' | textAlign="centered" (also left, right, justified) |
color: '#…' | textColor with the nearest Bulma color: primary, link, info, success, warning, danger, white, black, grey (+ grey-light, grey-dark, …) |
backgroundColor: '#…' | bgColor (same palette) |
fontSize: … | textSize="1"…"7" (1 largest). On Title/SubTitle, as sets the level and size picks it too, so an <h3> at size 4 is as="h3" textSize="4" |
fontWeight: … | textWeight: light, normal, medium, semibold, bold |
textTransform, italics | textTransform: uppercase, lowercase, capitalized, italic |
display: 'flex' + flex properties | same-named props: display="flex", flexDirection, justifyContent, alignItems, flexWrap |
height: '100%' on a flex child | flexGrow="1" |
display: 'none' | visibility="hidden", or responsive display* props (displayMobile, displayTablet, …) |
gap: '1rem' (flex or grid) | gap="2", or one axis: columnGap, rowGap; gap scale: 1=0.5rem, 2=1rem, 4=2rem, half steps ("1.5") |
No helper matches (e.g. maxWidth, a one-off gradient)? Add a named class to the project's
global stylesheet and pass it via className — still never inline style. In a create-bestax
app that is src/index.css, which its entry file imports after bestax's stylesheet, so the
class wins over a Bulma rule of the same weight. The starter page's src/App.css loads after
bestax's too, but only while the starter's App imports it.
References
references/layout-components.md— the layout component inventory: real prop names, types, and accepted values, plus subcomponent nesting.references/archetypes.md— the four archetypes: selection criteria, JSX skeleton, and responsive behavior.
Examples
examples/app-shell.tsx: anAppFramewith aNavbarheader, aMenucolumn and the page (dashboard).examples/landing.tsx— fixedNavbar(controlled burger) +Hero+Sections +Footer.examples/centered.tsx— centered single column (auth/settings).examples/card-grid.tsx— multilineColumnsofCards (catalog).examples/content-page.tsx— hero + feature cards + CTA styled with helper props (no inlinestyle), wrapped inConfigProvider.
Checklist
- Map the request to one archetype; do not ask layout questions.
- Wrap page content in
Container(+Sectionfor vertical rhythm). - Use
Grid/Cellfor uniform grids (equal heights per row, free);Columns/Columnfor proportional or per-breakpoint side-by-side layout — with the flex recipe when its cards must match height. - An app shell is
AppFrame, withAppFrame.BurgerinNavbar.Brand: nofixed, nohas-navbar-fixed-top, and never inside a<main>. - Elsewhere, wire
activestate to bothNavbar.BurgerandNavbar.Menu(they are controlled), and for a fixed navbar addhas-navbar-fixed-topto<html>. - Do not use
Tile— it is not shipped. - Action feedback goes through
Toast, a confirmation throughDialog, a text-styled action throughLinkButton— notNotification,Modalor a bare<a>. - An empty list or a search with no results renders
EmptyState, and a search or a filter keeps arole="status"region beside its field that says the count. - Style with helper props, not inline
style— translate via the mapping table; values with no helper get a named class in the stylesheet, neverstyle={{}}. No raw BulmaclassNames either (Span/Paragraphwrap bare text;Th/TdtaketextAlign/textWeight). - Alternating bands are
bgColor="scheme-main-bis"(next bandscheme-main-ter) on every otherSection— never band CSS, neverbgColor="light"/"white". - Decorative CSS ≤10 lines total incl. comments — no file-header comment (hero wash +
featured-card ring),
--bulma-*-derived; no resets — Bulma ships one. The ring sets--bulma-shadow(via a scoped CSS rule orTheme bulmaVars). - Set the icon library once via
<ConfigProvider iconLibrary="…">at the root. - Site built? ~800 KB raw / ~82 KB gzip CSS is the expected default-flavor size — to shrink
it, run the
bestax-optimizeskill (measure first).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

