@mohanscodex/spectra-code 0.4.9 → 0.5.0

package/skills/winui-app/references/motion-animations-and-polish.md

@@ -0,0 +1,45 @@
+---
+title: Motion, Animations, and Polish
+priority: MEDIUM
+tags: motion, animations, transitions, connected-animation, polish
+sources:
+  - https://learn.microsoft.com/windows/apps/design/motion/
+  - https://github.com/microsoft/WinUI-Gallery
+  - https://github.com/CommunityToolkit/Windows
+---
+
+## What This Reference Is For
+
+Use this file when adding polish to a WinUI app through motion, transitions, and subtle animated state changes.
+
+## Prefer
+
+- Motion that clarifies hierarchy, continuity, and state changes.
+- Theme transitions, connected animations, and built-in platform behaviors before custom animation systems.
+- Short, purposeful animations that support the task.
+
+## Avoid
+
+- Decorative animation that delays interaction.
+- Multiple overlapping animations for the same state change.
+- Animation that hides focus, selection, or accessibility state.
+
+## Guidance
+
+- Use transitions to explain where content came from and where it went.
+- Keep entrance and exit motion subtle.
+- Use connected animation when there is a real source-to-destination relationship.
+- Reach for CommunityToolkit animation helpers only when built-in transitions are not enough.
+
+## Sample and Source Anchors
+
+- WinUI Gallery animation, transition, and implicit animation pages
+- Learn motion guidance
+- CommunityToolkit animations package and samples
+
+## Review Checklist
+
+- Does the motion improve clarity?
+- Is the app still responsive while the animation runs?
+- Can the transition be simplified to a built-in WinUI behavior?
+- Does the motion preserve accessibility and input clarity?

package/skills/winui-app/references/performance-diagnostics-and-responsiveness.md

@@ -0,0 +1,46 @@
+---
+title: Performance, Diagnostics, and Responsiveness
+priority: HIGH
+tags: performance, responsiveness, ui-thread, wpr, wpa, diagnostics
+sources:
+  - https://learn.microsoft.com/windows/apps/performance/winui-perf
+  - https://github.com/microsoft/WinUI-Gallery
+---
+
+## What This Reference Is For
+
+Use this file when the user reports sluggish WinUI behavior, dropped frames, long startup, or laggy scrolling and layout.
+
+## Prefer
+
+- Keeping the UI thread free for layout, rendering, and input.
+- Simpler visual trees and lighter templates.
+- Virtualization-friendly controls and item layouts.
+- Measurement before optimization when the issue is not obvious.
+
+## Avoid
+
+- Doing expensive I/O or CPU work directly on the UI thread.
+- Deeply nested XAML trees without a concrete benefit.
+- Re-templating controls in ways that dramatically increase layout work.
+- Guessing at performance causes without profiling.
+
+## Guidance
+
+- Favor platform controls and layouts that virtualize well for long lists.
+- Defer or background heavy work when it does not need to block interaction.
+- Reduce unnecessary layout invalidation and repeated measure/arrange churn.
+- Use WPR and WPA with the XAML Frame Analysis plugin for frame-level investigations.
+- Treat slow-frame findings as a clue to UI-thread overload, not as a reason to micro-optimize blindly.
+
+## Sample and Source Anchors
+
+- Learn `winui-perf.md`
+- WinUI Gallery pages that demonstrate adaptive UI and complex controls without excessive custom infrastructure
+
+## Review Checklist
+
+- Is heavy work running off the UI thread where possible?
+- Are large collections using an appropriate items control?
+- Is the visual tree no more complex than it needs to be?
+- Has profiling been used before claiming a fix?

package/skills/winui-app/references/sample-source-map.md

