@reqvire-org/ads 0.0.0-stage → 0.2.9

package/dist/skills/ads-break-ui/SKILL.md

@@ -0,0 +1,235 @@
+---
+name: ads-break-ui
+description: Stress-test a project's local design-system components or patterns with extreme realistic content, empty and failure states, narrow containers, and accessibility settings. Build development fixtures, report layout failures, and fix them when requested.
+---
+
+Exercise the real component through its public API. Accept an item name, screen,
+file, or local project path; discover the relevant exports and usage when the
+request already identifies the target.
+
+## Discover the target
+
+When ADS MCP is connected, `ads_status`/`ads_catalog` identify public UI, guides and
+addressable scenarios. Registered Apps use project-built fixtures; verify the
+actual interactive view, not merely HTML delivery. Use the normal showcase for
+unsupported Apps features or required viewport/keyboard tests. Resolve served
+skill references relative to this `SKILL.md` URI and load them lazily; reading
+instructions does not establish native activation.
+Use the returned `projectRoot` and `project.commands`; the connected ADS may be
+inside a different or nested repository. Inspect the selected public API, owning
+source/available guides and relevant tokens, then mount its discovered scenario.
+Metadata and source reads do not prove rendered behavior.
+
+When `ads_status.mutations.enabled`, discover the owner with `ads_units`, read
+relevant ranges with `ads_read_file` and send only a Git unified diff through
+`ads_apply_patch({ unit, patch, dryRun })`. A unit includes its own implementation,
+scenarios and fixtures; imported peers remain separate. `tokens` is the token
+foundation unit. Unit discovery and file ownership are distinct from preview IDs.
+Include only that owner's required re-exports in the public entry. Use
+`dryRun: true` to inspect validation; applying re-runs the gates. Fix rejected
+patches in their owner. Shared styles/helpers use `foundation`, root guides use
+`documentation`, and branding/fonts use their discovered `assets/*` unit.
+Intentional configuration, rule exceptions, registered guard code and compiler
+changes use `configuration`; validate the proposed settings and keep mandatory
+ADS gates. For binary/large assets, generate `git diff --binary --full-index` into
+`.ds/patches/<name>.patch` and send `patchFile` instead of inline `patch`, so bytes
+stay out of model context. Binary changes require Git. When editing is disabled,
+use the client's normal source-editing tools.
+
+Before trusting a preview after edits, check `ads_status.build` or
+`ads://project/build`. Fix build diagnostics in owned source; an older view or
+unreported freshness is not evidence of current code. Notifications may not
+reach the agent.
+
+Read `docs/ARCHITECTURE.md` when present (or the existing architecture guide), the project's ADS guide, public barrel, item README, existing showcase/test
+harness, and package scripts. ADS is tooling; the project owns components,
+patterns, and token values. An empty ADS has no components to stress-test. Report
+that gap rather than installing a UI library or importing a catalogue.
+
+Identify the actual layout constraints and supported input domain. Separate a
+component defect from invalid application data, missing application validation,
+or a caller violating the documented API. Never change production data or
+backend validation just to create a stress case.
+
+React and native Preact are supported. Preserve the target runtime in both
+production and scenario builds; never alias React to Preact just to shrink a
+preview. Native Preact uses its own JSX transform, hooks and DOM events (live
+text updates use `onInput`). Native SVG uses DOM names such as `stroke-width`,
+not React presentation aliases. Keep Linaria extraction and the same public APIs.
+The shipped empty starter uses React; the tool repository's working example
+uses Preact. Neither is a component dependency of the receiving project.
+
+## Choose the work
+
+- Default: create or reuse development fixtures, exercise them, and report.
+- `data only`: provide fixtures for the requested data shape without editing UI.
+- `+fix`, or a request to fix: implement relevant findings in their owning layer
+  and rerun the failing cases. Existing authorization to fix is sufficient.
+
+Read [references/catalog.md](references/catalog.md) for the relevant categories;
+select plausible extremes rather than applying the whole catalogue to every
+control. Its failure notes are diagnostic prompts; the local API and domain
+contract determine the expected behavior. Use local data shapes and realistic locales.
+Keep baseline, worst-case,
+empty, and boundary cases distinct so the cause of a failure stays visible.
+
+## Exercise and diagnose
+
+Use the project showcase as the shared review surface for agents and humans.
+Scenarios import the same public ADS components/patterns and foundation
+styles as the app. Use the built-in client and the project compiler.
+An isolated harness is useful for diagnosis; retain useful regression cases in
+the project showcase. A static HTML imitation cannot verify the component.
+Keep fixture switches and test data out of production runtime exports. If useful,
+let the development harness select a fixture through a query parameter so a
+failure is reproducible.
+
+Scenarios own sample data and example selection. Missing reusable UI belongs in the
+ADS implementation and public exports, not in a scenario-only control. The tool supplies the neutral client shell; reusable scenario review layouts
+are public project ADS entities.
+Showcase/scenario files define no CSS, custom classes, or widget markup. Change
+the owning ADS frame pattern when a necessary layout is missing. Run shared ADS/project guards for its build and the app
+build, then give a full running URL or exact run command for human review.
+
+The showcase is a minimal shell plus an MCP client and Apps host, supplied by ADS
+tooling. It discovers Tokens/Components/Patterns/Composition entries through MCP
+tools and renders their scenarios in the preview App. Navigation, theme and
+pane/header visibility belong to the tool client. Do not create page files,
+copy its shell into the project or assemble a second catalogue/rendering pipeline.
+
+When MCP is connected, open the running URL from `ads_status`. Otherwise run the
+installed `ads showcase` or the project's `dev:showcase` script. Do not launch a
+second runtime/compiler for the same connected project. A configured project
+preview watcher publishes a shared graph on first demand and after source
+changes. The built-in client refreshes discovery and the active scenario in the
+same App after a successful build. Shared runtime, foundation CSS, fonts and
+selected scenario modules load through MCP
+resources inside the sandboxed App. Never inject project styles/runtime into
+the outer host. Keep the configured framework, compiler and mount/unmount adapter
+consistent; scenario teardown must release owned timers, portals and workers.
+The host shows errors and marks retained output as stale. Other hosts may need an
+explicit preview-tool invocation. Compilation remains project-owned and required
+for TSX/Linaria; it is automatic, not eliminated.
+
+Reusable review layouts belong in public project ADS patterns, while scenario
+files define no CSS, custom classes or widget replicas. Keep real presentation in
+its component/pattern owner. The tooling shell's CSS is outside that project
+contract. Legacy custom showcase pages may be retained during migration; new
+projects require no TokensPage/ComponentsPage/PatternsPage/CompositionPage files.
+
+Colocate `Scenario.tsx` and `fixture.ts` with tokens and each component/pattern; flat owners
+may use `<Owner>.scenario.tsx` and `<Owner>.fixture.ts`. Put larger entries under
+`composition/<Name>/Scenario.tsx` with their own `fixture.ts`. Export a default
+zero-input mountable view and literal metadata, for example
+`export const scenario = { title: "Button states", covers: ["Button"] };`.
+Import the real UI from the public ADS alias. Keep fixture inputs, simulated
+services and initial state/callback adapters beside the scenario. Empty fixtures
+are valid for an entry with no inputs. Extra development helpers use a
+`scenario/` or `fixtures/` subfolder, or `<Owner>.scenario-adapter.ts`, so guards
+recognize their role even beside runtime code. Never require a page, router or store to
+initialize the entry. Several contextual public parts may share one scenario.
+
+IDs derive from ADS-relative filenames: both `components/core/Button/Scenario.tsx`
+and `components/core/Button.scenario.tsx` identify `components/core/Button`.
+Use one form, no duplicate IDs or hand-maintained registry. Renames change IDs.
+The showcase and external hosts mount the same discovered entry. The Vite
+adapter uses `previewEntriesPlugin` and `createPreviewResources` with
+`runScenarioCompiler` to publish the shared graph. Its framework mount adapter
+returns cleanup; the project owns rendering and Linaria extraction. The older
+`scenarioRegistryPlugin` is only for retained legacy browsers. MCP discovers
+metadata without importing executable TSX. Existing apps need an explicitly
+integrated compiler; init alone adds no compiler or extraction setup.
+Use `ads_scenarios` (query/kind/limit) and `ads_show_scenario({id})` to open an exact
+entry. Check its build freshness; HTML delivery is not browser verification.
+If Apps or resource forwarding are unavailable, open that scenario in the real
+showcase, using the tool result's URL. Do not build a preview-only replica.
+
+For a production screen, find and render the application's public screen pattern.
+Its owner supplies structure, controls, layout and presentation. Scenario fixtures
+supply data/state/callbacks. Move shared presentation into a pattern if needed,
+preserving existing behavior and lazy imports, workers, caching and cancellation.
+Do not reassemble an alternative screen or substitute placeholder content.
+Screen reuse remains skill guidance, not a dedicated screen-parity lint.
+
+Resolve `scenario-contract`, `scenario-render` and `scenario-coverage` findings
+with meaningful entries. Every public renderable component and pattern needs an
+addressable scenario, including unused exports; types/constants/utilities do not.
+Only public render references reachable from the default entry count. Tests and
+unused imports/functions do not. Static reachability does not prove successful
+mounting, correct content, every branch/state or visual parity: open each affected
+entry independently and verify real behavior at narrow/wide sizes in both themes.
+The older `showcase-coverage` policy separately checks application references.
+
+Token previews use that same scenario pipeline. Colocate a token scenario and
+fixture under the configured token directory. Use static metadata
+`{ title: "Typography", covers: ["TokenSamples"], tokens: fixture.tokens }` with
+literal const fixture fields; names/sample text are fixture data, values come
+from the real foundation CSS. Reuse a public project review pattern for styled
+samples. The minimal starter's foundation value scenario can have `covers: []`.
+Every declared token needs reachable scenario coverage; adding/removing a token
+requires fixture updates. Fix `token-scenario-reference`, `token-scenario-render`
+and `token-scenario-coverage` findings. Metadata and unused fixture fields do not
+count. Discover exact token IDs with `ads_scenarios({kind:"tokens"})`; mount them
+with `ads_show_scenario({id})` or `ads_show_tokens({category:id})`. With the shared
+resource compiler, omitting category opens the first project token scenario.
+Legacy compilers retain the generic definition inspector. Use `ads_tokens` for
+source definitions and values; inspecting definitions does not prove UI parity.
+The tool keeps the shared naming contract; sample templates and their token
+lists belong to the project.
+
+Scenarios, colocated fixtures and helpers are development-only. Never export them
+from the runtime barrel or import them in production, including through aliases,
+re-exports or dynamic imports. They may not import application stores, routers,
+providers or HTTP clients. Live business data is application-owned; UI uses typed
+inputs or injected services/callbacks. Direct global fetch/XHR/WebSocket/EventSource
+is rejected; custom clients and computed access require review/project guards.
+Use local simulated services in fixtures. Tests may import fixtures; load real
+foundation CSS rather than assigning shared token values in JavaScript. Keep
+full-app integration harnesses and workflow coverage in application test support.
+
+
+
+Register component/project Oxlint plugins and rules in `ds.config.json`. Use
+scoped `oxlint.overrides` for justified file-specific settings; never edit
+`.ds/oxlintrc.json`. These overrides configure Oxlint, not the independent
+architecture checks in `ads check`. Measured renderer properties and documented
+non-state hooks use explicit `boundaries`; shared token writes and primitive
+state overrides cannot be allowlisted. Add generic architectural protections to
+ADS core and keep domain/component-specific rules registered in project setup.
+
+Read [references/verification.md](references/verification.md) for viewport,
+interaction, and build checks. Inspect both the item alone and its real pattern
+or application container. A wide viewport can hide a narrow-sidebar defect.
+
+For each finding, give the triggering value/state, actual container conditions,
+visible failure, owning file/line, likely cause, and proposed fix. Distinguish:
+
+| Severity | Meaning |
+|----------|---------|
+| Broken | Content or an action is inaccessible, controls overlap, or layout cannot be used |
+| Ugly | The UI remains usable but spacing, wrapping, or alignment visibly fails |
+| Fragile | A demonstrated boundary leaves little room for plausible content changes |
+
+Report observed failures separately from untested risks. Include tested cases
+that passed when that helps define the coverage. Screenshots alone do not prove
+keyboard, focus, scrolling, or gesture behavior.
+
+## Fix in the owner
+
+Components own reusable sizing, wrapping, state visuals, and interaction;
+patterns own reusable composition; the app owns data and domain constraints.
+Use typed variants and documented tokens. Do not dress component internals from
+showcase CSS or introduce raw visual constants outside token declarations.
+
+Choose wrapping, truncation, scrolling, or limits from the content's purpose.
+For example, a visually truncated identifier may need a way to retrieve its full
+value. Preserve documented states, accessibility, and source credits.
+
+Keep useful regression fixtures. Add tests for demonstrated behavior defects
+where they give lasting coverage. A component-local Oxlint rule is appropriate
+only when it can statically establish a concrete public-API misuse; document
+accepted/rejected examples and false-positive limits. Layout quality remains a
+rendered check.
+
+Source credits and retained MIT terms: [README.md](README.md) and
+[LICENSE.upstream](LICENSE.upstream).

