Topic: gemini
1,485 skills in this topic.
-
creative-thinking-for-research
Applies cognitive science frameworks for creative thinking to CS and AI research ideation. Use when seeking genuinely novel research directions by leveraging combinatorial creativity, analogical reasoning, constraint manipulation, and other empirically grounded creative strategies.
Orchestra-Research/AI-Research-SKILLs 6,644
-
mcaf-adr-writing
Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy.
managedcode/MCAF 47
-
mcaf-agile-delivery
Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements.
managedcode/MCAF 47
-
mcaf-architecture-overview
Create or update `docs/Architecture.md` as the global architecture map for a solution. Use when bootstrapping a repo, onboarding, or changing modules, boundaries, or contracts. Keep it navigational and use `references/overview-template.md` for scaffolding.
managedcode/MCAF 47
-
mcaf-ci-cd
Design or refine CI/CD workflows, quality gates, release flow, and safe AI-assisted pipeline authoring. Use when adding or changing build pipelines, release stages, IaC-driven environments, or deployment rollback policy.
managedcode/MCAF 47
-
mcaf-code-review
Prepare for, perform, or tighten code review workflow: PR scope, review checklist, reviewer expectations, and merge hygiene. Use when shaping pull requests, defining review policy, or auditing whether a change is review-ready.
managedcode/MCAF 47
-
mcaf-devex
Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup. Use when the repo is hard to run, debug, test, or onboard into.
managedcode/MCAF 47
-
mcaf-documentation
Create or refine durable engineering documentation: docs structure, navigation, source-of-truth placement, and writing quality. Use when a repo’s docs are missing, stale, duplicated, or hard to navigate, or when adding new durable engineering guidance.
managedcode/MCAF 47
-
mcaf-feature-spec
Create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.
managedcode/MCAF 47
-
mcaf-human-review-planning
Plan a human review for a large AI-generated code drop by reading the target area, tracing the natural user and system flows, identifying the riskiest boundaries, and prioritizing the files a human should inspect first. Use when the codebase is too large to review line-by-line and you need a practical review sequence plus a prioritized file list.
managedcode/MCAF 47
-
mcaf-ml-ai-delivery
Apply ML/AI project delivery guidance for data exploration, feasibility, experimentation, testing, responsible AI, and operating ML systems. Use when the repo includes model training, inference, data science workflows, or ML-specific delivery planning.
managedcode/MCAF 47
-
mcaf-nfr
Capture or refine non-functional requirements such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.
managedcode/MCAF 47
-
mcaf-observability
Design or improve observability for application and delivery flows: logs, metrics, traces, correlation, alerts, and operational diagnostics. Use when a change affects runtime visibility, failure diagnosis, SLOs, or alerting.
managedcode/MCAF 47
-
mcaf-security-baseline
Apply baseline engineering security guidance: secrets handling, secure defaults, threat modelling references, and review checkpoints for auth, data flow, pipelines, and external integrations. Use when a change has security impact but does not require a full standalone AppSec engagement.
managedcode/MCAF 47
-
mcaf-solid-maintainability
Apply SOLID, SRP, cohesion, composition-over-inheritance, and small-file discipline to code changes. Use when refactoring large files or classes, setting maintainability limits in `AGENTS.md`, documenting justified exceptions, or reviewing design quality.
managedcode/MCAF 47
-
mcaf-solution-governance
Set up or refine solution-level governance for MCAF repositories: root and project-local `AGENTS.md`, rule precedence, solution topology, skill routing, and maintainability-limit policy placement. Use when bootstrapping a repo, restructuring a multi-project solution, or tightening agent rules.
managedcode/MCAF 47
-
mcaf-source-control
Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.
managedcode/MCAF 47
-
mcaf-testing
Add or update automated tests for a change using the repository’s verification rules in `AGENTS.md`. Use when implementing a feature, bugfix, refactor, or regression test; prefer stable integration/API/UI coverage and pull deeper test strategy from the bundled references.
managedcode/MCAF 47
-
mcaf-ui-ux
Use UI/UX engineering guidance for design systems, accessibility, front-end technology selection, and design-to-development collaboration. Use when bootstrapping a UI project, choosing front-end stack, or tightening design and accessibility practices.
managedcode/MCAF 47
-
avalonia-accessibility-and-validation
Design or review Avalonia validation, data-error presentation, accessibility semantics, automation properties, focus order, and testable UI metadata. Use for validation pipelines, screen-reader support, keyboard-only UX, automation-tree issues, or accessibility hardening.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-bindings-and-xaml
Implement or troubleshoot Avalonia compiled bindings, runtime XAML loading, converters, markup extensions, binding notifications, dynamic resources, and AOT-safe XAML patterns. Use for `x:DataType`, `CompiledBinding`, converter wiring, `AvaloniaRuntimeXamlLoader`, resource lookup issues, or runtime markup refactors.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-platform-services
Integrate or troubleshoot Avalonia platform services such as storage provider, clipboard, launcher, drag/drop, screens, and top-level runtime helpers. Use for file pickers, external-open flows, clipboard or data-transfer bugs, multi-screen behavior, or platform service abstractions.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-rendering-and-graphics
Implement or review Avalonia animations, compositor usage, custom drawing, Skia rendering, geometry, hit testing, and advanced rendering interop. Use for transitions, frame-loop work, `Render` overrides, custom visuals, drawing optimizations, or OpenGL or Vulkan hosting boundaries.
wieslawsoltes/development-plugin-for-avalonia 57
-
winui-to-avalonia
Port WinUI or Windows App SDK applications to Avalonia, including shell design, dependency-property patterns, theme resources, composition, commands, dialogs, and platform integration. Use for `NavigationView`, `ContentDialog`, `ThemeResource`, `VisualStateManager`, `ItemsRepeater`, `AppWindow`, or broader WinUI-to-Avalonia migration work.
wieslawsoltes/development-plugin-for-avalonia 57