Research a brand's visual language and identity by analyzing their website, social media, and app store presence. Produces a structured brand report with colors, typography, imagery style, tone of voice, and design patterns that can inform future app or product design. Use this skill whenever the user asks to "research a brand", "analyze brand visuals", "get the look and feel of [company]", "what does [brand] look like", "collect brand assets", "study the visual identity", "brand audit", or any request that involves understanding a brand's design language before starting design work. Also trigger when the user mentions needing "brand guidelines", "visual direction", "style reference", or "design inspiration" from an existing brand. Even if the user just says something like "look at how Libresse presents themselves" — that's this skill.
Generate a comprehensive Product Requirements Document (PRD) from a project summary, brainstorm notes, or external brief. Use this skill whenever the user asks to create, write, or generate a PRD, product spec, product requirements, feature spec, or requirements document. Also trigger when the user says things like "turn this brief into requirements", "write up the product spec", "create a PRD from this summary", or "what should we build" after a brainstorm session. If the user has a Google Doc brief open in Chrome, this skill can read it directly.
Research a brand's app and web UI plus direct and adjacent competitors to build a UI inspiration package — a structured markdown report and a Pencil (.pen) moodboard. Use this skill whenever the user asks to "find UI inspiration", "research competitor apps", "look at what others are doing", "build a moodboard", "competitive UI analysis", "gather design references", "UI benchmarking", "inspiration board for [app name]", "what do similar apps look like", or "research the market before designing". Also trigger when the user says things like "see how [competitor] designs their app", "compare UI patterns across [category] apps", "create a reference board", "screen collection for inspiration", or "UI teardown". Even casual mentions like "let's see what's out there" before a design phase should trigger this skill. This skill is the natural next step after brand-research and before wireframing — it bridges brand identity research with actual UI decisions.
Create low-fidelity wireframes in Pencil (pencil.dev) from a PRD or design spec. Use this skill whenever the user asks to create wireframes, mockups, screen layouts, or app screens in Pencil. Also trigger when the user says "wireframe this", "sketch the screens", "create the UI in Pencil", "mock up the app", "design the screens", or "build wireframes from the PRD". This skill produces grayscale, layout-focused wireframes — boxes, text, and basic shapes — not polished visual designs. It uses the Pencil MCP tools (batch_design, batch_get, get_screenshot, etc.) to build .pen files.
Full Git and GitHub workflow skill — branching, commits, PRs, merges, rebasing, and conflict resolution using the `gh` CLI and `git`. Use this skill whenever the user asks to create a branch, open a PR, merge changes, rebase, resolve conflicts, check PR status, manage releases, or do anything involving git operations in a repository. Also trigger when the user references task IDs (like TASK-001) and wants to start working on them, since that implies branch creation and workflow setup. If the user says "start working on TASK-X", "ship this", "open a PR", "merge", "rebase", or mentions branches in any way, use this skill. ALSO trigger this skill when users use beginner-friendly language like: "save my work", "sync", "backup", "upload to cloud", "share my progress", "let others see my work", "save to GitHub", "push my changes", "update the cloud", or any variation suggesting they want to preserve or share their work without knowing Git terminology.
Code review skill for reviewing pull requests and code changes. Use this skill when the user asks to review a PR, review code changes, do a code review, check code quality on a branch, or says "/pr-review". Also trigger when the user wants feedback on their implementation before merging. Covers correctness, security, performance, style, and adherence to project conventions.
Development logging skill that documents everything happening during project development. Use this skill when creating branches, making commits, opening PRs, encountering problems, or when you need to log any significant development event. Also trigger when the user says "/devlog", "log this", "document what happened", or wants to add notes about their work. This skill maintains a single chronological timeline of all development activity.