frontend-ui-ux
Designer-turned-developer who crafts stunning UI/UX even without design mockups
Discover devops sales marketing skills, compare source repositories and read the instructions for each workflow.
Designer-turned-developer who crafts stunning UI/UX even without design mockups
Product requirements for FanHub features. Use when creating new pages, components, or user-facing functionality to ensure features meet product standards.
iterate on design discussion based on user feedback
HR Recruiter role: talent acquisition, employer branding, EVP, structured interviews, STAR method, candidate experience, onboarding, 30-60-90 day plans, ATS optimization, retention strategies, hiring compliance...
Design and UX improvements for org run lisa requests. Use when asked to refine UI, layout, typography, or user experience in the app.
Validate feature requests against Genfeed OSS core vs Cloud scope. Helps users and contributors understand whether a feature belongs in the open-source core (submit PR) or Cloud SaaS (subscribe).
Lead developer agent responsible for building and maintaining company documentation structure and clarity. Use for org run coder requests and any documentation build or restructuring tasks.
Vision audit and sprint execution for org run elon and org run elon sprint requests. Use when asked to scan the repo for vision alignment, inefficiencies, or to push a fast sprint that may bend rules for speed.
CLI-based kanban-style Task Management for your apps.
Manage Linear issues and projects from the command line. This skill allows automating Linear project management.
This skill should be used when the user asks to "prepare for a board meeting", "create a board deck", "draft investor update", "prepare board agenda", "calculate runway", "prepare for investor questions", or me...
Specification management - creating, organizing, and maintaining spec items with acceptance criteria and traits.
純粋定理 P4: 純粋行為 (A-P)。Flow×Value のみの最も抽象的な行為機能。 Use when: 実行、行動、「何をするか」を問う時。 Triggers: M6 Praxis(具体化), M8 Anamnēsis(記録化) Keywords: pure-action, doing, execution,...
Scenario-driven solution design that focuses on future use cases, dimensional analysis, and explicit trade-offs
Facilitate product thinking and structure work in Linear.
This skill should be used when the user asks to "write a spec", "create a spec", "define requirements", "use ralph", "ralph methodology", "autonomous development", "sync specs to code", "run the planning loop",...
This skill should be used when the user asks about "prioritization frameworks", "how to prioritize", "Eisenhower matrix", "delegation framework", "how to delegate", "decision frameworks", "how to make decisions...
Create marketing emails and newsletters using your brand voice. Use when asked to write emails, newsletters, launch announcements, email sequences, nurture emails, or promotional content for email. Triggers on...
Creates structured meeting notes, minutes, and action items from conversations or transcripts. Use when documenting meetings, standups, retrospectives, or extracting action items from discussions.
Create new workflows with consistent structure and matching skill integration. Meta-workflow for formalizing patterns into trackable processes.
Personal work record management with multi-dimensional tracking (person, task, type, time, location, urgency, importance, difficulty). Natural language search, reports, and smart prioritization.
This skill should be used when the user asks to "create a pitch deck", "write investor emails", "analyze a term sheet", "prepare for due diligence", "understand fundraising metrics", "compare term sheets", "dra...
Generate client-friendly AI visibility reports from audit data. Use when creating client reports, visibility reports, or presenting audit results in a client-facing format. Triggers on "client report", "generat...
This skill should be used when the user asks to "write an investor update", "draft monthly update", "send investor email", "create investor newsletter", "prepare investor communication", or mentions monthly upd...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.