feat(.ai): adds skills mindset/personas#6139
feat(.ai): adds skills mindset/personas#6139marissahuysentruyt wants to merge 21 commits intomainfrom
Conversation
|
1eea82a to
46dfc1d
Compare
2da7b64 to
fb70c0b
Compare
📚 Branch Preview Links🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
…skill - The a11y migration analysis doc is a full authoring playbook, not a linting rule. Moves it from .ai/rules/ to .ai/skills/ with a SKILL.md that mirrors the component-migration-analysis skill structure. - Also fixes a stale .cursor/ path reference in component-migration-analysis/SKILL.md.
- Delete .cursor/README.md and .cursor/config.json - Delete all skill files under .cursor/skills/
7bdadee to
117b2a4
Compare
fb70c0b to
98fbdec
Compare
Description
Can be merged directly into
feat-agnostic-ai-folder-stuffbefore or after the washing machine skills PR #6127Adds a
Mindsetblock near the top of.ai/skills/*/SKILL.mdfiles so agents load a short role and quality bar before using a skill. Mindsets are tailored per skill (e.g. accessibility auditor vs code archaeologist vs requirements analyst).Fixed
conventional-commitsso it has clearer lowercase-subject wording, body bullet continuation indentation, and examples refactored to leading-bullets were aligned with the skill’s actual body guidelines.Motivation and context
Skills already described "what" to do; mindsets anchor "how" the agent should show up (verify vs assume, ask vs guess, reader-first docs).
Related issue(s)
sc-1890
Screenshots (if appropriate)
Author's checklist
Reviewer's checklist
patch,minor, ormajorfeaturesManual review test cases
SKILL.mdconventional-commits: Examples still match commitlint expectations (lowercase subjects, sensible bodies); diff is copy/format only, no accidental rule changes.Device review
Accessibility testing checklist
Required: Complete each applicable item and document your testing steps (replace the placeholders with your component-specific instructions).
Keyboard
Documentation only.
Screen reader
Documentation only.