en un clic
dotfiles
dotfiles contient 10 skills collectées depuis mathiassoeholm, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Use when querying or automating Jira - sprints, issues, epics, stories, boards, or correlating Jira data with external systems
Based on our current conversion write a document with high level user stories representing the valuable increments the work can be split into
Grilling session for MBM that challenges a plan against the existing domain model, sharpens terminology using UBIQUITOUS_LANGUAGE.md, and updates MBM docs/KDRs as decisions crystallise. Use when the user wants to stress-test a plan against MBM's language and documented decisions.
Use the `mdc` CLI to publish local Markdown files to Confluence and fetch/pull Confluence pages back into Markdown files. Use when the user asks to publish, update, sync, pull, fetch, or create Confluence pages from markdown, including shorthand like "Publish this KDR".
Use the local Playwright browser tools to browse websites, navigate pages, extract visible text or HTML, take screenshots, and fill simple forms. Use when the user asks to inspect a live website, click through a flow, capture a screenshot, or read content that requires a real browser.
Use when querying or automating Jira - sprints, issues, epics, stories, boards, or correlating Jira data with external systems
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Use when interacting with AWS - managing S3, EC2, Lambda, IAM, CloudFormation, ECS/EKS, RDS, DynamoDB, CloudWatch, or any AWS service
Use when interacting with GitHub - searching for repos/orgs/packages, exploring codebases, finding projects to use, querying branches/PRs/issues/releases/workflows, automating GitHub operations, or when users mention GitHub organizations or repositories
Use when querying or automating Jira - sprints, issues, epics, stories, boards, or correlating Jira data with external systems