nixos

Trigger: update skills, commands, agents, orchestrator assets. Sync upstream AI into the @ai canonical tree while preserving local policy.

Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.

Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.

Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.

Design and manipulate Penpot projects using the Penpot MCP Plugin. Use when working with Penpot designs including creating shapes, boards, layouts, styling, components, generating CSS/HTML from designs, or any design task when Penpot MCP is connected. Triggers on mentions of "Penpot", design manipulation requests with connected MCP, or design-to-code workflows.

Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.

Create pull requests that follow the repo's own conventions. Trigger: creating, opening, or preparing PRs for review.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.

Trigger: /skill-creation, skill creation, skill creator, create skill, new skill. Create LLM-first skills with valid frontmatter.

Bootstrap or update testing context files at the repo root. Trigger: set up or refresh TESTING_CONTEXT/TESTING_SETUP when the stack or product changes.

Discover and prepare SDD testing prerequisites for Playwright, Maestro, browsers, and devices in a system-agnostic, user-guided way. Trigger: setup testing or missing testing prerequisites.

Compare a design reference (Figma, Zeplin, XD, screenshot, URL) against a live web or mobile UI via structured checklist. Trigger: visual diff in sdd-run-testing.

Bootstrap or update testing context files at the repo root. Trigger: set up or refresh TESTING_CONTEXT/TESTING_SETUP when the stack or product changes.

Discover and prepare SDD testing prerequisites for Playwright, Maestro, browsers, and devices in a system-agnostic, user-guided way. Trigger: setup testing or missing testing prerequisites.

Compare a design reference (Figma, Zeplin, XD, screenshot, URL) against a live web or mobile UI via structured checklist. Trigger: visual diff in sdd-run-testing.

Create pull requests that follow the repo's own conventions. Trigger: creating, opening, or preparing PRs for review.

Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Create versioned releases for DBFlux with automated version bumping across all package manifests. Trigger: When user asks to create a release, bump version, tag a release, or prepare a new version.

Create issues that follow the repo's own conventions. Trigger: creating GitHub issues, bug reports, or feature requests.

Activate when the user mentions their Obsidian vault, notes, tags, frontmatter, daily notes, backup, or sync. Route operations across MCP, Obsidian CLI/app actions, and git sync with safe defaults.

Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.

Create the SDD technical design and architecture approach. Trigger: orchestrator launches design for a change.

Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.

Walk users through the SDD workflow on the real codebase. Trigger: orchestrator launches onboarding for the full SDD cycle.

Create an SDD change proposal with intent, scope, and approach. Trigger: orchestrator launches proposal work for a change.

Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.

Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.

Trigger: /skill-creation, skill creation, skill creator, create skill, new skill. Create LLM-first skills with valid frontmatter.

Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.

Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.

Generate comprehensive Markdown test plans (test suites + individual test cases) from any functional specification. Use this skill whenever a user provides a spec, requirements document, user story, API description, or feature description and needs test coverage produced from it. Also trigger when the user says things like "write tests for this", "create a test plan", "generate test cases", "QA this spec", "what should I test here?", "give me coverage for this feature", or "how should I test X" — even if they don't explicitly say "functional spec". Accepts any input format: plain prose, Markdown, Confluence/Notion pages, code with inline comments, OpenAPI/Swagger specs, user stories, or mixed formats. Always use this skill for test plan requests — don't try to wing it from general knowledge.

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

(no description)

Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.