brand guidelines
An Anthropic-specific visual identity reference for applying its palette and typography to appropriate artifacts.
Repository star change: +586 over 26.7 hours. 2026-11-01
A Claude Code plugin for turning a visual brief into frontend implementation, with a bundled design skill rather than a separate browser connection.
The checked package exposes frontend design guidance through a Claude Code plugin manifest and a skills directory. Its scoped README describes interface implementation, typography, color and visual direction. This is guidance for the coding agent; the manifest does not establish that the resulting interface has been tested or that it matches an existing product system.
A developer with a concrete interface brief, existing project conventions and an opportunity to inspect the rendered result. Supply the real content, target widths and accessibility expectations before asking for a component or page.
Creative direction can conflict with a mature site's visual language. State which spacing, navigation and brand assets must be preserved. Bundled instructions do not replace browser validation, keyboard checks or review of generated dependencies.
Try one small settings panel in a disposable branch. Give the agent a reference to your current components and a short list of acceptance conditions. Inspect desktop and mobile output before broadening the task.
Confirm focus visibility, text contrast, overflow and the behavior of real controls. Compare the delivered artifact against your brief. This assessment reads package metadata and documentation; it does not run the plugin or certify the frontend it produces.
claude-code
Publisher manifest for claude-code; runtime behavior not tested
Review the publisher setup, permissions, credentials and service costs before use.
Open the pinned package below and follow its publisher instructions for your agent. A Skills installer is not a universal plugin installer. Review hooks, bundled MCP connections, permissions and configuration before enabling the package.
plugins/frontend-design/.claude-plugin/plugin.jsonPresence is a static file/manifest observation. A missing declaration does not prove the component is absent at runtime.
Unknown; source software and connected services may have separate terms.
Unknown — no runtime security assessment.
Only sanitized manifest/registry metadata and bounded documentation are inspected. Package code, transitive dependencies, hooks and remote services have not been audited. Review access before use.
Category-based discovery suggestions. Review functional overlap; these combinations have not been integration-tested.
An Anthropic-specific visual identity reference for applying its palette and typography to appropriate artifacts.
Repository star change: +586 over 26.7 hours. 2026-11-01
A design-direction skill for giving a new interface a deliberate visual identity and reviewing whether the result fits its audience and task.
Repository star change: +586 over 26.7 hours. 2026-11-01
A native interface review guide for Expo screens, semantic colors, controls, icons, media and responsive layout.
Repository star change: +74 over 26.7 hours. 2026-11-01
Category-based discovery suggestions. Review functional overlap; these combinations have not been integration-tested.
Explore landing as an agent plugin package for design & ux. Review its supported format, bundled components and setup requirements before installing.
Explore slo-architect as an agent plugin package for design & ux. Review its supported format, bundled components and setup requirements before installing.
Explore playground as an agent plugin package for design & ux. Review its supported format, bundled components and setup requirements before installing.
Category-based discovery suggestions. Review functional overlap; these combinations have not been integration-tested.
Explore AINDF as an MCP connection for design & ux. Compare the declared transport, package requirements and source evidence before connecting an agent.
Explore dsh-verify as an MCP connection for design & ux. Compare the declared transport, package requirements and source evidence before connecting an agent.
Explore 2nd Brick as an MCP connection for design & ux. Compare the declared transport, package requirements and source evidence before connecting an agent.
Choose a complementary capability only after checking for duplicated permissions and bundled connections. Agent Stacks explain the roles and validation steps; they are proposals, not tested integrations.
Build a stack for your task · Related AI guides · Report a correction