@@ -0,0 +1,37 @@
+---
+title: Sample and Source Map
+priority: MEDIUM
+tags: sources, mapping, lookup, gallery, docs, toolkit
+sources:
+  - https://learn.microsoft.com/windows/apps/get-started/samples
+  - https://github.com/microsoft/WinUI-Gallery
+  - https://github.com/microsoft/WindowsAppSDK-Samples
+  - https://github.com/CommunityToolkit/Windows
+---
+
+## What This Reference Is For
+
+Use this file when you know the task but need to identify the best canonical source to inspect first.
+
+| Task | First source | Backup source |
+| --- | --- | --- |
+| Check whether a PC can build WinUI apps | `../SKILL.md` | `foundation-environment-audit-and-remediation.md` |
+| Install missing prerequisites | `../SKILL.md` | `foundation-environment-audit-and-remediation.md` |
+| Start a new packaged or unpackaged app | `../SKILL.md` | `foundation-setup-and-project-selection.md` |
+| Choose packaged vs unpackaged | Learn Windows App SDK deployment docs | WindowsAppSDK-Samples `Samples/Unpackaged` |
+| Build a shell with navigation | WinUI Gallery navigation pages | Learn navigation basics |
+| Design a custom title bar | Learn title bar guidance | WinUI Gallery title bar samples |
+| Add Mica or system backdrops | Learn Mica guidance | WindowsAppSDK-Samples `Samples/Mica` |
+| Design a settings page | WinUI Gallery control pages | CommunityToolkit `SettingsControls` |
+| Pick a control for a list or collection | WinUI Gallery control pages | Learn responsive/layout guidance |
+| Improve accessibility | Learn accessibility docs | WinUI Gallery standard control behavior |
+| Diagnose responsiveness | Learn `winui-perf.md` | WPR/WPA guidance in `testing-debugging-and-review-checklists.md` |
+| Add notifications or activation flows | WindowsAppSDK-Samples | Learn Windows App SDK lifecycle docs |
+| Decide whether to add CommunityToolkit | `community-toolkit-controls-and-helpers.md` | Toolkit component directories |
+
+## Source Preferences
+
+- Learn first for requirements and behavioral guidance.
+- WinUI Gallery first for concrete control usage and shell composition.
+- WindowsAppSDK-Samples first for scenario APIs and platform integration.
+- CommunityToolkit only when the task clearly requires Toolkit-specific functionality.

package/skills/winui-app/references/shell-navigation-and-windowing.md

@@ -0,0 +1,67 @@
+---
+title: Shell, Navigation, and Windowing
+priority: HIGH
+tags: navigationview, titlebar, appwindow, multi-window, shell
+sources:
+  - https://learn.microsoft.com/windows/apps/design/basics/navigation-basics
+  - https://learn.microsoft.com/windows/apps/design/basics/titlebar-design
+  - https://github.com/microsoft/WinUI-Gallery
+  - https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/Windowing
+---
+
+## What This Reference Is For
+
+Use this file for top-level app shells, page navigation models, custom title bars, and multi-window decisions.
+
+## Prefer
+
+- `NavigationView` for standard desktop shells with clear top-level destinations.
+- A small, stable set of primary destinations.
+- Built-in back navigation behavior that matches user expectations.
+- `AppWindow` and Windows App SDK windowing APIs for modern window management.
+
+## Avoid
+
+- Overloading the nav surface with every command and secondary action.
+- Turning the `NavigationView` pane into a branded hero area when the user did not ask for custom shell treatment.
+- Custom title bar layouts that break drag regions or caption button clarity.
+- Multi-window designs unless the workflow clearly benefits from them.
+
+## Navigation Guidance
+
+- Use left navigation when the app has several stable, high-level destinations.
+- Use top navigation when there are few peer destinations and width is available.
+- Use a single-page or document-first layout when navigation is shallow and the user mostly stays in one workflow.
+- Keep naming and iconography stable across pages.
+- Treat `NavigationView` as functional shell chrome first. Keep pane headers, footer content, and decorative branding minimal unless the product requirements clearly call for them.
+- Prefer the platform's normal pane structure before adding custom logo blocks, taglines, or non-navigation content that changes the shell's native feel.
+- For narrow or phone-like widths, stop reserving permanent pane width for desktop navigation. Prefer a minimal or overlay navigation mode, show the pane toggle when needed, close the pane by default after navigation, and give content the width back.
+- When a shell enters a phone-width mode, reduce content padding and decorative chrome so the page reads as one primary column instead of a desktop shell with a squeezed content strip.
+
+## Title Bar Guidance
+
+- Treat the title bar as functional chrome first, branding surface second.
+- Keep empty non-interactive areas draggable.
+- Blend title bar visuals with the rest of the app when possible.
+- Respect light, dark, and high-contrast states.
+
+## Windowing Guidance
+
+- Start with one main window.
+- Add secondary windows only for workflows such as document detachment, inspection panes, or tool windows.
+- Use Windows App SDK samples for resizing, placement, and window-specific behaviors instead of inventing custom platform abstractions.
+
+## Sample and Source Anchors
+
+- WinUI Gallery `NavigationView`, `TitleBar`, `AppWindow`, and windowing sample pages
+- WindowsAppSDK-Samples `Samples/Windowing`
+- Learn navigation and title bar guidance
+
+## Review Checklist
+
+- Is the navigation model simple and intentional?
+- Does the shell still look and behave like a normal WinUI `NavigationView` unless there is an explicit reason to diverge?
+- Does the title bar still behave like a Windows title bar?
+- Are back, search, and pane behaviors consistent?
+- Is multi-window use justified by the workflow?
+- Does the shell intentionally switch behavior at narrow or phone widths instead of leaving a full desktop pane open?

