Loading...
Loading...
Found 2,986 Skills
YC-style office hours partner. Two modes — Startup mode runs six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit; Builder mode is an enthusiastic design partner for hackathons, learning, and side projects. Produces a design doc, never code. Use when the user says 'office hours', 'grill this idea', 'is this worth building', 'help me think through this', or describes a new product idea before any code is written.
Redesign GitHub README homepages or create standalone GitHub-safe SVG and animated GIF assets around a repository's real theme. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If the request does not clearly distinguish whole-README work from asset-only work, ask which scope the user wants before editing anything.
Set up and maintain an auditable JSON status file for a single research project, recording research phases, materials, judgments, unknowns, handovers, and change logs. Use when the user asks for "establish research archives", "save the material status of this research project", "hand over literature, judgments, and next steps to another research Skill", "check research status files", or requests the rw-research-passport workflow.
Clarify and compile project technical solutions. Use this when users need to determine the overall implementation approach, key technology trade-offs, module and file responsibilities, compatibility and verification boundaries for a problem, bug, function change, or existing requirement in combination with the current project, or when they need to create a technical document that can be understood by product, development, and testing teams and used for subsequent work. No prior requirement document is required, and it does not cover task breakdown, coding implementation, or project acceptance.
Write and maintain a CHANGELOG that stays useful months later — as a decision log, not a commit dump. Use when setting up a changelog for a project; after any code change in a project that has one; when preparing a release; or when the user asks why something was built the way it is and the answer is not in the code. Do not use for commit messages, PR descriptions, or user-facing release notes — those are different formats with different readers.
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Transform feature descriptions into well-structured project plans following conventions
Generate and critically evaluate grounded improvement ideas for the current project. Use when asking what to improve, requesting idea generation, exploring surprising improvements, or wanting the AI to proactively suggest strong project directions before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on this project', 'surprise me with improvements', 'what would you change', or any request for AI-generated project improvement suggestions rather than refining the user's own idea.
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, replacing, or archiving them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, or when pattern docs no longer reflect current code.
Research an Elixir/Phoenix topic on the web. Searches ElixirForum, HexDocs, blogs, and GitHub. Uses efficient markdown conversion.
2. Create Feature Design Document
Document a recently solved problem to compound your team's knowledge