agents-templated 2.2.9 → 2.2.11

package/templates/agents/commands/risk-review.md

@@ -0,0 +1,33 @@
+# /risk-review
+
+## A. Intent
+Identify release risks that may pass CI but fail in production.
+
+## B. When to Use
+Use before merge or release candidate approval.
+
+## C. Required Inputs
+- Proposed changes
+- Test and validation status
+- Deployment context
+
+## D. Deterministic Execution Flow
+1. Inspect behavior deltas.
+2. Rank risks by impact and likelihood.
+3. Validate mitigation or rollback paths.
+4. Identify missing tests.
+5. Emit ship recommendation.
+
+## E. Structured Output Template
+- `risk_findings[]`
+- `severity_summary`
+- `mitigations[]`
+- `rollback_readiness`
+- `release_recommendation`
+
+## F. Stop Conditions
+- High-severity risk has no mitigation.
+- Rollback path is undefined.
+
+## G. Safety Constraints
+- Block release for unresolved high-severity findings.

package/templates/agents/commands/scope-shape.md

@@ -0,0 +1,33 @@
+# /scope-shape
+
+## A. Intent
+Constrain scope to the smallest high-leverage release that still proves value.
+
+## B. When to Use
+Use after problem framing and before architecture planning.
+
+## C. Required Inputs
+- Problem frame
+- Candidate feature list
+- Delivery constraints
+
+## D. Deterministic Execution Flow
+1. Rank features by impact and effort.
+2. Define must-have vs defer list.
+3. Freeze first-release boundaries.
+4. Add explicit out-of-scope items.
+5. Emit scope decision rationale.
+
+## E. Structured Output Template
+- `scope_in[]`
+- `scope_out[]`
+- `tradeoffs[]`
+- `release_goal`
+- `defer_queue[]`
+
+## F. Stop Conditions
+- Scope still exceeds constraints.
+- No out-of-scope list produced.
+
+## G. Safety Constraints
+- Prefer one reversible release over broad irreversible scope.

package/templates/agents/commands/ux-bar.md

@@ -0,0 +1,33 @@
+# /ux-bar
+
+## A. Intent
+Set a minimum UX quality bar with clear criteria before UI implementation.
+
+## B. When to Use
+Use when a feature has user-facing interaction or visual design impact.
+
+## C. Required Inputs
+- Target user flow
+- Existing design language
+- Accessibility requirements
+
+## D. Deterministic Execution Flow
+1. Evaluate key interaction states.
+2. Check visual hierarchy and clarity.
+3. Validate accessibility coverage.
+4. Identify UX risks and gaps.
+5. Emit UX quality checklist.
+
+## E. Structured Output Template
+- `ux_scorecard[]`
+- `interaction_states[]`
+- `accessibility_checks[]`
+- `ux_gaps[]`
+- `improvements[]`
+
+## F. Stop Conditions
+- Critical flow has undefined state handling.
+- Accessibility constraints are missing.
+
+## G. Safety Constraints
+- Preserve existing design system patterns unless an explicit redesign is approved.

package/templates/agents/skills/README.md

@@ -67,6 +67,10 @@ To create a new skill for your specific domain:
 │   └── SKILL.md              # Risk-based hardening and obfuscation guidance
 ├── ui-ux-pro-max/
 │   └── SKILL.md              # Premium UI/UX implementation patterns
+├── emilkowalski-skill/
+│   └── SKILL.md              # Frontend polish and animation quality checks
+├── raphaelsalaja-userinterface-wiki/
+│   └── SKILL.md              # UI hierarchy and interface best-practice playbook
 ├── my-custom-skill/
 │   └── SKILL.md              # Your custom skill
 └── README.md                 # This file
