opencode-skills-collection 1.0.210 → 2.0.0-beta.2

package/bundled-skills/ux-copy/SKILL.md

@@ -1,79 +0,0 @@
----
-name: ux-copy
-description: "Generate UX microcopy in StyleSeed's Toss-inspired voice for buttons, empty states, errors, toasts, confirmations, and form guidance."
-category: design
-risk: safe
-source: community
-source_repo: bitjaru/styleseed
-source_type: community
-date_added: "2026-04-08"
-author: bitjaru
-tags: [ux, copywriting, microcopy, frontend, styleseed]
-tools: [claude, cursor, codex, gemini]
----
-
-# UX Copy
-
-## Overview
-
-Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill generates concise product copy for common UI states. It follows the Toss-inspired tone: casual but polite, direct, active, and specific enough to help the user recover or proceed.
-
-## When to Use
-
-- Use when you need button labels, helper text, toasts, empty states, or error messages
-- Use when a feature has functional UI but weak or robotic wording
-- Use when you want consistent product voice across a flow
-- Use when confirmation dialogs or state feedback need better phrasing
-
-## Tone Rules
-
-- casual but polite
-- active voice over passive voice
-- positive framing where it stays honest
-- plain language instead of internal jargon
-- concise wording where every word earns its place
-
-## Common Patterns
-
-### Buttons
-
-Use a short action verb plus object when needed.
-
-### Empty States
-
-Start with a friendly observation, then suggest the next action.
-
-### Errors
-
-Explain what happened in user-facing language and what to do next. Do not surface raw internal error strings.
-
-### Toasts
-
-Confirm the result quickly. Add an undo action for reversible destructive behavior.
-
-### Forms
-
-Use clear labels, useful placeholders, specific helper text, and corrective error messages.
-
-### Confirmation Dialogs
-
-State the action in plain language and explain the consequence if the decision is risky or irreversible.
-
-## Output
-
-Return:
-1. The requested microcopy grouped by UI surface
-2. Notes on tone or localization considerations if relevant
-3. Any places where the UX likely needs a structural fix in addition to better copy
-
-## Best Practices
-
-- Make the next action obvious
-- Avoid generic labels like "Submit" or "OK" when the action can be named precisely
-- Blame the system, not the user, when something fails
-- Keep error and empty states useful even without visual context
-
-## Additional Resources
-
-- [StyleSeed repository](https://github.com/bitjaru/styleseed)
-- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-copy/SKILL.md)

package/bundled-skills/ux-feedback/SKILL.md

@@ -1,64 +0,0 @@
----
-name: ux-feedback
-description: "Add loading, empty, error, and success feedback states to StyleSeed components and pages with practical mobile-first rules."
-category: design
-risk: safe
-source: community
-source_repo: bitjaru/styleseed
-source_type: community
-date_added: "2026-04-08"
-author: bitjaru
-tags: [ux, states, loading, error-handling, styleseed]
-tools: [claude, cursor, codex, gemini]
----
-
-# UX Feedback
-
-## Overview
-
-Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill ensures data-dependent UI does not stop at the happy path. It adds the four core feedback states every serious product needs: loading, empty, error, and success.
-
-## When to Use
-
-- Use when a component or page fetches, mutates, or depends on async data
-- Use when a flow currently renders only the success path
-- Use when a card, list, or page needs better state communication
-- Use when the product needs clear recovery and confirmation behavior
-
-## The Four Required States
-
-### Loading
-
-Use skeletons that match the final layout. Avoid spinners inside cards unless the pattern genuinely requires them. Delay skeletons slightly to avoid flashes on fast responses.
-
-### Empty
-
-Provide a friendly explanation and a next action. Zero values should still render meaningfully instead of disappearing.
-
-### Error
-
-Use plain-language failure messages and always offer recovery where possible. Localize failures to the affected card or section if the rest of the page can still work.
-
-### Success
-
-Use toasts or equivalent lightweight confirmation for completed actions. Add undo for reversible destructive changes.
-
-## Output
-
-Return:
-1. The data-dependent areas identified
-2. The loading, empty, error, and success states added for each one
-3. Any reusable empty-state or toast patterns created
-4. Follow-up work needed for analytics, retries, or accessibility
-
-## Best Practices
-
-- Match loading placeholders to the real layout
-- Keep partial failure isolated whenever possible
-- Make recovery obvious, not hidden in logs or developer tools
-- Use success feedback sparingly but clearly
-
-## Additional Resources
-
-- [StyleSeed repository](https://github.com/bitjaru/styleseed)
-- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-feedback/SKILL.md)

package/bundled-skills/ux-flow/SKILL.md

@@ -1,68 +0,0 @@
----
-name: ux-flow
-description: "Design user flows and screen structure using StyleSeed UX patterns such as progressive disclosure, hub-and-spoke navigation, and information pyramids."
-category: design
-risk: safe
-source: community
-source_repo: bitjaru/styleseed
-source_type: community
-date_added: "2026-04-08"
-author: bitjaru
-tags: [ux, flows, navigation, product-design, styleseed]
-tools: [claude, cursor, codex, gemini]
----
-
-# UX Flow
-
-## Overview
-
-Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill designs flows before screens. It uses proven UX patterns to define entry points, exits, screen inventory, and navigation structure so the implementation has a coherent user journey instead of a pile of disconnected pages.
-
-## When to Use
-
-- Use when planning onboarding, checkout, account management, dashboards, or drill-down flows
-- Use when a new feature spans multiple screens or modal states
-- Use when users need a clear path through a task instead of a single isolated page
-- Use when the UI needs navigation logic before components are built
-
-## How It Works
-
-### Information Architecture Principles
-
-- progressive disclosure: reveal complexity only when needed
-- Miller's Law: chunk content into manageable groups
-- Hick's Law: minimize decision overload on each screen
-
-### Common Navigation Models
-
-- hub and spoke for dashboards and detail views
-- linear flow for onboarding, forms, and checkout
-- tab navigation for 3 to 5 top-level areas
-
-### Flow Rules
-
-- every flow has a clear entry point
-- every flow has a clear exit or success condition
-- key features should usually be reachable within three taps from home
-- non-root screens need back navigation
-- loading, empty, and error states need explicit recovery paths
-
-## Output
-
-Provide:
-1. An ASCII flow diagram
-2. A screen inventory with each screen's purpose
-3. Edge cases for loading, empty, and error states
-4. Recommended page scaffolds and reusable patterns to implement next
-
-## Best Practices
-
-- Optimize for clarity before density
-- Let one screen answer one primary question
-- Keep escape hatches visible for risky or destructive steps
-- Define state transitions before drawing detailed layouts
-
-## Additional Resources
-
-- [StyleSeed repository](https://github.com/bitjaru/styleseed)
-- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-flow/SKILL.md)