package/skills/winui-app/references/styling-theming-materials-and-icons.md

@@ -0,0 +1,71 @@
+---
+title: Styling, Theming, Materials, and Icons
+priority: HIGH
+tags: styling, theme-resources, mica, acrylic, typography, icons
+sources:
+  - https://learn.microsoft.com/windows/apps/design/style/mica
+  - https://learn.microsoft.com/windows/apps/design/style/acrylic
+  - https://learn.microsoft.com/windows/apps/design/signature-experiences/typography
+  - https://learn.microsoft.com/windows/apps/design/signature-experiences/iconography
+  - https://github.com/microsoft/WinUI-Gallery
+  - https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/Mica
+---
+
+## What This Reference Is For
+
+Use this file for Fluent styling choices, theme resources, Mica or Acrylic usage, custom title bar visuals, typography, and iconography.
+
+## Prefer
+
+- Theme resources and system brushes over hard-coded colors.
+- Standard WinUI surface resources and default control chrome before custom panel systems.
+- Mica on long-lived surfaces such as the main window background or title bar region.
+- Acrylic on transient or light-dismiss surfaces.
+- Segoe UI Variable or platform-default typography choices.
+- Fluent iconography that matches the platform language.
+- When metadata needs a visual container, prefer small rounded rectangles or subtle badges over bright oval pills.
+
+## Avoid
+
+- Hard-coded light-theme colors that break dark or high-contrast themes.
+- Wrapping every region in a custom `Border` with a bespoke corner radius, stroke, and fill when standard WinUI surfaces would do the job.
+- Adding an outer section `Border` around content that is already visually grouped by card controls, spacing, or headers; this often creates a redundant "card around cards" effect.
+- Using Acrylic where Mica or a simple theme-aware surface would be cheaper and clearer.
+- Mixing unrelated icon styles.
+- Filling lists or cards with rows of decorative oval chips for routine metadata. Use tag treatments sparingly, and default to rounded rectangles when they are justified.
+
+## Theming Guidance
+
+- Support light, dark, and high-contrast by default.
+- Centralize brushes, typography, and corner/spacing decisions in shared resource dictionaries.
+- Let built-in controls keep their platform behavior unless there is a strong design reason to customize them.
+- When a grouped surface is needed, prefer system resources such as `CardBackgroundFillColorDefaultBrush`, `CardStrokeColorDefaultBrush`, and `LayerFillColorDefaultBrush` instead of inventing a parallel surface language.
+- If child content already uses card-like surfaces, prefer removing the outer section border and relying on layout spacing and typography for grouping unless the section needs its own distinct background, inset, or stroke.
+
+## Materials Guidance
+
+- Use Mica for long-lived base layers.
+- Use Acrylic for transient surfaces such as flyouts and menus.
+- Verify fallback behavior on older Windows versions or unsupported scenarios.
+
+## Icon and Typography Guidance
+
+- Use standard Windows iconography and keep visual weight consistent.
+- Use typography to create hierarchy instead of adding extra borders or decoration.
+- Keep title bar text and document titles aligned with Windows guidance.
+
+## Sample and Source Anchors
+
+- Learn material, typography, and iconography guidance
+- WinUI Gallery system backdrop and styling pages
+- WindowsAppSDK-Samples `Samples/Mica`
+
+## Review Checklist
+
+- Are colors and brushes theme-aware?
+- Does the app look correct in light, dark, and high contrast?
+- Is the selected material appropriate for the surface lifetime?
+- Are icon and typography choices consistent with Fluent design?
+- Are standard WinUI surfaces doing most of the visual work, with custom borders limited to clearly justified cases?
+- Are there any redundant outer borders that could be removed without losing hierarchy or usability?
+- Are tag or chip treatments sparse, visually quiet, and not rendered as default oval pills unless the product explicitly calls for that style?

package/skills/winui-app/references/testing-debugging-and-review-checklists.md

