Menü
SkillsMP hat 15 Skills aus gjalla/gjalla-plugin gesammelt. Öffne einen Skill, um Quelle und Details zu prüfen.
Es werden 15 von 15 gesammelten Skills angezeigt.
Add production-grade observability to code — structured logging, metrics, tracing, alerting, etc. Use this skill when the user is building or modifying a service that runs in prod. Triggers on phrases like "how will we know if this breaks", "production…
Quellsprache: Englisch
Stop and analyze before writing any code. Review the problem space — trace what the change touches, estimate the blast radius, and mentally simulate the system with the change in place. Use this skill whene you're about to implement something that modifies…
Quellsprache: Englisch
Design error handling as a first-class concern, not an afterthought. Consider where failures get caught, what state they leave the system in, and what information flows to operators, callers, and users. Triggers on phrases related to errors, when you notice a…
Quellsprache: Englisch
Analyze requirements for gaps, ambiguities, and unstated assumptions before implementing. This is "negative space analysis" — finding what the spec doesn't say that it should. Use this skill when you receive a task, ticket, user story, or feature request and…
Quellsprache: Englisch
Conduct a blameless post-mortem analysis after an incident, outage, or significant bug. Use this skill when something went wrong in production and the team needs to understand what happened, why, and how to prevent it from happening again. Triggers on phrases…
Quellsprache: Englisch
Design APIs with the discipline expected at companies known for great developer experiences. Use this skill when building new API endpoints, redesigning existing ones, or reviewing API contracts. Triggers on phrases like "design the API", "new endpoint", "API…
Quellsprache: Englisch
Design to accommodates the system's likely future, not just its present state. This is "temporal design" — reasoning about how today's implementation interacts with tomorrow's roadmap and evolving requirements. Use this skill when making decisions during…
Quellsprache: Englisch
Identify, catalog, and plan the resolution of technical debt in a codebase. Use this skill when the user wants to understand the health of their codebase, prioritize cleanup work, or plan a refactoring effort. Triggers on phrases like "tech debt", "code…
Quellsprache: Englisch
Detect and match the conventions, patterns, and local idioms of an existing codebase before writing new code. Use this skill when adding an existing codebase, especially when you're unfamiliar with the project or haven't worked in this area of the code…
Quellsprache: Englisch
Three-perspective code review from Senior Tech Lead, Product Manager, and QA Engineer. Use this skill when the user wants to be sure that their feature is complete, high quality, and bug free. Triggers when the user says things like "review this code", "is…
Quellsprache: Englisch
Plan safe migrations, deployments, and rollouts with rollback strategies, feature flags, and progressive delivery. Use this skill when the user is making changes that affect production systems — database schema changes, service deployments, data migrations,…
Quellsprache: Englisch
Cleanup and completeness gate to run before task completion in preparation for a code review. Use this skill when implementation is done and the code needs to be tidied up before handing off to reviewers. Triggers when the user says things like "clean this up…
Quellsprache: Englisch
Triage issues discovered during implementation — decide what to fix now, what to note for later, and what to leave alone. This is a "scope filtering" process that senior engineers do continuously while coding: they notice problems that aren't part of the…
Quellsprache: Englisch
Write a technical design document (RFC, tech spec, design doc, or plan) before implementing a feature or system change. Use this skill whenever the task involves building something non-trivial — a new service, a significant refactor, a new API, a data model…
Quellsprache: Englisch
Write operational runbooks for services and systems — the documented procedures that on-call engineers follow when something goes wrong. Use this skill when building or modifying a production service, after an incident reveals a gap in operational…
Quellsprache: Englisch