Loading...
Loading...
Found 2,101 Skills
Facilitates the final step of a proven customer-interview method: distilling everything a round of interviews produced (GOALS.md, HYPOTHESES.md, QUESTIONS.md, and a directory of per-interview debriefs) into a single FINAL-REPORT.md the whole company can use. Top: a summary as brief as possible without losing salient information. Below: numbered findings (F1, F2, …) tagged validated / disproved / directional / watch / untested, every one citing debriefs and quoting customers verbatim, plus per-area briefs that marshal the evidence for ideal-customer definition, positioning, pricing, marketing & sales, and product priorities. Load when the user says 'write up what we found from the interviews,' 'summarize the interview results for the team,' or 'turn the interviews into a report.' Do NOT load for updating hypotheses from interviews (the synthesis step), for recording one conversation (the debrief step), or for actually doing the positioning, ideal-customer, or pricing work the report feeds.
Wait. I didn't understand the previous message—please re-explain it.
Write nurb.dev changelog entries from the releases since the last published one. Filters the release's merged PRs to what a user would actually notice, drafts each in the site's voice, and inserts the release into site/changelog.html. Use when the user says "changelog", "update the changelog", "announce this", or after cutting a release.
Create audience-aware standalone application release notes and actionable migration guides from version-control changes, contracts, schemas, configuration, tests, and deployment evidence. Use for release-visible behavior, breaking changes, upgrades, deprecations, rollout steps, or rollback guidance.
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a repository contains an `.okf/` (or other OKF) bundle that should inform the task. Triggers on: "document this in OKF", "update the knowledge bundle", "capture this as a concept", or any work in a repo that has an OKF bundle.
Trim a spec, ADR set, or design doc down to what a builder needs, without losing a fact. TRIGGER when: user says a spec is 'too long' or 'bloated'; user asks what to remove from it, or wants it cut to 'just what we need to build'.
Writes a clear design for a proposed feature or system change. Use when important product or technical choices must be settled before coding. Covers behavior, interfaces, failures, risks, acceptance criteria, and tests. Use architecture when the repository needs current ARCHITECTURE.md.
Read at the start of every session, before any other skill, and again after any compaction, model change, resume, or handoff. Routes the work to the right skill in this collection and holds one person's decisions rather than a recommendation: where generated files go, which skill wins when two match, which borrowed collections are trusted, where the ceremony is not wanted, and what the portable skills deliberately leave open. Machine-specific on purpose. Not a summary of the other skills, and not a substitute for reading the one that matched.
Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
One-time setup that maps direct competitors, alternatives, and category substitutes for the current project from the codebase, user input, and external research, then writes a root COMPETITORS.md. Use when the user invokes $setup-competitors-md, says "setup competitors", "create COMPETITORS.md", "competitive landscape", or asks to document rivals and differentiation for the project.
Review a skill to identify flaws and suggest fixes. Use when auditing an existing skill for gaps, drift, or convention violations.