Developer-tools MCP server
buoy
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 2
- 0
- 0
- 3
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @buoy-design/cli@0.8.25
- Registry
- npm
- Published
- Nov 14, 2026
- Integrity
sha512-CibrRZQODQfsj9RGs/wxot1Thr0gmgICmLVOG0oRcfGv/7FKFIW95FqnUcT0sd2Z8JS+3861FahqgFmyOxcs8Q==- Analyzer
- modelara v0.1.8 · policy not recorded
- Repository
- https://github.com/ahoybuoy/buoy
5 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
check_ui_against_design_systemahoybuoy-buoy:tool:check_ui_against_design_systemObserved interface and hashesAfter you edit UI code, check it against this repository's design system before you finish. Returns every hardcoded color, spacing, font, radius or shadow that should be a token, with the token to use. When an issue has an `edit`, replace line `edit.line` (currently `edit.before`) with `edit.after` exactly; it is a verified one-line swap. Pass the files you edited to check only those (fast); omit files to check the whole repository. Re-run until it reports no issues. Input schemasha256:294b81449fce6eed23fe516a967a5118bb757dcbd40c8544bfec2c9ab87b4dd6Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.8.23 | No change observed | |
context_for_fileahoybuoy-buoy:tool:context_for_fileObserved interface and hashesBefore you edit a UI file, get only the design context it needs: tokens the file already uses, tokens its neighbours use, the scale steps for the kinds of values it contains (spacing, type, radius), components in the same folder or already imported that you should reuse, the drift already in it, and the team's decisions (values they chose to keep, which you must not replace, and values they always want flagged). Much smaller than the full token list. Then write values from it and run check_ui_against_design_system on the file. Input schemasha256:4d09a12cd50f1ef74e9ea39a9be1ca32a7d3aecf45b7d95ffda65bd820f2dc37Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.8.23 | No change observed | |
design_system_contextahoybuoy-buoy:tool:design_system_contextObserved interface and hashesRead this once at the start of any task that builds or changes UI. A Markdown summary of this repository's design system: token categories with example names, the existing components to reuse before creating new ones, and the patterns to avoid. Input schemasha256:96f175a981119c5e48bc423e0293858afc10da5bd25b8c883247c708f157baf5Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.8.23 | No change observed | |
find_token_for_valueahoybuoy-buoy:tool:find_token_for_valueObserved interface and hashesBefore you write a literal CSS value (for example '#1a73e8', '16px', '0.5rem'), find the design token in this repository that already holds it, and write the token instead. An empty result means no token has that value; pick the nearest one from list_design_tokens rather than inventing a new value. Input schemasha256:b8e659ce1ca97f5c50e7d4126b8ceb859a6b423e3452ac9ac91ce44b993e6d2eOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.8.23 | No change observed | |
list_design_tokensahoybuoy-buoy:tool:list_design_tokensObserved interface and hashesGet this repository's design system: the colors, spacing, typography, radius, shadow and motion values it defines (CSS custom properties, Tailwind theme, tokens.json, Sass variables, DESIGN.md). Without arguments it returns a short summary (counts plus a few tokens per category) to keep context small; pass a category or name substring for the full list. When you are about to edit a specific file, prefer context_for_file, which returns only what that file needs. Repos with no tokens get the values their code already uses most. Categories: color, spacing, typography, shadow, border, sizing, motion, zIndex. Input schemasha256:5ce82ce41c54b3446da9d75cb3a921ac6efc00b3c7c03cc980bd524eacea27e5Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.8.23 | No change observed |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 0.8.24 0.8.25PASS0 added0 removed0 schema0 write0 destructive0 unknown
- 0.8.23 0.8.24PASS0 added0 removed0 schema0 write0 destructive0 unknown