Skill UI

This command merges the results of the highest-ranked agent from a specified or latest session into the base branch. It automates the finalization of a development cycle by ensuring a clean and traceable history. Functionality includes merging the winner's branch, archiving all losing agents' commits using Git tags, and cleaning up temporary worktrees.

This skill generates user-friendly, public-facing release notes (changelogs) for App Stores. It analyzes the raw Git history since the last tag, intelligently filtering out internal commits (like refactors, CI updates, or build scripts) and grouping visible changes into concise, benefit-focused bullet points suitable for a "What's New" section.

A comprehensive guide to professional Git version control. It covers best practices for branching strategies (GitHub Flow, GitFlow, Trunk-Based), writing standardized commit messages using Conventional Commits, managing merges vs. rebases, and defining effective Pull Request workflows. Ideal for any development team looking to improve code collaboration and maintain a clean, traceable history.

This skill acts as a Consumer Psychologist, building deep psychographic profiles by analyzing desires, fears, identity commitments, and underlying worldview. It moves beyond basic demographics to uncover the emotional drivers and core needs that shape consumer behavior. Ideal for pre-positioning, developing persuasive copy, and designing effective funnels.

This skill specializes in crafting multi-touch communication sequences (such as email nurture, onboarding flows, or sales funnels) based on behavioral psychology principles. It leverages key principles—including the curiosity gap, reciprocity, and gradual commitment—to guide users toward a desired outcome. It ensures each touchpoint builds upon the last, respecting the user's autonomy while creating a natural, progressive emotional arc for ethical and effective persuasion.

This skill applies principles of behavioral psychology and choice architecture to redesign user experience (UX) flows. It is used when a product's conversion friction is rooted in interaction design, not just copy. By auditing cognitive load, defining optimal default paths, and inserting strategic commitment points, it guides users toward desired actions ethically, maximizing commitment while preserving autonomy. Ideal for improving onboarding, checkout funnels, and complex decision-making sequences.

Master Git best practices for code management, including trunk-based development, atomic commits, and descriptive messages. Organize parallel work streams, manage branches effectively, and prepare for releases with semantic versioning. Essential for maintaining clean, reviewable, and reversible code history in modern development environments.

This skill refines vague raw ideas into actionable concepts using structured divergent and convergent thinking. It helps stress-test assumptions, expand options, and define MVP scope before committing to a plan. Ideal for early-stage product development where clarity is needed.

This comprehensive workflow automatically retrieves and synthesizes your day's schedule (meetings and events) and uncompleted to-do tasks. It generates a structured 'Standup Report' or daily briefing, featuring conflict detection, time zone conversion, and a clear overview of all commitments and pending items. Ideal for morning standups or checking daily readiness.

This skill simulates a high-level CTO (P10) perspective, focusing on macro-level corporate planning. It assists in defining overarching strategic directions, designing complex organizational topologies, and managing cross-team architectural decisions. Use this when initiating strategic planning, forming an architecture committee, or resolving enterprise-wide technical conflicts.

Write terse, intent-only Conventional Commits messages. Use for generating commit messages from diffs or summaries, with optional scope, imperative mood, and concise body only when needed.

This workflow guides developers through generating standardized, descriptive commit messages using the Conventional Commits specification. It provides a structured XML template (including type, scope, description, body, and footer) and integrates directly into the Git workflow, ensuring project history is clean, traceable, and machine-readable. Ideal for maintaining large, collaborative codebases.