package/dist/skills/ads-break-ui/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "ADS Break UI"
+  short_description: "Stress-test local ADS components with realistic extremes"
+  default_prompt: "Use $ads-break-ui to stress-test a component through this project’s real design-system API."

package/dist/skills/ads-break-ui/references/catalog.md

@@ -0,0 +1,135 @@
+# Worst-Case Catalog
+
+Realistic values that break UI, grouped by what kind of value the component renders. Use the rows that apply to its actual rendered fields and supported input domain. Each value is something a real user could produce; the note says what it tends to break.
+
+Use `example.com`, `example.org`, or `.test` domains for emails and URLs, so the fixture never points at a real inbox or site.
+
+---
+
+## People and names
+
+| Value | Breaks |
+| --- | --- |
+| `Aleksandra Wiśniewska-Kowalczyk` | Long, hyphenated, diacritics; wraps to two lines, and the hyphen is a line-break point |
+| `Christopher Alexander Montgomery III` | Long with a suffix; naive first + last initials give `CI` |
+| `Konstantin Oberhauser-Wettstein` | Long and compound; overflows single-line rows |
+| `Jo` | Two letters; leaves the name column mostly empty, and naive initials give `J` |
+| `J` | One letter; single-character initials, very short click target if the name is the link |
+| `Ólafur Darri Ólafsson` | Leading accented capital; uppercase/sort logic, initials `ÓÓ` |
+| `Đặng Thị Ngọc Hân` | Stacked Vietnamese diacritics; clipped by tight `line-height` + `overflow: hidden` |
+| `王秀英` | CJK, no spaces; "first + last word" initials logic finds one word, and CJK breaks anywhere |
+| `نور الهدى عبد الرحمن` | RTL; punctuation and icons land on the wrong side without `dir="auto"` |
+| `Seán O'Brien-Ó Súilleabháin` | Apostrophe and accents; escaping, initials, search |
+| `María José de la Cruz y Fernández` | Lowercase particles; initials `Md` or `MF`, sorting by "last name" |
+| `dana` | All lowercase; initials should still be uppercase |
+| `🦊 Fox` | Emoji first; `.charAt(0)` returns half a surrogate pair (`�`) |
+| `👩🏽‍💻 Priya` | ZWJ emoji sequence; `.length` is 7+, slicing breaks it into pieces |
+| `  Sam   Lee ` | Leading, trailing, and repeated spaces; initials from empty words, odd gaps |
+| *(missing)* | No name at all, only an email; the UI must fall back to something |
+
+## Emails, URLs, identifiers
+
+Unbreakable strings: they have no spaces, so the browser has nowhere to wrap them.
+
+| Value | Breaks |
+| --- | --- |
+| `bartholomew.fitzgerald@northwind-industries-holdings.example.com` | The classic. Pushes every sibling off the row without `overflow-wrap: anywhere` |
+| `a@b.co` | Shortest realistic; layout that assumed a long email looks empty |
+| `first.last+billing-notifications@example.com` | Plus-addressing; validation that rejects `+`, display that truncates the meaningful part |
+| `ops@sub.department.region.example.co.uk` | Many subdomains, two-part TLD; "domain" extraction logic |
+| `https://example.com/workspaces/acme/projects/q3-launch/docs/9f8e7d6c5b4a?tab=comments&filter=unresolved` | Long URL; overflow, and end-truncation hides the part that differs |
+| `9f8e7d6c-5b4a-4c3d-8e2f-1a0b9c8d7e6f` | UUID; monospace width, middle-truncation candidate |
+| `Q3 Board Deck — FINAL (revised) v12 [approved by legal].pdf` | File name; end-truncation hides the version and extension, brackets and dashes in paths |
+| `IMG_20250914_183022_HDR_portrait_edited_edited.HEIC` | Camera file name; unbreakable, uppercase extension |
+| `@a` / `@thisisaverylongusernamethatisallowed` | Handle extremes |
+
+## Labels, titles, and copy from data
+
+| Value | Breaks |
+| --- | --- |
+| `Senior Product Design Engineer, Platform Infrastructure` | Long job title; wraps to three lines in a secondary slot |
+| `Invitation expired 12 days ago` | Long status badge; badge wraps or squeezes the name column |
+| `Benachrichtigungseinstellungen` | German compound (30 chars, no spaces); label overflow, unbreakable |
+| `Paramètres de confidentialité et de sécurité` | French expansion of "Privacy & security"; UI copy runs ~30% longer in translation |
+| Twelve tags on one item: `design`, `frontend`, `q3`, `urgent`, `needs-review`, … | Tag rows that wrap into a wall; needs a `+8` overflow |
+| A tag named `customer-feedback-from-enterprise-onboarding` | One tag wider than its container |
+| `Untitled` / empty string / `   ` | Title missing; collapsed heading, zero-height row |
+| `<script>alert(1)</script>` / `&amp;` / `**bold**` | Escaping; must render as literal text |
+| `Line one` + newline + `Line two` | Newline in a single-line field; doubles row height or is silently dropped |
+| A 2,000-character pasted description | Clamps, "show more", and textarea growth |
+
+## Numbers and money
+
+| Value | Breaks |
+| --- | --- |
+| `0` | Zero states: "0 members", empty progress bar, division by zero in percentages |
+| `1` | Plurals: "1 members", "1 days ago" |
+| `1284` | Needs a thousands separator: `1,284` |
+| `1000000` | Width of the count badge; consider compact form `1M` where precision doesn't matter |
+| `12345678.9` as currency | `$12,345,678.90`; overflows totals columns |
+| `-42.5` | Negative sign, red color logic, parentheses in accounting formats |
+| `0.1 + 0.2` | `0.30000000000000004` rendered raw |
+| `142%` / `-3%` | Progress bars and meters past their bounds |
+| `null` / `undefined` / `NaN` | Rendered literally |
+| `1.284` in `de-DE` vs `1,284` in `en-US` | Locale formatting; hardcoded separators are wrong for half the world |
+| A value that changes live (`99` → `100`) | Width jump and jitter without `tabular-nums` |
+
+## Collections
+
+| Value | Breaks |
+| --- | --- |
+| 0 items | The empty state, and whether one exists at all |
+| 1 item | Grids that look broken with one card; "1 of 1" |
+| Exactly page size, and page size + 1 | Off-by-one in "Showing 40 of 40", pagination that shows an empty page 2 |
+| 1,000+ items, unpaginated | Scroll performance, render time, memory; also "Showing 40 of 1,284" copy |
+| One item 10× the size of the others | Masonry and grid rows stretching to the tallest item |
+| Items with identical names | Lists where the name is the only distinguishing field |
+
+## Time
+
+| Value | Breaks |
+| --- | --- |
+| Now | "0 seconds ago" instead of "just now" |
+| 12 days ago, 11 months ago, 3 years ago | Relative-time thresholds; switch to an absolute date after a week or so |
+| A future date | "in 3 days" vs "-3 days ago" |
+| `1970-01-01` | A zero timestamp shown as a real date |
+| `2025-12-31T23:30:00-08:00` | Shows as a different day in UTC and the user's timezone |
+| Very long duration (`1,284 hours`) | Duration formatting that never rolls up to days |
+
+Use `Intl.RelativeTimeFormat` and `Intl.DateTimeFormat`, not hand-built strings.
+
+## Images and media
+
+| Value | Breaks |
+| --- | --- |
+| Avatar URL that 404s | Broken-image icon instead of the initials fallback |
+| No avatar at all | The fallback itself: initials, color, size parity with real avatars |
+| 4000×200 panorama as avatar or cover | Distortion without `object-fit: cover` |
+| 200×4000 tall image | Same, other axis; can also blow out a card's height |
+| Transparent PNG logo, dark logo on dark mode | Invisible on the background |
+| Slow-loading image | Layout shift without fixed dimensions or `aspect-ratio` |
+
+## States
+
+| Value | Breaks |
+| --- | --- |
+| Loading | Skeletons that don't match final layout, spinners that shift content |
+| Error from the API | No error state, or a raw error message (`TypeError: Cannot read properties of undefined`) |
+| Partial data | Some optional fields filled, others not, in the same list; misaligned rows |
+| Every status at once | All enum values in one list (`active`, `invited`, `expired`, `suspended`); badge widths vary |
+| No permission | Disabled actions; does the row still lay out the same? |
+| The current user in the list | "You" labels, actions that shouldn't apply to yourself |
+
+## Environment
+
+Not data, but checked the same way: flip to the worst case, then change these.
+
+| Condition | Breaks |
+| --- | --- |
+| Container at 320px | Every overflow above, at once |
+| Narrow sidebar placement | Components designed full-width, reused in a 280px column |
+| 2560px wide | Lines too long to read, content stranded on one side |
+| Browser zoom 200% / large text setting | Fixed heights that clip growing text |
+| Dark mode | Hardcoded colors, invisible borders and logos |
+| `dir="rtl"` | Icons, chevrons, padding, and the order of trailing actions |
+| Touch device | Hover-only actions (the ••• that appears on hover) are unreachable |

