Loading...
Loading...
Found 863 Skills
Upstash's UI design system. Use when building interfaces inspired by Upstash's aesthetic - light mode, Inter font, 4px grid.
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
Создаёт однозначную спецификацию результата без шагов реализации. Используй, когда пользователь хочет зафиксировать контекст задачи, обоснование правки, желаемый итог, критерии приемки и рамки, оставив технический путь исполняющему агенту. Не используй для выбора решения, составления плана реализации, непосредственной реализации или ревью изменений кода.
Transform raw brain dumps (dictated freestyle) into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness about something they want to build. Produces contracts and implementation specs written to ./docs/ideation/{project-name}/.
Create interactive chart visualizations (bar, line, pie) from data.
Provides active execution protocols to rigorously audit how code, directory structures, and agent actions comply with the authoritative ecosystem specs. Trigger when validating new skills, plugins, or workflows.
Améliorer un Prompt avec le Contexte du Projet, Techniques Avancées et Skills Spécialisés
How to create and structure skills for this repository. Covers the type system (guideline vs pattern), frontmatter conventions, and behavioral instructions. Follow when creating or updating any skill.
Product execution specialist for SaaS, apps, AI tools, and internal software products. Trigger when user requests 'build SaaS', 'define features', 'create user flow', 'scope MVP', 'prepare build package', 'software product', 'app definition', or 'PRD creation'.
Break down a functional spec that is too complex into smaller specs that each imply ≤ 200 lines of code. Use when analyze-if-func-spec-too-complex flags a spec as TOO COMPLEX, or when a spec is suspected of being too large.
Understand network protocols in the style of W. Richard Stevens, author of TCP/IP Illustrated. Emphasizes deep protocol understanding through packet analysis, layered thinking, and knowing exactly what happens at every byte. Use when debugging network issues, implementing protocols, or building networked applications.
Use when an agent needs to write user stories for a project