@@ -101,6 +105,8 @@ Consider creating skills for:
 - `error-patterns`: Use when errors repeat to apply known fixes from lessons-learned and automatically record new resolutions.
 - `app-hardening`: Use for high-risk/distributed runtimes to enforce hardening profile, obfuscation decisions, and release evidence.
 - `shadcn-ui`: Use for shadcn/ui installation, component composition, form patterns, and theme customization.
+- `emilkowalski-skill`: Use for frontend animation, micro-interaction quality, and visual polish passes.
+- `raphaelsalaja-userinterface-wiki`: Use for interface hierarchy, readability, and UX consistency audits.
 
 ## Using Skills in Your Project
 

package/templates/agents/skills/emilkowalski-skill/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: emilkowalski-skill
+description: Frontend interaction and motion quality checks for polished, minimal UI.
+---
+
+# Emil Kowalski Frontend Polish
+
+Use this skill when refining frontend motion, interaction quality, and visual clarity.
+
+## Trigger Conditions
+
+- User asks to improve UI quality, animations, or perceived smoothness.
+- User wants cleaner interactions without heavy redesign.
+- Interface feels functional but not polished.
+
+## Workflow
+
+1. Baseline the current interaction quality.
+2. Remove accidental motion (janky or decorative-only animation).
+3. Define motion hierarchy: page, section, element, micro-interaction.
+4. Tune timing and easing with consistency.
+5. Validate accessibility: reduced-motion support and focus visibility.
+6. Verify mobile and desktop interaction parity.
+
+## Frontend Quality Checklist
+
+- Animation duration is intentional and consistent.
+- Entry and exit transitions communicate state changes.
+- Hover/focus/active states are visually distinct.
+- Touch targets remain accessible on mobile.
+- Layout and typography remain readable during motion.
+
+## Output Contract
+
+- Interaction problems found
+- Priority fixes (high/medium/low)
+- Motion system decisions (duration, easing, delay)
+- Accessibility checks performed
+- Before/after verification notes
+
+## Guardrails
+
+- Do not add animation where no UX value exists.
+- Prefer CSS/transform-based transitions over layout-thrashing properties.
+- Always provide a reduced-motion fallback.
+- Keep performance budget visible (FPS, input latency, layout shifts).
+
+## Upstream Reference
+
+- Original package command:
+  - npx skills add emilkowalski/skill

package/templates/agents/skills/raphaelsalaja-userinterface-wiki/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: raphaelsalaja-userinterface-wiki
+description: UI and UX best-practice playbook for stronger information architecture, readability, and usability.
+---
+
+# User Interface Wiki Playbook
+
+Use this skill when improving UI clarity, hierarchy, and interaction ergonomics.
+
+## Trigger Conditions
+
+- User requests a frontend cleanup or UX review.
+- Interface has weak visual hierarchy or navigation confusion.
+- Product needs consistent UI patterns across pages.
+
+## Workflow
+
+1. Audit hierarchy: headings, spacing, grouping, and contrast.
+2. Audit navigation and task flow for top user goals.
+3. Standardize component patterns (cards, forms, tables, dialogs).
+4. Tighten copy and labels for faster comprehension.
+5. Validate responsive behavior at mobile, tablet, and desktop widths.
+6. Validate accessibility semantics and keyboard flow.
+
+## Interface Quality Checklist
+
+- Primary action is obvious in each view.
+- Navigation labels are unambiguous.
+- Form errors are clear, contextual, and actionable.
+- Empty/loading/error states are explicit.
+- Density and spacing are consistent across sections.
+
+## Output Contract
+
+- UX issues grouped by severity
+- IA and layout improvements
+- Component consistency decisions
+- Accessibility and responsiveness findings
+- Validation steps and acceptance criteria
+
+## Guardrails
+
+- Avoid visual changes that break existing design-system tokens.
+- Keep interaction patterns predictable and learnable.
+- Optimize for readability before decoration.
+- Confirm improvements with at least one critical user journey.
+
+## Upstream Reference
+
+- Original package command:
+  - npx skills add raphaelsalaja/userinterface-wiki