Skill UI

This guide provides an expert framework for directory submissions, transforming them from simple listings into a foundational marketing layer. Learn how to strategically submit your SaaS or AI product to major directories (like Product Hunt, G2, and AI registries) to build high-authority backlinks, boost domain rating, and capture in-market buyer attention. It emphasizes building optimized destination pages (alternatives, use-cases) *before* submission to maximize lead conversion.

This comprehensive guide outlines expert strategies for creating high-authority competitor comparison and alternative pages. It details four proven formats—including 'Alternative to X,' 'You vs Competitor,' and 'Competitor A vs Competitor B'—to capture high-intent search traffic. By emphasizing honesty, deep research, and modular content architecture, these pages boost SEO ranking, build user trust, and drive qualified leads for sales enablement.

This skill simulates a rigorous review by a Chief Financial Officer (CFO) to stress-test any major plan that involves spending or fundraising. It forces consideration of critical financial metrics such as burn rate, unit economics, dilution path, and capital allocation alternatives. Use this when evaluating new expenditures, hiring waves, or funding decisions to ensure financial viability and sustainable growth.

This skill helps users discover alternatives, equivalents, or related tools/models/datasets for a specified Japanese NLP resource (GitHub repo, Hugging Face model, or tool). It first checks a bundled dataset and then expands the search via web research across GitHub and Hugging Face, providing a comprehensive list of related resources.

Unship is a dedicated local workflow for front-end developers to compare multiple AI-generated UI alternatives (such as layouts, copy, or flows) directly within a running application environment. Instead of committing to one generated version, it adds temporary source-level variants, allowing for visual comparison. After the user selects the final version, the skill automatically cleans up all unused temporary code and attributes, ensuring a clean, production-ready codebase. Note: This tool is for local iteration only, not for production A/B testing or analytics.

This skill generates a formal Architecture Decision Record (ADR) following industry-standard formats. It guides users through documenting the full rationale behind significant technical choices, ensuring that the context, alternatives considered, chosen option, and resulting trade-offs are all captured. Ideal for maintaining architectural integrity and knowledge transfer within engineering teams.

A comprehensive skill for generating a structured Request for Comments (RFC) document. Use this to formally propose technical decisions, architectural changes, or significant system implementations. The output ensures all critical aspects are covered, including problem statements, proposed solutions, rejected alternatives, success metrics, and migration plans, facilitating rigorous technical review and decision-making.

This skill guides the creation of high-converting, honest comparison and alternative pages for developer tools. It teaches how to structure content that ranks for competitive SEO terms (e.g., "[Competitor] alternatives," "[Product] vs [Competitor]"), capturing high-intent traffic by addressing user pain points and providing clear technical differentiation.

This foundational skill guides the establishment and maintenance of a comprehensive developer audience context. It helps map out detailed developer personas, identify core pain points, analyze current alternatives, and determine key technical differentiators. By structuring this context across 10 critical sections, it ensures all subsequent developer marketing materials are highly targeted and speak the exact language of the target user.

This skill helps developers structure and record critical architectural decisions (ADRs) made during coding sessions. It automatically detects moments of decision, capturing the context, alternatives considered, and the rationale (trade-offs and consequences). This maintains a living log that explains 'why' the code base was built the way it is, preventing knowledge loss and improving project maintainability.