frontend-design
Distinctive, production-grade interfaces that avoid the generic generated look: subject-driven direction, typography, palette, restrained motion and interface copy, built inside the locked design system.
Reference
| Field | Value |
|---|---|
| Name | frontend-design |
| Version | 1.0.0 |
| Category | Development |
| Licence | Not declared |
| Source | catalog/navin/builtin_plugins/frontend-design/plugin.json |
| README | catalog/navin/builtin_plugins/frontend-design/README.md |
| Digest | sha256:1ceeb2eea91f6c06df54889a218e411d9091f9c2399ba09c96634e123a176bb0 |
| plugin.json | category, description, name, skills, steps, version |
Commands
The plugin declares no command.
Agents
The plugin declares no agent.
Skills
| Name | Description |
|---|---|
| frontend-design | Gives a new or reworked interface a distinctive, deliberate visual identity instead of a templated look - subject-driven aesthetic direction, typography, palette, layout, restrained motion and interface copy, planned as a token system and critiqued before code. |
| ui-ux-pro-max | Default web UI/UX design intelligence for Navin. Design-system generator (84 styles, 192 palettes, typography, landing patterns, UX rules) plus mandatory framer-motion for all web sites. |
| make-interfaces-feel-better | Design engineering principles for making interfaces feel polished. |
Hooks, MCP servers and settings
plugin.json declares no hook, no MCP server and no setting: the plugin is made of the components above only.
Workflow
| Step | Use |
|---|---|
| choose a visual direction for a new interface | skill:frontend-design |
| search styles, palettes and font pairings | skill:ui-ux-pro-max |
| polish the finished interface | skill:make-interfaces-feel-better |
Enable it in a project
Activating frontend-design creates 4 activations in the project: the plugin itself and 3 skills. Removing the plugin activation removes them all.
curl -X POST <control-plane-url>/v1/projects/<project>/navin-library/activations \
-H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
-d '{"kind": "plugin", "name": "frontend-design"}'
<project>: id or slug of the project. <token>: API key with the editor role on the project.
client.navin_library.activate("<project>", "plugin", "frontend-design")