Design frameworks
Fit an accepted interface to the components, tokens, and constraints a real project already provides.
How can the existing system express the accepted product decision?
A narrow job with a visible boundary
Use it after the job, concept, and prototype are settled enough to implement, or to restore framework compliance.
Input
An accepted prototype, evidence references, and an installed design system, registry, Storybook, or supported adapter.
Outputs
- A capability-probed component catalog
- A fit plan with exact operations
- Native validation receipts and explicit limitations
Boundary
The framework may report that it cannot express the concept. It may not redesign the product to make its component library look sufficient.
Invocation
humane:design-frameworks
See the decision change
Probe the installed library, map accepted behavior to native resources, and report the missing capability as a deviation before changing the flow.
The product decision remains above the component system.
1 / 2- Library-led redesign
Replace the flow with the closest component in our library.
Probe the installed library, map accepted behavior to native resources, and report the missing capability as a deviation before changing the flow.
- Assumed capability
Storybook probably has the required date range picker.
Read the project-local Storybook manifest and installed types. If the component is absent, mark it not supported and propose an exact alternative.
Run the skill by name
Install the Humane pack once, then name this skill when the task reaches its boundary.
humane:design-frameworks