Skip to content

docs(design): require the Clay design skill for UI work - #579

Merged
chadbyte merged 1 commit into
mainfrom
docs/clay-design-skill
Oct 9, 2026
Merged

chadbyte merged 1 commit into
mainfrom
docs/clay-design-skill

Conversation

@chadbyte

@chadbyte chadbyte commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Clay UI work should follow the project's agreed design principles and compact product patterns. Add a project instruction to use the owner-level clay-design-skill and its visual references, and to report a missing installation instead of substituting frontend-design.

The skill and self-contained HTML studies remain outside this repository at ~/.clay/skills/clay-design-skill/, as requested. This PR contains only the project routing rule; it does not distribute those owner-local files or change production UI.

Validation: git diff --check passed. Skill metadata validation, Clay owner-scope discovery, local reference integrity, and an independent instruction review passed during skill creation.

Direct Clay UI design and review to the owner-level skill and its
preserved examples. Keep the skill outside the repository and avoid
substituting frontend-design when the reference is unavailable.
@chadbyte
chadbyte merged commit 014d63b into main Oct 9, 2026
2 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

This issue has been resolved in version 5.1.0-beta.2 (main).

To update, run:

npx clay-server@5.1.0-beta.2

-- Clay Deploy Bot

Build anything, with anyone, in one place.

@github-actions

Copy link
Copy Markdown
Contributor

This issue has been resolved in version 5.1.0 (stable).

To update, run:

npx clay-server@5.1.0

-- Clay Deploy Bot

Build anything, with anyone, in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant