Loading...
Loading...
Found 2,896 Skills
Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.
Explain and document MTHDS bundles. Use when user says "what does this pipeline do?", "explain this workflow", "explain this method", "walk me through this .mthds file", "describe the flow", "document this pipeline", "how does this work?", or wants to understand an existing MTHDS method bundle.
Implements stories with code and tests.
Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.
Create and maintain a repository-root ROADMAP.md as the single source of truth for project milestones and accepted plans. Use when bootstrapping any new project, accepting/completing a plan, defining or updating milestone/version roadmaps, marking milestones as reached/changed/de-scoped, or answering where roadmap and milestone status should be referenced.
Systematisk analys av intervjutranskript enligt Gioia-metodiken. [VAD] Analyserar kvalitativa intervjutranskript genom 1st-order kodning (informantspråk), 2nd-order tematisering (forskarkonceptualisering) och aggregerade dimensioner. Producerar standardiserad dokumentation med indexerade, export-ready citat. [NÄR] Use when: gioia, intervjuanalys, transkriptanalys, kvalitativ analys, kodning, tematisk analys, grounded theory, 1st-order, 2nd-order [SPRÅK] Svenska (primärt), engelska vid behov [KÄLLA] Gioia, D.A., Corley, K.G. & Hamilton, A.L. (2013). Seeking Qualitative Rigor in Inductive Research. Organizational Research Methods.
Use the mermaid-diagrams skill whenever you are creating or updating mermaid diagrams. Provides guidance on mermaid best practices.
Explain code in detail - what it does, how it works, and why. Use when you need to understand unfamiliar code or explain code to others.
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Comprehensive content review and quality assurance for PRD documents - validates link integrity, threshold consistency, BRD alignment, and identifies issues requiring manual attention
Creates or updates the product marketing context document for a brand — the deep positioning reference that all marketing specialists read before any task. Use when the user wants to document product positioning, target audience, customer language, competitive differentiation, objections, personas, or proof points. Also use when marketing output feels generic and needs richer brand context, when starting a new brand without a full SOSTAC plan, or when SOSTAC is complete and the user wants a distilled reference for the whole team. Works with the multi-brand system — always asks which brand to work on first.