Full grading rubric

Template rubric 1.4 scores seven categories for 100 points. Aim for 100; B (75) is the publication floor, not the target. Each category below lists its weight. Never award points for anything you did not inspect.

Keep improving while a deduction has a reasonable fix. A score below 100 is fine only when the remaining tradeoff is intentional and recorded. A template is not ready if the copied file fails to build or a required asset is missing, whatever its score.

Version 1.4 counts public integration components as Astryx components and grades assets and imports after the copy. Record the version with every score so results stay comparable.

Count every JSX opening tag in the copied .tsx source. An Astryx element is a component imported from @astryxdesign/core or from a public component export of the integration package. A raw HTML element is any lowercase intrinsic JSX tag. Count occurrences, not only unique tag names.

Do not count fragments or a PascalCase helper defined in the same file. Inspect that helper and count the raw HTML inside it. For each raw element, decide whether it is necessary because Astryx has no equivalent, or unnecessary because an Astryx component can replace it.

• Do not deduct for an img when no general Astryx image component fits and its source passes the Image handling category.
• Do not deduct for a form that wraps FormLayout to provide native submission semantics.
• Do not deduct for input type="hidden" when it carries native form state.

Count raw icon markup in the copied file. astryx docs cli/integrations/building-blocks/templates/build-the-template/template-assets/template-icons shows how to render icons through Astryx instead.

• Count every raw svg, path, circle, rect, line, polyline, polygon, ellipse, or g used as an icon.
• Count an inline SVG component defined in the template.
• Count an icon component rendered directly instead of through Icon or an Astryx icon prop.

Prefer Astryx component props and design tokens. Count individual CSS properties inside stylex.create and inline style objects. Count each className and stylex.props use once. Do not count Astryx props such as gap, padding, variant, size, color, level, columns, contentPadding, or height.

This category scores styles authored in the copied source. A package stylesheet is graded through its effect on portability and the rendered app, not as a way to hide custom declarations from this count.

1. Use Layout or Center as the page root. A template whose category starts with Shell - uses AppShell because global chrome is its purpose.
2. Outside a Shell - template, leave global navigation to the host app. Put in-page navigation in a LayoutPanel and page headings in LayoutHeader.
3. Use Grid with columns={{minWidth: 280}} for responsive collections. Do not fix the column count or rebuild the grid in raw CSS.
4. Use Center for centered content instead of custom flexbox workarounds.
5. Render one page from one source file. Links may be inert examples, but the template does not create nested routes or router integration.

1. Do not wrap a block in AppShell. A block renders inside a preview or page container.
2. Keep the block focused on one pattern or component usage.
3. Keep the composition substantial enough to teach the pattern and small enough to adapt. About 20-100 lines is the normal range.

Score field accuracy for 6 points, the description for 3 points, and naming for 1 point. Read the source and doc together. A field that exists but disagrees with the source is not complete.

• Page: type, name, displayName, description, explicit isReady, and a specific category when the page is meant for browsing.
• Block: type, name, displayName, description, explicit isReady, positive aspectRatio, and complete componentsUsed.
• Relationship and preview fields follow astryx docs cli/integrations/building-blocks/templates/document-the-template/block-template. A value that contradicts that guide is an inaccuracy.

A strong description covers four slots: the archetype, the job someone does, the structural or behavioral differentiator, and the alternate words people may search. Use at least six distinct content words after removing generic words such as page, screen, app, view, and component names. Describe the reusable shape, not only the sample data.

The id follows astryx docs cli/integrations/building-blocks/templates/start-a-template, displayName is readable, and a browsable page has a specific category (astryx docs cli/integrations/building-blocks/templates/document-the-template/page-template). Slug length is guidance, not a scored condition.

Inspect every image reference in the copied file against astryx docs cli/integrations/building-blocks/templates/build-the-template/template-assets/template-images-media.

Award 2 points for each condition. Grade the copied file, not only the package source.