@@ -0,0 +1,77 @@
+---
+title: Testing, Debugging, and Review Checklists
+priority: HIGH
+tags: testing, debugging, review, hot-reload, live-visual-tree, checklists
+sources:
+  - https://learn.microsoft.com/windows/apps/get-started/start-here
+  - https://learn.microsoft.com/windows/apps/get-started/developer-mode-features-and-debugging
+  - https://learn.microsoft.com/windows/apps/performance/winui-perf
+---
+
+## What This Reference Is For
+
+Use this file for final review passes, debugging sessions, and "what should I verify before I call this done?" prompts.
+
+## Required Verification Loop
+
+- Build after each meaningful edit, not only at the end.
+- Run the app after changes when the user asked for it or when startup-sensitive files changed.
+- Verify actual launch instead of assuming success from a spawned process.
+- If the app fails before showing a window, debug the startup path before continuing feature work.
+
+## Design Review Checklist
+
+- Shell and navigation are simple and predictable.
+- `NavigationView` still reads like standard WinUI shell chrome unless the product explicitly calls for branded pane content or custom shell composition.
+- Layout stays usable when the window is narrow.
+- Layout has been checked at more than one breakpoint, including a genuinely phone-like width when the app can be resized that far.
+- Collection pages with mixed scroll regions have been checked at runtime so shelves still render in the intended direction and do not collapse into a single vertical column.
+- Theme, contrast, hierarchy, and interactive state visibility hold up in both light and dark mode, and typography and iconography still feel native to Windows.
+- Command placement and hierarchy are clear.
+- Default WinUI surfaces and control templates carry most of the layout instead of a custom border/card system.
+- Search and filter workflows avoid redundant controls when live local filtering would be clearer.
+- At narrow and phone widths, nonessential controls are simplified, hidden, or moved behind shell affordances instead of merely compressed.
+
+## Code Review Checklist
+
+- App structure is coherent and scalable.
+- Resource dictionaries and styles are centralized where they should be.
+- Platform controls are preferred over unnecessary custom control work.
+- New dependencies are justified.
+- The packaging model matches the startup, storage, and launch code.
+- The app builds cleanly from the workflow the user will actually use.
+
+## Accessibility Checklist
+
+- Keyboard-only flow works end to end.
+- Focus states are visible and sensible.
+- Automation properties are present where needed.
+- High contrast and text scaling do not break the UI.
+
+## Performance Checklist
+
+- No obvious UI-thread blocking work in interactive paths.
+- Large collections use an appropriate control and layout.
+- Scroll ownership is intentional for collection-heavy pages; nested `GridView` plus outer `ScrollViewer` combinations have been justified or replaced.
+- Expensive styling or template choices are justified.
+- Profiling data exists for non-obvious performance claims.
+
+## Debugging Tools
+
+- Use Hot Reload for fast visual iteration.
+- Use Live Visual Tree and Live Property Explorer for layout and property debugging.
+- Use WPR and WPA when diagnosing frame or responsiveness issues.
+- Reproduce resize, theme, and input-mode changes before concluding the issue is fixed.
+- When resize behavior is part of the task, verify wide, medium, and phone-width states against the running app rather than trusting the XAML structure alone.
+- When a collection page looks wrong, inspect the live tree for nested `ScrollViewer` ownership before rewriting the item template; the bug may be layout ownership rather than card markup.
+- Use startup exception details, debugger output, or Event Viewer when the process dies before any window appears.
+
+## Exit Criteria
+
+- The build succeeds from the intended local workflow.
+- The feature works on the intended machine configuration.
+- The app launches and shows the expected shell or window.
+- The app remains usable in light, dark, and high contrast.
+- Primary flows are keyboard-accessible.
+- Resize behavior, startup, and interactive responsiveness have been checked.
+- If the window can become phone-width, the shell and content have been verified there too.

package/skills/winui-app/references/windows-app-sdk-lifecycle-notifications-and-deployment.md

