Loading...
Loading...
Found 2,113 Skills
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.
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.
codebase intel | map graphify docs learnings mempalace
Generate a comprehensive project summary from milestone artifacts for team onboarding and review
Guide existing codebase onboarding through mapping, doc ingest, and planning setup
Cross-phase audit of all outstanding UAT and verification items
career/ 에 기록된 경험 하나를 면접관 시점으로 검증하고, 파고들 자리를 되캐서 채운다. 기록이 실제로 면접에서 방어 가능한지 확인할 때 쓴다.
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.