package/dist/skills/ads-break-ui/references/verification.md

@@ -0,0 +1,48 @@
+# Verify stress cases
+
+Use the project's real public API and discovered commands. Do not assume `@ds`,
+a particular Toast/Button, or this tool checkout's prototype exists in another
+project. Read the local component contract before inventing props or states.
+
+## Rendered checks
+
+Select checks that match the item:
+
+- Normal content, realistic long content, an unbreakable string, and absent
+  optional content. Test translations, CJK, or RTL when supported or requested.
+- Empty, single-item, boundary-count, and large collections. Use supported
+  pagination/virtualization rather than accidentally creating a production DoS.
+- Loading, success, failure, disabled, and partial results where exposed by the
+  API. Invalid numbers/dates should exercise the documented boundary, not be
+  passed as valid props when the API excludes them.
+- The actual narrow container, a 320 CSS-pixel viewport, and 200% zoom where
+  practical. At larger zoom, check reflow against the project's accessibility
+  requirements. Also check wide layouts if stretching is relevant.
+- Both supported themes, keyboard focus order and activation, accessible names,
+  touch/scroll interaction, and reduced motion for animated controls.
+
+Use an isolated browser context. Preserve the user's open pages and settings.
+Capture the fixture, viewport/container size, theme, zoom, and actions alongside
+each failure. CSS viewport emulation is useful; it is not evidence of real
+mobile keyboard, browser chrome, or assistive-technology behavior.
+
+For transient UI, use the actual notification/dialog/menu entry point. Check
+long content, repeated additions, dismissal, and retained focus using the local
+contract. Don't duplicate the component's internal markup to simplify a demo.
+
+## Validate fixes
+
+Run the target's lint, typecheck, and appropriate build after implementation
+changes. ADS initialization normally wires its local tooling into the project's
+build; use that existing integration. An ad hoc `npx` check is not a substitute
+for project build integration, and an unpublished package must not be fetched
+as if it were available.
+
+Rerun the failing scenario and a representative normal case. Test neighboring
+states only when the fix could affect them. For a local rule, verify valid and
+invalid usage and its registration; keep rule code out of runtime exports.
+
+For a diagnostic-only request, report findings and reproduction steps without
+silently applying production changes. Stop any temporary server started for the
+check unless the user requested a running preview. Include any checks that
+could not be performed and the practical limits of emulation.

