Name: core
Author: YashjitPal

Imported from YashjitPal/Willow (platform/core/AGENTS.md). Install upstream with npx skills add YashjitPal/Willow --skill core. Copyright stays with the author.

platform/core

Utility functions, types, and constants used everywhere. No UI, no state, no side effects — just the shared vocabulary that both features/ and platform/ depend on.

Files

Path	Role
`src/types.ts`	TypeScript interfaces used across features. `StudioExperience`, etc.
`src/utils.ts`	`cn()` (clsx + tailwind-merge) and other pure functions.
`src/layout.ts`	Sidebar width constants.
`src/color.ts`	Color manipulation (hex ↔ RGB, interpolation).
`src/attachments.ts`	File → base64 data URL, MIME type detection.
`src/display-name.ts`	`getDisplayName(user)` — falls back to email if name is missing.
`src/dialog-focus.ts`	Focus-trap helpers for modals.
`src/json-schema.ts`	JSON Schema → TypeScript type inference helpers.
`src/error-store.ts`	Nanostore for global error toasts.
`src/workspace-theme.ts`	Centralized workspace theme registry and automated OKLCh color engine.

Adding Workspace Colors

Willow workspace theming is 100% automated. All derivative assets (glow accents, send/submit button states, horizontal top loadbars, creamy agent card icons, text selection tints, logo filters, and settings swatches) are computed automatically using perceptual OKLCh formulas.

To add a new workspace color in the future:

Add an entry to WORKSPACE_COLOR_DEFINITIONS in src/workspace-theme.ts:
```
{ id: 'amber', label: 'Warm Amber', hex: '#f59e0b' }
```
Extend the UserProfile.workspaceColor union type in platform/auth/src/AuthContext.tsx if desired for strict typing.
No UI components or CSS classes need manual editing — everything binds dynamically through getWorkspaceTheme(color).

Dependency constraint

platform/core must never import from features/ or apps/. It may import sibling platform packages, and that is all. If you are tempted to reach up into a feature, stop — the abstraction belongs here, and the feature calls it.

What goes here

Types that appear in more than one platform package or feature.
Pure functions with no I/O, no fetch, no localStorage.
Constants (layout dimensions, magic numbers).

What does not go here: React components (those are platform/ui), API clients (those are the feature or platform/ai), storage logic (that is platform/storage).

Related packages

Imported by:

apps/studio — the host shell: routing, sidebar, settings
features/agent-builder — the Agents workflow canvas
features/auth — login / account UI
features/chat — the standalone chat surface
features/code — the Workbench: sandbox and visual editing
features/design — the design surface
features/media — AI image and video generation
platform/storage — persistence, adapters, sync
platform/ui — shared components

Repo-wide conventions, the layering rule and the full package table live in the root AGENTS.md.

Install core and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "yashjitpal-willow-core", "kind": "skill", "name": "core", "description": "Utility functions, types, and constants used everywhere. No UI, no state, no side effects — just the shared vocabulary that both `features/` and `platform/` depend on.", "publisher": "YashjitPal", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Utility functions, types, and constants used everywhere. No UI, no state, no side effects — just the shared vocabulary that both `features/` and `platform/` depend on." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/YashjitPal/Willow", "path": "platform/core/AGENTS.md", "ref": "b04d83b1e8933215608b6a79cd61fefaec5295fe", "url": "https://github.com/YashjitPal/Willow/blob/b04d83b1e8933215608b6a79cd61fefaec5295fe/platform/core/AGENTS.md", "key": "YashjitPal/Willow/platform/core/AGENTS.md" } }, "instructions": "# platform/core\n\nUtility functions, types, and constants used everywhere. No UI, no state, no side\neffects — just the shared vocabulary that both `features/` and `platform/` depend on.\n\n## Files\n\n| Path | Role |\n| --- | --- |\n| `src/types.ts` | TypeScript interfaces used across features. `StudioExperience`, etc. |\n| `src/utils.ts` | `cn()` (clsx + tailwind-merge) and other pure functions. |\n| `src/layout.ts` | Sidebar width constants. |\n| `src/color.ts` | Color manipulation (hex ↔ RGB, interpolation). |\n| `src/attachments.ts` | File → base64 data URL, MIME type detection. |\n| `src/display-name", "cost": { "context_tokens": 817 } }

core

About

platform/core

Files

Adding Workspace Colors

Dependency constraint

What goes here

Related packages

Install core and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews