Skills¶
48 English profiles generated from canonical sources. Select by outcome; load focused references only when needed.
| Name | Use when |
|---|---|
| agent-routing | Select skills and specialist agents for a user outcome, using progressive loading and explicit, verifiable handoffs. |
| anti-patterns | Spot avoidable complexity when reviewing architecture, code, processes or proposed dependencies. |
| architecture | Choose an architecture approach when planning system boundaries, interfaces, deployment or quality requirements. |
| api-design | Design or review an HTTP API, consumer contract, errors, authorization, pagination or compatibility changes. |
| cloud-native | Plan or review cloud deployment, managed services, runtime configuration and operational resilience. |
| domain-driven-design | Model business rules, aggregates, bounded contexts or domain terminology in an existing or new application. |
| microservices | Evaluate a service split or improve an existing distributed system with explicit ownership and failure handling. |
| performance | Investigate measured latency, throughput, memory or resource problems and validate an optimization. |
| security | Review a concrete trust boundary, authentication, authorization, secret handling or vulnerability fix. |
| creative-apps | Develop an interactive creative application for music, art, editing or other expressive workflows. |
| creative-app-patterns | Implement document models, undo/redo, real-time feedback or media processing in a creative application. |
| flutter-patterns | Build, review or debug a Flutter application, including platform integration and widget behavior. |
| frontend-patterns | Build or improve a web interface with accessible interaction, clear states, reusable components and API contracts. |
| game-development | Plan or implement a playable prototype, game loop, mechanics or game architecture. |
| game-architecture | Structure an existing or new game for clear state ownership, engine integration and testable mechanics. |
| game-design | Clarify a game concept, core loop, player goals, balancing or playtest criteria. |
| game-mechanics | Implement or tune a specific game mechanic such as movement, combat, inventory or progression. |
| prototyping | Create a short experiment to reduce uncertainty in a game, interface or technical concept. |
| gcp-patterns | Design, deploy or troubleshoot a workload on Google Cloud with clear cost and operational constraints. |
| general | Select communication or engineering decision support for work that does not require a language-specific skill. |
| communication | Write a status update, explanation, decision request or stakeholder message with a clear audience and purpose. |
| principal-engineer-decisions | Compare consequential technical options and record an architecture or delivery decision. |
| golang-patterns | Write, review or debug idiomatic Go code, concurrency, interfaces and resource management. |
| iot-embedded-patterns | Develop or review firmware, embedded protocols, resource-constrained systems or device integration. |
| marp-presentations | Create or revise a Marp presentation with concise narrative, readable slides and compatible frontmatter. |
| obsidian-para | Capture, retrieve and maintain notes in a private Obsidian vault organized as Projects, Areas, Resources and Archive, including Windows/WSL links. |
| product-discovery | Clarify a product idea or feature, test uncertain assumptions and produce a small delivery slice with measurable acceptance criteria. |
| project-management | Organize delivery, technical debt or release work without excessive process overhead. |
| agile-methodologies | Improve delivery flow, break down work or plan a small iteration using proportionate agile practices. |
| devops-cicd | Build or repair CI, deployment, release, rollback or reproducible development workflows. |
| technical-debt | Assess a maintainability problem and prioritize a safe, incremental repayment plan. |
| python-patterns | Write, review or refactor Python using dataclasses, explicit boundaries, uv and behavior-focused tests. |
| software-engineering | Select focused engineering guidance for code quality, testing, refactoring or design choices. |
| clean-code | Improve readability and changeability of code while preserving behavior and project conventions. |
| code-review | Review a change for correctness, regression risk, security and maintainability with actionable findings. |
| design-patterns | Choose or simplify a design pattern at a real variation, lifecycle or integration boundary. |
| practical-refactoring | Refactor existing code incrementally while preserving behavior and keeping changes reviewable. |
| solid-principles | Evaluate responsibilities and dependencies using SOLID principles without unnecessary abstractions. |
| testing-strategies | Choose meaningful unit, integration or end-to-end checks proportional to a software change. |
| system-design | Plan system-level behavior, data flow, interfaces and operational constraints for a concrete use case. |
| architecture-planning | Produce a concise architecture plan with boundaries, alternatives, delivery steps and verification. |
| team-collaboration | Coordinate shared work, reviews, incidents or handoffs with explicit ownership and compact records. |
| feature-discovery-session | Turn a stakeholder conversation into a scoped feature, assumptions and verifiable acceptance criteria. |
| incident-response | Investigate an outage or regression, restore service and record an evidence-based follow-up. |
| pr-crafting | Prepare a reviewable pull request description, scope and validation evidence for a code change. |
| progress-sync | Summarize current work, evidence, blockers and next actions without duplicating project records. |
| testing | Design or improve behavior-focused tests and a practical verification strategy for a change. |
| work-management | Plan and execute a larger task with one compact Markdown record containing acceptance criteria, tasks, feedback, decisions and evidence. |