package/dist/skills/ads-designer/LICENSE.upstream

@@ -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/dist/skills/ads-designer/README.md

@@ -0,0 +1,19 @@
+# Credits
+
+The bundled empty scaffold and local ADS workflow belong to this repository.
+Selected craft/mobile guidance adapts [Emil Kowalski's skills](https://github.com/emilkowalski/skills)
+at revision `2d228630ba1446365f614a108cb8252f1feda202`:
+
+| Upstream source | Local reference |
+|-----------------|-----------------|
+| [emil-design-eng](https://github.com/emilkowalski/skills/tree/2d228630ba1446365f614a108cb8252f1feda202/skills/emil-design-eng) | [design-craft.md](references/design-craft.md): state completeness, interaction detail, layout, content, and purposeful motion |
+| [mobile-native](https://github.com/emilkowalski/skills/tree/2d228630ba1446365f614a108cb8252f1feda202/skills/mobile-native) | [mobile.md](references/mobile.md): input capabilities, viewport/safe areas, forms, scrolling, and device verification |
+
+The adaptations preserve project-owned token values and styles, public APIs,
+component/pattern ownership, and application responsibility for document-level
+setup. They do not impose upstream numeric/brand defaults or native app tooling.
+
+[LICENSE.upstream](LICENSE.upstream) retains the complete MIT license and
+Copyright (c) 2026 Emil Kowalski for copied/adapted upstream guidance. Retain it
+on redistribution of that material. It does not declare a license for unrelated
+project source or the bundled scaffold.