Loading...
Loading...
Found 437 Skills
Document lessons, update rules/templates/docs. Use to capture learnings after review.
Proofread posts before publishing for spelling, grammar, repetition, logic, weak arguments, and broken links
Use this skill when you need to review test cases for completeness, clarity, maintainability, and missing scenarios; triggers include 'test case review' and 'test case review'.
This skill provides the 12 critical story questions for screenplay evaluation. Covers concept, theme, audience reaction, beginning, ending, rising tensions, characters, protagonist, motivation, antagonist, and believability. Use when: evaluating a screenplay draft, identifying story weaknesses, preparing for rewrites, or validating fundamentals before submission.
OAuth and OIDC misconfiguration testing playbook. Use when reviewing redirect URI handling, state and nonce validation, PKCE, token audience, callback binding, and identity-provider trust flaws.
Crear o actualizar una Historia de Usuario. Usar cuando se necesite crear, documentar, actualizar o estandarizar historias de usuario. Activar cuando el usuario solicite una nueva historia de usuario, describa una necesidad funcional, pida refinar requisitos, estructurar funcionalidades o alinear historias existentes a las convenciones del proyecto.
Use to orchestrate approvals, QA, and go-live steps for SEO content + technical launches.
Use when planning home improvement, renovation, or DIY projects that need materials lists, tool requirements, timelines, or seasonal weather considerations
Use when you need concrete UI/UX inputs (palette, typography, landing patterns, UX/a11y constraints) to drive design or review. Searchable UI/UX design intelligence (styles, palettes, typography, landing patterns, charts, UX/a11y guidelines + stack best practices) backed by CSV + a Python search script. Triggers: UIUX/uiux, UI/UX, UX design, UI design, design system, design spec, color palette, typography, layout, animation, accessibility/a11y, component styling. Actions: search, recommend, review, improve UI.
Run after making Docyrus API changes to catch bugs, performance issues, and code quality problems. Use when implementing or modifying code that uses Docyrus collection hooks (.list, .get, .create, .update, .delete), direct RestApiClient calls, query payloads with filters/calculations/formulas/childQueries/pivots, or TanStack Query integration with Docyrus data sources. Triggers on tasks involving Docyrus API logic, data fetching, mutations, or query payload construction.
Missing state triggers repair, not failure.
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.