@@ -0,0 +1,52 @@
+---
+title: Windows App SDK Lifecycle, Notifications, and Deployment
+priority: HIGH
+tags: windows-app-sdk, lifecycle, activation, notifications, deployment, packaged, unpackaged
+sources:
+  - https://learn.microsoft.com/windows/apps/windows-app-sdk/
+  - https://learn.microsoft.com/windows/apps/windows-app-sdk/deploy-packaged-apps
+  - https://learn.microsoft.com/windows/apps/windows-app-sdk/deploy-unpackaged-apps
+  - https://github.com/microsoft/WindowsAppSDK-Samples
+---
+
+## What This Reference Is For
+
+Use this file when the user needs lifecycle, activation, notification, packaged vs unpackaged, or runtime initialization guidance that goes beyond plain XAML UI work.
+
+## Prefer
+
+- Learning the scenario from the matching WindowsAppSDK sample before designing an abstraction.
+- Packaged deployment when it fits the product constraints.
+- Explicit unpackaged guidance when the user has an installer, external-location requirement, or expects repeatable direct executable launches during development.
+
+## Avoid
+
+- Mixing packaged and unpackaged guidance in one answer without stating which path applies.
+- Treating deployment requirements as optional details.
+- Re-implementing lifecycle behavior already covered by Windows App SDK APIs.
+- Using package-identity-dependent APIs in unpackaged startup code without an explicit guard or replacement path.
+
+## Guidance
+
+- Use AppLifecycle guidance and samples for activation, instancing, restart, and state notifications.
+- Use notifications samples for push or app notifications rather than inventing custom delivery logic.
+- For packaged apps, account for framework-dependent deployment and runtime package requirements.
+- For unpackaged apps, account for bootstrapper and runtime initialization requirements.
+- For unpackaged apps, treat package identity as absent unless the app deliberately establishes it through the chosen deployment model.
+- Keep storage, settings, and startup services aligned with the deployment model. If a service assumes packaged storage or activation, redesign it before local unpackaged verification.
+- Explain the deployment model before giving build or publish steps.
+
+## Sample and Source Anchors
+
+- WindowsAppSDK-Samples `Samples/AppLifecycle`
+- WindowsAppSDK-Samples `Samples/Notifications`
+- WindowsAppSDK-Samples `Samples/Unpackaged`
+- WindowsAppSDK-Samples `Samples/CustomControls`
+- Learn packaged and unpackaged deployment guides
+
+## Review Checklist
+
+- Is the app’s deployment model explicit?
+- Are lifecycle and activation behaviors using platform APIs rather than ad hoc workarounds?
+- Are notification requirements matched to the correct sample and runtime guidance?
+- Does the recommendation match packaged or unpackaged constraints?

package/skills/yeet/LICENSE.txt

@@ -0,0 +1,201 @@
+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/yeet/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: "yeet"
+description: "Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`)."
+---
+
+## Prerequisites
+
+- Require GitHub CLI `gh`. Check `gh --version`. If missing, ask the user to install `gh` and stop.
+- Require authenticated `gh` session. Run `gh auth status`. If not authenticated, ask the user to run `gh auth login` (and re-run `gh auth status`) before continuing.
+
+## Naming conventions
+
+- Branch: `codex/{description}` when starting from main/master/default.
+- Commit: `{description}` (terse).
+- PR title: `[codex] {description}` summarizing the full diff.
+
+## Workflow
+
+- If on main/master/default, create a branch: `git checkout -b "codex/{description}"`
+- Otherwise stay on the current branch.
+- Confirm status, then stage everything: `git status -sb` then `git add -A`.
+- Commit tersely with the description: `git commit -m "{description}"`
+- Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
+- Push with tracking: `git push -u origin $(git branch --show-current)`
+- If git push fails due to workflow auth errors, pull from master and retry the push.
+- Open a PR and edit title/body to reflect the description and the deltas: `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)`
+- Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \\n-escaped markdown.
+- PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

package/skills/yeet/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Yeet"
+  short_description: "Stage, commit, and open PR"
+  icon_small: "./assets/yeet-small.svg"
+  icon_large: "./assets/yeet.png"
+  default_prompt: "Prepare this branch for review: stage intended changes, write a focused commit, and open a PR."

package/skills/yeet/assets/yeet-small.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" fill="currentColor" viewBox="0 0 14 14">
+  <path d="M6.873 11.887a1.06 1.06 0 0 1-.813.38.971.971 0 0 1-.8-.34c-.2-.231-.242-.551-.127-.96l.58-2.107h-2.78c-.31 0-.553-.087-.726-.26a.896.896 0 0 1-.254-.64c0-.253.085-.482.254-.687l4.9-5.82c.209-.244.477-.37.806-.38.334-.008.6.105.8.34.205.236.25.556.134.96l-.6 2.147h2.786c.307 0 .547.089.72.267a.859.859 0 0 1 .267.64c0 .253-.087.48-.26.68l-4.887 5.78Zm4.054-6.22a.178.178 0 0 0 .04-.107.091.091 0 0 0-.034-.087.154.154 0 0 0-.113-.04H7.733a.544.544 0 0 1-.32-.093.467.467 0 0 1-.173-.253.663.663 0 0 1 .007-.36l.64-2.314c.017-.066.01-.117-.02-.153a.136.136 0 0 0-.127-.053.18.18 0 0 0-.127.073l-4.58 5.433a.225.225 0 0 0-.046.107c0 .036.013.065.04.087.026.022.066.033.12.033h3.046c.143 0 .258.031.347.093a.447.447 0 0 1 .187.26.664.664 0 0 1-.007.36l-.627 2.274c-.017.066-.01.12.02.16a.135.135 0 0 0 .12.046.194.194 0 0 0 .134-.066l4.56-5.4Z"/>
+</svg>