@danieljvdm/dev-kit 1.0.2 → 2.0.0

package/skills/animate/references/principles.md

@@ -0,0 +1,48 @@
+# Motion principles
+
+## Purpose and timing
+
+Motion can acknowledge input, explain a state change, or preserve an element's
+identity across states. Choose the smallest effect that communicates that
+relationship. Keep repeated actions quick and avoid movement that distracts
+from reading or acting.
+
+Use the project's existing timing tokens. As starting points, small press or
+popover transitions often settle in roughly 100–250ms; larger sheets can need
+more time to communicate travel. Judge perceived response and interruption,
+not a universal 300ms cutoff. Long explanatory sequences have different needs.
+
+Ease-out often gives input-triggered motion an immediate response; ease-in-out
+can suit movement between visible positions. Use a spring when retargeting and
+velocity matter. Preserve a deliberate existing curve when it works.
+
+## Spatial continuity
+
+Anchor a popover's scale to its trigger. Centered dialogs can use a centered
+origin. Choose a modest scale offset when scaling a surface; avoid shrinking
+text into illegibility. A pure fade is valid when spatial movement adds no
+information. Match entry and exit paths to the user's spatial expectation.
+
+## Rendering cost
+
+Prefer transform and opacity when they express the intended effect cheaply.
+Some expanding content needs layout changes. Contain and measure that work
+instead of forbidding height animation or replacing it with a distorted scale.
+Scope transitions to intended properties.
+
+Acceleration depends on the property, browser, and animation engine. Check the
+installed library and inspect a trace before claiming dropped frames or forcing
+a rewrite. [Motion's performance guide](https://motion.dev/docs/performance)
+explains rendering and acceleration constraints. Avoid permanent layer promotion
+or `will-change` without evidence it helps.
+
+## Accessibility and interaction
+
+Honor reduced-motion preferences by removing or simplifying movement that can
+cause discomfort. Retain useful state feedback, using an instant change or a
+gentle fade where appropriate. Do not require a fade if the user needs no motion.
+
+Keep focus, keyboard operation, and accessible state synchronized with the
+interaction. Decorative transitions must not delay availability of controls.
+Gate hover-only effects by hover capability; provide equivalent usable touch
+and keyboard behavior.

package/skills/animate/references/review.md

@@ -0,0 +1,19 @@
+# Review motion
+
+Scope the review to the requested diff, component, or application area. Identify
+the product's timing tokens, interaction frequency, and intended behavior.
+Use [principles](principles.md) and [gestures](gestures.md) for relevant decisions.
+
+Report a finding when the evidence shows harm: delayed feedback, jumping on
+interruption, broken focus, unnecessary movement, inconsistent spatial behavior,
+or measured rendering cost. Explain the trigger and user-visible consequence.
+A different easing preference or an arbitrary frequency threshold is not enough.
+
+Prioritize functional and accessibility problems, then responsiveness and
+cohesion. Cite locations and propose the smallest useful correction. A clean
+review is valid. Use a table, prose, or a diff according to what explains the
+findings clearly; give a blocking verdict only when the review calls for one.
+
+When code alone cannot establish how something feels or performs, label the
+uncertainty and identify a focused visual or performance check. Preserve
+documented tradeoffs unless new evidence shows they no longer hold.

package/skills/cloudflare-workers/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/skills/cloudflare-workers/NOTICE

@@ -0,0 +1,9 @@
+Dev Kit adaptation of https://github.com/cloudflare/skills
+Source revision: 30553f89ae1ef1e3c2917cd09d72dac992bb4e9a
+Apache License 2.0 retained in LICENSE.
+
+Modified by Dev Kit: scope-specific entrypoints and references replace copied
+manuals, automatic setup changes, and blanket implementation prescriptions.
+Use the target repository's versions, command authority, and testing policy.
+
+Combines workers-best-practices, durable-objects, wrangler, and sandbox-sdk.

package/skills/cloudflare-workers/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: cloudflare-workers
+description: Build, review, or operate Cloudflare Workers, Durable Objects, and Sandbox SDK applications with Wrangler.
+license: Apache-2.0
+---
+
+# Cloudflare Workers
+
+Use the repository's architecture, commands, installed types, and runtime
+compatibility settings. Current documentation explains APIs; a maintenance task
+does not by itself call for a dependency or compatibility-date upgrade.
+
+Read for the changed boundary:
+
+- Worker handlers, streams, bindings, and verification: [Workers](references/workers.md).
+- Durable Object identity, storage, alarms, and WebSockets: [Durable Objects](references/durable-objects.md).
+- Wrangler commands, environments, deployment, and secrets: [Wrangler](references/wrangler.md).
+- An application using `@cloudflare/sandbox`: [Sandbox SDK](references/sandbox.md).
+  Ordinary commands inside an agent sandbox do not require the SDK.
+
+Resolve the account, environment, and local or remote target before mutations.
+Preserve deployed storage migrations, existing authorization, and host ownership
+of task containers, previews, authentication, and capability URLs. Follow the
+repository's testing policy and verify the behavior at its actual runtime boundary.
+
+Attribution is in [NOTICE](NOTICE); terms are in [LICENSE](LICENSE).

package/skills/cloudflare-workers/references/durable-objects.md

@@ -0,0 +1,68 @@
+# Durable Objects
+
+Identify the object's identity, coordination scope, durable state, and callers. Preserve existing class and storage migration history.
+
+## State and concurrency
+
+Choose an object boundary around the entities that need coordination. Separate
+independent entities when scale requires it; a bounded singleton can still be an
+intentional coordinator. Evaluate its traffic and responsibilities before
+calling it a bottleneck.
+
+Use durable storage for state that must survive eviction or failure. Memory may
+cache durable values but cannot be the only record of acknowledged durable work.
+Prefer SQLite for new objects when appropriate; retain existing migration history
+and plan a storage migration explicitly for deployed classes.
+
+Understand input and output gates for the storage APIs in use. Synchronous
+SQLite operations without an intervening await can have different guarantees
+from operations separated by asynchronous work. Use a transaction for the
+required atomic unit. Avoid a blanket rule that every await breaks atomicity.
+
+Keep `blockConcurrencyWhile` short and tied to initialization or a specific
+invariant. Avoid external network work while holding it. Reconstruct necessary
+state after eviction and make initialization safe to repeat.
+
+Check schema changes against existing data, including partially completed
+upgrades when relevant. Consult the [rules of Durable Objects](https://developers.cloudflare.com/durable-objects/best-practices/rules-of-durable-objects/)
+and the installed storage API before relying on concurrency guarantees.
+
+## Calls and lifecycle
+
+Use typed RPC for service calls where supported. Retain HTTP handling when the
+transport requires it, such as an incoming WebSocket upgrade. Keep caller
+authentication and authorization at the actual trust boundary.
+
+Route repeat calls using the same intended object identity. Persist any mapping
+needed to recover an opaque generated ID. Changing naming or namespaces can
+route traffic to a different object with different storage.
+
+An object has one alarm time; setting it replaces the previous alarm. If the
+application owns multiple deadlines, keep those deadlines in durable state and
+schedule the next due time. Make alarm work safe under retries and interrupted
+execution. External side effects need their own deduplication strategy.
+
+Use hibernating WebSockets when that fits the connection lifecycle. Reconstruct
+connection metadata from durable state or supported attachments after waking.
+Do not assume a constructor, in-memory map, or ordinary timer survives eviction.
+Handle close and error paths without leaving stale application presence.
+
+Inspect the relevant [alarm](https://developers.cloudflare.com/durable-objects/api/alarms/)
+or [WebSocket](https://developers.cloudflare.com/durable-objects/best-practices/websockets/)
+documentation when modifying those behaviors.
+
+## Verify the boundary
+
+Follow repository policy for test placement and whether a committed regression
+is warranted. Reuse the existing Worker test environment and generated bindings.
+Avoid creating a standalone test configuration beside an established one.
+
+Choose verification based on the changed behavior: RPC response and failure,
+durable data after a new instance, retry-safe alarm handling, or connection
+state after hibernation. Include real migrations when schema behavior matters.
+In-memory mocks alone cannot establish platform storage or lifecycle semantics.
+
+Use [Cloudflare's testing guidance](https://developers.cloudflare.com/durable-objects/testing/)
+for runtime-specific helpers, checked against installed versions. Exercise the
+running application when tests are not warranted. State when eviction, retries,
+or multi-request coordination remain unverified.

package/skills/cloudflare-workers/references/sandbox.md

@@ -0,0 +1,48 @@
+# Cloudflare Sandbox SDK
+
+Inspect the installed SDK, Worker bindings, image, and lifecycle owner. Docker is relevant to local container execution, not every remote SDK or documentation task. Preserve host ownership of containers and previews.
+
+## Sandbox setup
+
+Inspect the existing Worker entrypoint, Durable Object binding and migrations,
+container image, and instance settings. Export the Sandbox class or the project's
+subclass in the way required by the installed SDK. Match the binding to that
+export; preserve deployed class names and migration history.
+
+Select the image and SDK versions together using the project's lock and image
+policy. Check compatibility before upgrading. Add only dependencies needed by
+the workload; avoid pinning all projects to an example image tag or capacity.
+
+Use Docker when exercising local container behavior. Prefer the repository's
+existing local or deployed test route and report a missing capability when it
+prevents verification. Do not install infrastructure just to inspect SDK code.
+
+For new setup or a missing platform detail, use [the SDK getting-started guide](https://developers.cloudflare.com/sandbox/get-started/)
+and [examples](https://github.com/cloudflare/sandbox-sdk/tree/main/examples).
+Treat them as examples to adapt to the target repository.
+
+## Execution and resource ownership
+
+Choose a sandbox identity that matches the intended user or task isolation.
+Reusing an ID can reuse state; a container boundary does not authorize sharing
+one user's files or interpreter context with another.
+
+Use command execution for shell workloads and interpreter contexts for stateful
+language execution with structured results. Inspect the installed API for
+timeouts, streaming, cancellation, exit codes, and file path semantics. Handle
+process failure explicitly instead of treating successful transport as a
+successful command.
+
+Track the lifetime of processes, contexts, and exposed ports. The owner of a
+temporary resource cleans it up, including on cancellation or partial failure.
+Keep a user-requested persistent session alive. Do not destroy a host-managed or
+shared sandbox merely because one command finished.
+
+Expose a port only when the task calls for it and the host permits it. Treat
+preview URLs as capabilities and publish them only through the host's approved
+path. Diagnose domain and exposure settings from the current
+[service exposure guide](https://developers.cloudflare.com/sandbox/guides/expose-services/).
+
+Before retrying a command that may have written data, inspect its outcome or
+use an idempotent operation. Stop when cleanup or authorization cannot be
+established and report the exact resource still outstanding.

package/skills/cloudflare-workers/references/workers.md

@@ -0,0 +1,63 @@
+# Workers runtime
+
+Follow installed generated types and the repository command authority.
+
+## Worker runtime boundaries
+
+Keep request-specific state and I/O resources within the request or an explicit
+application lifetime. Immutable constants can be shared; mutable globals must
+not leak one request's identity or data into another.
+
+Stream large or unbounded bodies rather than buffering them. Preserve stream
+cancellation and backpressure, and avoid consuming a body twice. Bound work
+that depends on client-controlled sizes or upstream responses.
+
+Await work required for the response. Use the execution context for permitted
+post-response work that fits its lifetime. `void` alone does not keep a Promise
+alive or handle its failure. Use durable execution such as a queue or workflow
+when the work must outlive that request lifetime.
+
+Keep authentication, decoding, and error mapping at the appropriate boundary.
+In Effect applications, preserve the existing service and Layer ownership.
+Do not force a plain async example into an established Effect handler design.
+
+Use the installed types and relevant [Workers runtime documentation](https://developers.cloudflare.com/workers/runtime-apis/)
+to check limits and API behavior that affect the task.
+
+## Worker configuration
+
+Use generated binding types and the effective configuration for the target
+environment. Prefer service and resource bindings when available; use external
+APIs where the integration requires them. Preserve existing database connection
+ownership and evaluate Hyperdrive only for the relevant connection needs.
+
+Add compatibility flags when required by the dependencies actually in use.
+Treat compatibility-date changes as runtime changes with their own verification.
+Keep secrets in the repository's configured secret store or binding mechanism.
+
+For error capture, structured logs, tracing, sampling, and sensitive fields,
+follow the repository's reporting policy. A narrow Worker edit is not a reason
+to install another telemetry system or change global sampling.
+
+Retrieve the relevant [Workers best practices](https://developers.cloudflare.com/workers/best-practices/workers-best-practices/)
+when a platform-specific question remains. Validate signatures against the
+installed toolchain instead of downloading newer types to judge older code.
+
+## Review and verification
+
+Trace the changed request or event path, the capabilities it uses, and its
+failure and cancellation behavior. Check configuration only where it affects
+that path. Cite the concrete failure or risk in each finding; unrelated
+hardening is not a prerequisite for completing the requested change.
+
+Inspect surrounding code when needed to establish ownership. For uncertain API
+behavior, consult installed declarations and the relevant official documentation
+before reporting a violation.
+
+Run the repository's required commands. Exercise the affected handler with its
+actual runtime or the project's existing integration setup when needed.
+Use the repository's testing policy to decide whether to add a regression test;
+a new Worker does not imply a new test suite.
+
+Report what ran, the observable result, and any runtime behavior left unverified.
+Keep an audit read-only unless fixes are also requested.

package/skills/cloudflare-workers/references/wrangler.md

@@ -0,0 +1,56 @@
+# Wrangler
+
+Use the declared Wrangler version and command entrypoint. Inspect the relevant script, config, and installed help before composing arguments. With Vite+, use the repository task or `vp exec wrangler`. Install a missing tool only when the requested task needs it.
+
+## Configuration and local development
+
+Locate the owning Worker config and environment before changing a binding.
+Prefer JSONC for new configurations when it fits repository conventions;
+preserve an existing format for unrelated edits. Check fields against the
+installed Wrangler config schema and regenerate binding types through the
+repository's normal command after changing them.
+
+Compatibility dates and flags change runtime behavior. Preserve the selected
+date during routine edits. When an upgrade is requested or required, read the
+relevant compatibility changes and verify affected behavior rather than setting
+today's date automatically.
+
+Inspect local and remote binding settings before starting development. Local
+development can reach real services when remote bindings are enabled. Keep
+private temporary servers separate from any preview managed by the host.
+Reuse an existing dev process when it exercises the change.
+
+Use the installed CLI's help for flags and subcommands. The repository's scripts
+own ports, environment names, credential loading, and generated file locations.
+Do not create a second workflow merely to reproduce an example from this skill.
+
+References:
+
+- [Configuration](https://developers.cloudflare.com/workers/wrangler/configuration/)
+- [Compatibility dates](https://developers.cloudflare.com/workers/configuration/compatibility-dates/)
+- [Local development](https://developers.cloudflare.com/workers/development-testing/)
+
+## Operations
+
+Identify the selected account, Worker or resource, environment, and local or
+remote target. An environment flag does not guarantee every resource setting
+is inherited; inspect the effective config and binding before acting.
+
+For a deployment, use the repository's release procedure and required checks.
+Use a dry run when it materially checks packaging or bindings. A dry run does
+not prove runtime behavior or authorize deployment. Reuse any deployment
+authorization already present in the task.
+
+Preview the target and impact of deletion, migrations, or resource replacement.
+Use existing backup or recovery procedures where the operation calls for them.
+Inspect versions before a rollback; code rollback may not undo data changes.
+
+After a timeout or partial failure, inspect the resulting resource or deployment
+before retrying a mutation. Retry only the missing work. Stop and report the
+remaining state when access is unavailable, the target is ambiguous, or further
+retries could duplicate consequential work.
+
+Use protected input or the repository's secret integration for credentials.
+Preserve existing authentication instead of starting an interactive login
+unnecessarily. Report deployment and resource identifiers without exposing
+secrets or private preview capabilities.

package/skills/design-ui/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Emil Kowalski
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/design-ui/NOTICE

@@ -0,0 +1,8 @@
+Dev Kit adaptation of skills from https://github.com/emilkowalski/skills
+Source revision: 70744e3816f1d93eafb697161a8b880a7384c5ff
+Copyright (c) 2026 Emil Kowalski. MIT license retained in LICENSE.
+
+Modified by Dev Kit to preserve task scope, share motion workflows, use
+progressive disclosure, and follow repository-owned tools and state policy.
+Combines apple-design, emil-design-eng, prototype, and pick-ui-library.
+Motion mechanics are consolidated in animate.

package/skills/design-ui/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: design-ui
+description: Build or refine web UI, explore design alternatives, or choose UI libraries and theme handling.
+license: MIT
+---
+
+# Design web UI
+
+Follow the brief and the product's design language. Implement a requested change;
+keep a review to findings unless implementation is also requested.
+
+Read only what the task needs:
+
+- Control behavior, focus, feedback, and content states: [components](references/components.md).
+- Typography, hierarchy, depth, or Apple-inspired materials: [appearance](references/appearance.md).
+- Requested design alternatives or a visual comparison picker: [exploration](references/exploration.md).
+- Requested library selection: [libraries](references/libraries.md).
+- Theme switching, persistence, first paint, or hydration: [themes](references/themes.md).
+
+Use the existing tokens and adequate dependencies. Library selection and multiple
+prototypes are optional workflows, not prerequisites to polishing a component.
+For detailed motion work, use `animate` when available, or consult the installed
+animation library and [Emil's motion guidance](https://emilkowal.ski/ui/you-dont-need-animations).
+
+Judge the changed interaction in context with realistic content, keyboard input,
+and relevant viewport sizes. Preserve deliberate product choices and report what
+could not be verified.
+
+Attribution is in [NOTICE](NOTICE); terms are in [LICENSE](LICENSE).

package/skills/design-ui/references/appearance.md

@@ -0,0 +1,22 @@
+# Hierarchy and typography
+
+Use depth and translucency to explain layering, such as a sheet over content.
+Keep text contrast and boundaries legible over changing backgrounds. Prefer a
+solid surface when blur adds cost or weakens readability. Respect relevant
+contrast and transparency preferences where the platform exposes them.
+
+Choose type size, weight, line height, and tracking as a system. Check the
+font's optical sizing support before manually compensating at display sizes.
+Headings may benefit from tighter tracking; body text often needs a neutral
+setting. Inspect the actual font and content instead of prescribing one value
+or banning consistent tracking across a working type scale.
+
+Use spacing and alignment to communicate groups before adding decorative
+borders. Preserve familiar control locations and interaction conventions for
+the target platform. Test small windows, long labels, and larger text when
+these affect the design.
+
+References:
+
+- [Apple typography guidance](https://developer.apple.com/design/human-interface-guidelines/typography)
+- [Apple materials guidance](https://developer.apple.com/design/human-interface-guidelines/materials)