alloy

Use only when the user explicitly allows bounded unattended execution of an approved Alloy task.

Use when encountering a bug, regression, failing command, or unexpected behavior before attempting a fix.

Use before planning when requirements are ambiguous, large, user-visible, or likely to cause rework unless decisions are locked.

Use when implementing an approved Alloy plan. Maintains progress.md, enforces TDD/debug discipline, and stops on blocked gates.

Use when a task needs broad source understanding before planning or execution.

Use when turning context or a clear user request into an implementation-ready plan with acceptance criteria, files, commands, gates, risks, and handoff.

Automated end-to-end QA — read acceptance criteria (Azure DevOps or manual), generate Playwright test plan, execute with screenshots/video/GIF, produce acceptance report. Uses Playwright CLI for deterministic, reportable execution.

Use for product or UI QA, regression checks, generated artifact inspection, and release confidence reporting.

Use before implementing new behavior or behavior-sensitive changes. Enforces red-green-refactor and records gate proof in progress.md.

Use when explaining how Alloy works, how to choose /discuss /plan /execute /verify, or how task artifacts should be maintained.

Use after implementation to verify acceptance criteria, review findings, and close progress.md gates before completion.

Fetch and normalize an Azure DevOps work item into a structured QA context. Wraps `az boards work-item show`.

MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED - Use with task(category='quick', load_skills=['git-master'], ...) to save context. Triggers - 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

Designer-turned-developer who crafts stunning UI/UX even without design mockups

MUST USE for any browser-related tasks. Browser automation via playwright-cli - verification, browsing, information gathering, web scraping, testing, screenshots, and all browser interactions.

Use when a task benefits from Container Use isolation, especially risky dependency installs, large refactors, or unfamiliar test commands.

Use when a task needs a bounded retry loop between execution, review, testing, and follow-up fixes

Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. **Trigger when user asks to:** - Design or modify PostgreSQL tables, schemas, or data models - Choose data types, constraints, indexes, or partitioning strategies - Work with pgvector embeddings, semantic search, or RAG - Set up full-text search, hybrid search, or BM25 ranking - Use PostGIS for spatial/geographic data - Set up TimescaleDB hypertables for time-series data - Migrate tables to hypertables or evaluate migration candidates **Keywords:** PostgreSQL, Postgres, SQL, schema, table design, indexes, constraints, pgvector, PostGIS, TimescaleDB, hypertable, semantic search, hybrid search, BM25, time-series